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
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: trusty- amd64 pristine "uvt snapshot" trusty- amd64 trusty- amd64 trusty- amd64 # this is showing as shutoff after start, this might be different with qemu 1.5
$ virsh snapshot-create-as forhallyn-
$ virsh snapshot-current --name forhallyn-
pristine
$ virsh start forhallyn-
$ virsh snapshot-list forhallyn-
in guest:
sudo apt-get update
sudo apt-get dist-upgrade
780 upgraded...
shutdown -h now
$ virsh snapshot-delete forhallyn- trusty- amd64 pristine --children trusty- amd64 pristine "uvt snapshot"
$ virsh snapshot-create-as forhallyn-
$ virsh start forhallyn- trusty- amd64 # this command works, but there is often disk corruption