On Fri, Jun 15, 2007 at 12:05:33AM +0100, Daniel P. Berrange wrote:
> I'm curious as to what the changes for bootloader / kernel are for ?
> Surely you always have either a bootloader, or a kenrel present in
> the SEXPR ? So I'm not sure why its neccessary to disable the check
No, this is not true, and it's not true in Xen too. This is stuff that
got merged up in my pygrub changes.
Basically the logic is something like:
if there is no kernel specified:
if there is no bootloader specified:
default to pygrub (for Solaris, this will fill in
kernel/ramdisk/extra automatically)
if there is a bootloader specified:
use the specified bootloader
else:
if there is no bootloader specified:
load kernel/ramdisk from dom0 FS
else
use bootloader to load specified files
> for validating presence of one of the two. I'd be interested to see
> the output of 'xm list --long' SEXPR on a Solaris system with a few
> guests running.
An example:
(domain
(domid 15)
(on_crash preserve)
(memory 512)
(uuid dd2b0096-0b4f-db69-20da-ecc19202f2e4)
(bootloader_args )
(name sxc16)
(maxmem 512)
(on_reboot restart)
(on_poweroff destroy)
(localtime 0)
(vcpus 1)
(bootloader )
(shadow_memory 0)
(cpu_weight 256)
(cpu_cap 0)
(features )
(on_xend_start ignore)
(on_xend_stop shutdown)
(start_time 1181862774.81)
(cpu_time 49.172084538)
(online_vcpus 1)
(image (linux (kernel ) (args 'root=/dev/dsk/c0d0s0 ')))
(status 2)
(memory_dynamic_min 511)
(memory_dynamic_max 512)
(state -b----)
(store_mfn 918112)
(console_mfn 918111)
(device
(vif
(mac aa:04:03:35:a8:50)
(uuid 1c1010a0-ddfd-7173-7b8f-2d7115524f73)
)
)
(device
(vbd
(uname phy:/dev/zvol/dsk/export/sxc16-root)
(driver paravirtualised)
(mode w)
(dev 0)
(uuid ac1699dd-5154-6432-8dee-73322c80adaa)
)
)
)