libvirt/tests/sexpr2xmldata/sexpr2xml-fv-empty-kernel.sexpr

(domain (domid 3)(name 'fvtest')(memory 400)(maxmem 400)(vcpus 1)\
(uuid 'b5d70dd275cdaca517769660b059d8bc')(on_poweroff 'destroy')\
(on_reboot 'restart')(on_crash 'restart')\
(image (hvm (loader /usr/lib/xen/boot/hvmloader)(kernel '')\
(device_model '/usr/lib64/xen/bin/qemu-dm')(boot d)(cdrom '/root/boot.iso')\
(acpi 1)(vnc 1)(keymap ja)))(device (vbd (dev 'ioemu:hda')\
(uname 'file:/root/foo.img')(mode 'w')))\
(device (vif (mac '00:16:3e:1b:b1:47')(bridge 'xenbr0')\
(script 'vif-bridge')(type ioemu))))
xen_xs: Guard against set but empty kernel argument On xen 4.1 I observed configurations that look like: (image (hvm (kernel '') (loader '/foo/bar') )) The kernel element is there but unset. This leads to an empty <kernel/> element in the XML and even worse makes us skip the boot order parsing and therefore not emit a <boot device='$dev>'/> element which breaks CD booting. 2011-10-10 16:22:44 +00:00			`(domain (domid 3)(name 'fvtest')(memory 400)(maxmem 400)(vcpus 1)\`
			`(uuid 'b5d70dd275cdaca517769660b059d8bc')(on_poweroff 'destroy')\`
			`(on_reboot 'restart')(on_crash 'restart')\`
			`(image (hvm (loader /usr/lib/xen/boot/hvmloader)(kernel '')\`
			`(device_model '/usr/lib64/xen/bin/qemu-dm')(boot d)(cdrom '/root/boot.iso')\`
			`(acpi 1)(vnc 1)(keymap ja)))(device (vbd (dev 'ioemu:hda')\`
			`(uname 'file:/root/foo.img')(mode 'w')))\`
			`(device (vif (mac '00:16:3e:1b:b1:47')(bridge 'xenbr0')\`
			`(script 'vif-bridge')(type ioemu))))`