[Bug 634488] Re: new virtual machines do not boot

[Matt Price]

  On 10-10-02 05:24 PM, William Ahern wrote:
> I ran into the same problem after upgrading from Lucid to Maverick. The
> problem is that vmbuilder isn't changing the disk file format from `raw'
> to `cow2' when moving the image from /tmp to the install location. To
> get the VM to boot just fire up virsh, edit [vm], and change "<driver
> name='qemu' type='raw/>" to"<driver name='qemu' type='qcow2'/>".
this is really helpful, William.  Thanks so much for tracking this 
down.  couldn't immediately find the place in the code to fix this; 
concievably it's a libvirt issue?  Is there a dev listening on this bug 
-- it looks like a quick fix if you know where to look for it.  Thanks 
again...

-- 
new virtual machines do not boot
https://bugs.launchpad.net/bugs/634488
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.