[Bug 1292234] Re: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)

[Jamie Strandboge]

Did you try with the image on
https://chinstrap.canonical.com/~jamie/lp1292234/? I was only able to
trigger it by using an old image, creating the snapshot, starting it,
apt-get dist-upgrading, cleanly shutting down, then deleting the
snapshot and creating another with the same name. Using a fresh install
or a too new image doesn't do it for me (I guess enough has to happen in
the guest to trigger it).

Ie:
$ virsh snapshot-create-as forhallyn-trusty-amd64 pristine "uvt snapshot"
$ virsh snapshot-current --name forhallyn-trusty-amd64
pristine
$ virsh start forhallyn-trusty-amd64
$ virsh snapshot-list forhallyn-trusty-amd64 # this is showing as shutoff after start, this might be different with qemu 1.5

in guest:
sudo apt-get update
sudo apt-get dist-upgrade
780 upgraded...
shutdown -h now

$ virsh snapshot-delete forhallyn-trusty-amd64 pristine --children
$ virsh snapshot-create-as forhallyn-trusty-amd64 pristine "uvt snapshot"

$ virsh start forhallyn-trusty-amd64 # this command works, but there is
often disk corruption

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1292234

Title:
  qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1292234/+subscriptions