to create snapshot ,I did step below: virsh snapshot-create-as centos snap1 --disk-only --atomic --no-metadata virsh snapshot-create-as centos snap2 --disk-only ...... ........................ virsh snapshot-creates-as centos snap10 ..... then i got 10 snapshot of a vm, to revert, i just did the follow step: 1 destroy centos 2 editor="sed -i 's/centosdisk.snap10/centosdisk.snap1/g'" virsh edit centos 3 rm -f centos.snap{2,3,4,5,6.....} 4 start centos is these steps correct? and another question is ,when i revert to a snapshot,some files of the vm's system missing，does this have any relation with the disk cache mode (writeback,writethrough,none,etc.)???how could i avoid that happen?? thanks.

On 05/29/2012 10:22 AM, xingxing gao wrote: > to create snapshot ,I did step below: > virsh snapshot-create-as centos snap1 --disk-only --atomic --no-metadata > virsh snapshot-create-as centos snap2 --disk-only ...... > ........................ > virsh snapshot-creates-as centos snap10 ..... > then i got 10 snapshot of a vm, > to revert, i just did the follow step: > 1 destroy centos > 2 editor="sed -i 's/centosdisk.snap10/centosdisk.snap1/g'" virsh edit centos > 3 rm -f centos.snap{2,3,4,5,6.....} Yes, that will be sufficient to revert to the state of the first disk snapshot, and on booting the 'centos' VM, your domain will have to run fsck in order to recover to the fact that the file system was not in a clean state at the time of the snapshot (basically, booting from your disk snapshot is the same as booting as if you had yanked the power cord). > 4 start centos > is these steps correct? > and another question is ,when i revert to a snapshot,some files of the > vm's system missing，does this have any relation with the disk cache > mode (writeback,writethrough,none,etc.)???how could i avoid that > happen?? You can install the qemu-ga guest agent in the guest, wire it up in the host XML describing that guest, and add the --quiesce option to your snapshot-create-as command in an effort to have the guest freeze file systems before taking the snapshot. The end result will be that the file system is in a sane state (as if you had cleanly shut down), rather than in an incomplete state (as if you had yanked the power cord). I know that qemu-ga is available as part of the latest Fedora package, and that it was designed to be compiled for older Linux and also for Windows guests, although I don't personally have a good pointer for where to get the best version of qemu-ga for your specific guests. Maybe others can chime in here. -- Eric Blake eblake(a)redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org

Eric Blake <eblake@...> writes:

> > Yep. You've run into a case where I haven't yet been able to code > things. The problem is that reverting to a disk image has a question - > you are starting with two files (the snapshot backing file and the new > qcow2 wrapper), but the moment you reload the backing file for > modification, you invalidate the qcow2 wrapper. There are two sane > options - create yet another qcow2 wrapper around the same backing file, > or delete the qcow2 wrapper as part of reverting to the snapshot, but we > would probably need two new flags to the virDomainRevertToSnapshot API > to select one of these two behaviors. In the meantime, the only way to > revert to a disk-only snapshot is to manually edit the domain XML to > match what you want to do, possibly with manual qemu-img operations as well. > > Help in writing the patches to improve the functionality would be welcome. > Has the issue ( revert to external disk snapshot ) been solved in later versions of libvirt?

I am using: Compiled against library: libvirt 1.2.2 Using library: libvirt 1.2.2

Using API: QEMU 1.2.2 Running hypervisor: QEMU 2.1.92 On trying to revert to an external snapshot, Getting the error: revert to external disk snapshot not supported yet If not is there any alternate.