** Description changed: Binary package hint: vmbuilder 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'. TEST CASE 1 (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'. - TEST CASE 2 (don't regress --raw (first delete the previos 'ubuntu' domain)): + TEST CASE 2 (don't regress --raw (first delete the previous 'ubuntu' domain)): $ qemu-img create /tmp/foo.img 5G $ sudo /sbin/losetup /dev/loop1 /tmp/foo.img - $ sudo vmbuilder kvm ubuntu --suite lucid --flavour virtual --arch i386 -o --libvirt qemu:///system --raw=/tmp/foo.img + $ sudo vmbuilder kvm ubuntu --suite lucid --flavour virtual --arch i386 -o --libvirt qemu:///system --raw=/dev/loop1 $ virsh --connect=qemu:///system start ubuntu $ virt-viewer --connect=qemu:///system ubuntu At this point the VM should be started and running.
-- vmbuilder XML is incomplete with libvirt 0.8.3 (No bootable devices) https://bugs.launchpad.net/bugs/659532 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
