Daniel P. Berrange wrote:
On Thu, Feb 07, 2008 at 12:38:07PM +0100, Guido Guenther wrote:
... since a bootloader tag is found the kernel and initrd entries are being dropped. My hack is to ignore empty bootloader statements for the moment:
I've seen this issue as well.
Nope, that's no good - empty bootloader indicates use of the defautl XenD bootloader. What we need is to not drop the kernel/initrd when doing XML to SEXPR back into XenD. We currently create an SXPR with either a (bootloader) or a (kernel) block - we should unconditionally do both & not try to second guess it. IIRC, John mentioned this is already needed for Solaris too.
Ah. So to make sure I understand correctly, the planned resolution is to leave the empty bootloader tag and then ensure that it's handled properly during the domain start? -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com