| 2010-10-12 21:39:31 |
Jamie Strandboge |
bug |
|
|
added bug |
| 2010-10-12 21:40:00 |
Jamie Strandboge |
vm-builder (Ubuntu): importance |
Undecided |
High |
|
| 2010-10-12 21:40:00 |
Jamie Strandboge |
vm-builder (Ubuntu): status |
New |
Triaged |
|
| 2010-10-12 21:40:25 |
Jamie Strandboge |
description |
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:
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: 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'. 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'
|
|
| 2010-10-12 21:40:53 |
Jamie Strandboge |
nominated for series |
|
Ubuntu Lucid |
|
| 2010-10-12 21:40:53 |
Jamie Strandboge |
bug task added |
|
vm-builder (Ubuntu Lucid) |
|
| 2010-10-12 21:40:53 |
Jamie Strandboge |
nominated for series |
|
Ubuntu Maverick |
|
| 2010-10-12 21:40:53 |
Jamie Strandboge |
bug task added |
|
vm-builder (Ubuntu Maverick) |
|
| 2010-10-12 21:40:53 |
Jamie Strandboge |
nominated for series |
|
Ubuntu Natty |
|
| 2010-10-12 21:40:53 |
Jamie Strandboge |
bug task added |
|
vm-builder (Ubuntu Natty) |
|
| 2010-10-12 21:42:51 |
Jamie Strandboge |
vm-builder (Ubuntu Maverick): status |
New |
Triaged |
|
| 2010-10-12 21:42:53 |
Jamie Strandboge |
vm-builder (Ubuntu Lucid): status |
New |
Triaged |
|
| 2010-10-12 21:42:56 |
Jamie Strandboge |
vm-builder (Ubuntu Lucid): importance |
Undecided |
High |
|
| 2010-10-12 21:43:00 |
Jamie Strandboge |
vm-builder (Ubuntu Maverick): importance |
Undecided |
High |
|
| 2010-10-12 21:45:03 |
Jamie Strandboge |
removed subscriber Jamie Strandboge |
|
|
|
| 2010-10-12 21:45:08 |
Jamie Strandboge |
bug |
|
|
added subscriber Jamie Strandboge |
| 2010-10-12 21:45:30 |
Jamie Strandboge |
bug |
|
|
added subscriber Ubuntu Security Team |
| 2010-10-12 22:20:50 |
Jamie Strandboge |
description |
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'. 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: 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'. 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 --connect=qemu:///system start ubuntu
$ virt-viewer --connect=qemu:///system ubuntu
At this point the VM has started, but shows 'No bootable devices'
|
|
| 2010-10-12 22:21:02 |
Jamie Strandboge |
vm-builder (Ubuntu Maverick): status |
Triaged |
In Progress |
|
| 2010-10-12 23:06:21 |
Jamie Strandboge |
description |
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'. 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 --connect=qemu:///system start ubuntu
$ virt-viewer --connect=qemu:///system ubuntu
At this point the VM has started, but shows 'No bootable devices'
|
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)):
$ 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
$ virsh --connect=qemu:///system start ubuntu
$ virt-viewer --connect=qemu:///system ubuntu
At this point the VM should be started and running. |
|
| 2010-10-12 23:38:32 |
tp |
bug |
|
|
added subscriber tp |
| 2010-10-12 23:42:26 |
tp |
removed subscriber tp |
|
|
|
| 2010-10-13 00:24:47 |
Jamie Strandboge |
attachment added |
|
vm-builder_0.12.4-0ubuntu1.1.debdiff https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/659532/+attachment/1689824/+files/vm-builder_0.12.4-0ubuntu1.1.debdiff |
|
| 2010-10-13 12:36:56 |
Jamie Strandboge |
description |
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)):
$ 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
$ virsh --connect=qemu:///system start ubuntu
$ virt-viewer --connect=qemu:///system ubuntu
At this point the VM should be started and running. |
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 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=/dev/loop1
$ virsh --connect=qemu:///system start ubuntu
$ virt-viewer --connect=qemu:///system ubuntu
At this point the VM should be started and running.
|
|
| 2010-10-13 12:58:27 |
Jamie Strandboge |
description |
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 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=/dev/loop1
$ virsh --connect=qemu:///system start ubuntu
$ virt-viewer --connect=qemu:///system ubuntu
At this point the VM should be started and running.
|
Binary package hint: vmbuilder
SRU
1. 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'.
2. this is not yet fixed upstream (or Natty), but is ACKd by upstream
3. Patch adjusts VMbuilder/disk.py to have a new 'self.format_type' attribute. This attribute will normally be 'None', but will be set when a disk is convert()ed. VMbuilder/plugins/libvirt/templates/libvirtxml*.tmpl is then adjusted to supply the proper qemu image format to libvirt if the format_type is set for the disk. Since libvirt defaults to 'raw' for unspecified format types, this covers the default 'qcow2' case and avoids setting the format type when using --raw.
4a. 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 will have started, but shows 'No bootable devices' if unpatched. If patched, it should boot up fine.
4b. 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=/dev/loop1
$ virsh --connect=qemu:///system start ubuntu
$ virt-viewer --connect=qemu:///system ubuntu
At this point the VM should be started and running.
5. Risk of regression is considered low. Patch is not intrusive and only will add the extra XML only if a disk is converted, so it should affect no other parts of libvirt. Since vm-builder with libvirt and qcow2 disks (the default) are currently broken, there is no risk of regression in the libvirt code. Tests show that --raw still works properly too. |
|
| 2010-10-13 13:05:16 |
Jamie Strandboge |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2010-10-13 13:05:34 |
Jamie Strandboge |
vm-builder (Ubuntu Lucid): assignee |
|
Jamie Strandboge (jdstrand) |
|
| 2010-10-13 13:05:38 |
Jamie Strandboge |
vm-builder (Ubuntu Maverick): assignee |
|
Jamie Strandboge (jdstrand) |
|
| 2010-10-13 13:05:42 |
Jamie Strandboge |
vm-builder (Ubuntu Natty): assignee |
|
Jamie Strandboge (jdstrand) |
|
| 2010-10-13 13:05:52 |
Jamie Strandboge |
vm-builder (Ubuntu Maverick): milestone |
|
maverick-updates |
|
| 2010-10-14 06:54:22 |
Martin Pitt |
vm-builder (Ubuntu Maverick): status |
In Progress |
Fix Committed |
|
| 2010-10-14 06:54:25 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2010-10-14 06:54:27 |
Martin Pitt |
tags |
regression-release |
regression-release verification-needed |
|
| 2010-10-14 13:31:28 |
Launchpad Janitor |
vm-builder (Ubuntu Maverick): status |
Fix Committed |
Fix Released |
|
| 2010-10-14 13:32:20 |
Jamie Strandboge |
vm-builder (Ubuntu Maverick): status |
Fix Released |
Fix Committed |
|
| 2010-10-14 13:32:24 |
Jamie Strandboge |
vm-builder (Ubuntu Natty): status |
Triaged |
Fix Released |
|
| 2010-10-14 13:34:25 |
Jamie Strandboge |
vm-builder (Ubuntu Lucid): status |
Triaged |
Fix Committed |
|
| 2010-10-14 13:38:04 |
Jean-Baptiste Lallement |
tags |
regression-release verification-needed |
regression-release verification-done |
|
| 2010-10-14 13:38:32 |
Jean-Baptiste Lallement |
tags |
regression-release verification-done |
regression-release verification-done verification-needed |
|
| 2010-10-15 13:41:26 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/maverick-proposed/vm-builder |
|
| 2010-10-20 16:16:07 |
Launchpad Janitor |
vm-builder (Ubuntu Maverick): status |
Fix Committed |
Fix Released |
|
| 2010-10-21 22:07:33 |
Launchpad Janitor |
vm-builder (Ubuntu Lucid): status |
Fix Committed |
Fix Released |
|
| 2010-10-21 22:14:20 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/lucid-security/vm-builder |
|
| 2011-09-19 21:34:46 |
Ubuntu Foundations Team Bug Bot |
tags |
regression-release verification-done verification-needed |
regression-release testcase verification-done verification-needed |
|
