libvirt 0.8.3 and later (and the upcoming libvirt update for lucid-security) does not probe qemu disks for the image format and defaults to 'raw' when the format is not specified in the XML. This breaks vmbuilder because the version in maverick does not specify a format in the XML.
WORKAROUND:
After creating, use '/usr/sbin/libvirt-migrate-qemu-disks'. Should be able to also use the '--raw' option when running vmbuilder (need to create the disk first when using '--raw', eg: 'qemu-img create foo.img 2G'), but I can't seem to get this to work right.
TEST CASE (in maverick release):
$ sudo vmbuilder kvm ubuntu --suite lucid --flavour virtual --arch i386 -o --libvirt qemu:///system
$ virsh start ubuntu
$ virt-viewer ubuntu
At this point the VM has started, but shows 'No bootable devices'
Binary package hint: virtinst
libvirt 0.8.3 and later (and the upcoming libvirt update for lucid-security) does not probe qemu disks for the image format and defaults to 'raw' when the format is not specified in the XML. This breaks vmbuilder because the version in maverick does not specify a format in the XML.
WORKAROUND: libvirt- migrate- qemu-disks' . Should be able to also use the '--raw' option when running vmbuilder (need to create the disk first when using '--raw', eg: 'qemu-img create foo.img 2G'), but I can't seem to get this to work right.
After creating, use '/usr/sbin/
TEST CASE (in maverick release):
$ sudo vmbuilder kvm ubuntu --suite lucid --flavour virtual --arch i386 -o --libvirt qemu:///system
$ virsh start ubuntu
$ virt-viewer ubuntu
At this point the VM has started, but shows 'No bootable devices'