search for: virdomainsnapshotcreatexml

...Is there only way that I turn to freeze/thaw functions? > > Guest freeze/thaw (virDomainFSFreeze) only works on a live guest. So > what you will have to do is: > > virDomainFSFreeze(vm1, ...) > virDomainFSFreeze(vm2, ...) > virDomainSuspend(vm1) > virDomainSuspend(vm2) > virDomainSnapshotCreateXML(vm1, ...) > virDomainSnapshotCreateXML(vm2, ...) > virDomainResume(vm1) > virDomainResume(vm2) > virDomainFSThaw(vm1, ...) > virDOmainFSThaw(vm2, ...) > I see, thanks. > > However, I honestly don't know why you think you need disk snapshots > from the same point...

...o store these snapshots on my storage devices to use them whenever and wherever I want. Is it possible to store a single snapshot providing both the memory and disks state in a file (maybe a .qcow2 file)? Is there any way to get a unique interface which handles my snapshots? I was used to use the virDomainSnapshotCreateXML() defining the destination file in the XML with <disk> fields. After updating libvirt it was not working anymore, I thought was a bug but then I realized it was intentional. The function complains about the fact that the <disk> parameter is not accepted anymore. So I started guessing ho...

yes, I got your point, thanks very much Eric. If I want to take a distributed snapshot, which need pause all the VMs and then take snapshot, how can I control the pause for all the VMs? Is there only way that I turn to freeze/thaw functions? and freeze/thaw only for file systems, not for the whole guest, am I right? Thanks a lot! Best, Yuanzhen On Wed, Aug 6, 2014 at 11:35 AM, Eric Blake

...xDaFox wrote: > > To create the snapshots I'm using the libvirt command snapshotCreateXML > > with no flag set. Does libvirt support consistent snapshotting or shall I > > rely on QEMU backup new feature only? > > According to: http://wiki.libvirt.org/page/Snapshots > virDomainSnapshotCreateXML is only consistent if the guest is paused > during the operation. > > The new qemu feature is called drive-backup > (http://wiki.qemu.org/Features/IncrementalBackup). Unless things > changed recently, it is not exposed through libvirt, so the only way > to use it is by sending qe...

...pdates</description> <disks> <disk name='vda'> <source file='/home/potato/libvirt/backups/test-snap1.qcow2'/> </disk> </disks> </domainsnapshot> And got the following error: if ret is None:raise libvirtError('virDomainSnapshotCreateXML() failed', dom=self) libvirt.libvirtError: unsupported configuration: disk 'vda' must use snapshot mode 'internal' Is this expected? Thanks! Sincerely, Roger Jin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/arch...

...);* The error is as follows libvir: Remote error : out of memory Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.6/dist-packages/libvirt.py", line 669, in snapshotCreateXML if ret is None:raise libvirtError('virDomainSnapshotCreateXML() failed', dom=self) libvirt.libvirtError: out of memory -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20110516/44c5fad4/attachment.htm>

...works while a guest is paused. > > Is there only way that I turn to freeze/thaw functions? Guest freeze/thaw (virDomainFSFreeze) only works on a live guest. So what you will have to do is: virDomainFSFreeze(vm1, ...) virDomainFSFreeze(vm2, ...) virDomainSuspend(vm1) virDomainSuspend(vm2) virDomainSnapshotCreateXML(vm1, ...) virDomainSnapshotCreateXML(vm2, ...) virDomainResume(vm1) virDomainResume(vm2) virDomainFSThaw(vm1, ...) virDOmainFSThaw(vm2, ...) However, I honestly don't know why you think you need disk snapshots from the same point in time across multiple VMs, though. Compare it to bare metal -...

...1:17 AM, Yuanzhen Gu wrote: >> Guest freeze/thaw (virDomainFSFreeze) only works on a live guest. So >> what you will have to do is: >> >> virDomainFSFreeze(vm1, ...) >> virDomainFSFreeze(vm2, ...) >> virDomainSuspend(vm1) >> virDomainSuspend(vm2) >> virDomainSnapshotCreateXML(vm1, ...) >> virDomainSnapshotCreateXML(vm2, ...) >> virDomainResume(vm1) >> virDomainResume(vm2) >> virDomainFSThaw(vm1, ...) >> virDOmainFSThaw(vm2, ...) >> > > I see, thanks. > >> >> However, I honestly don't know why you think y...

...t = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2620, in snapshotCreateXML if ret is None:raise libvirtError('virDomainSnapshotCreateXML() failed', dom=self) libvirtError: internal error: unable to execute QEMU command 'transaction': Parameter 'encrypt.key-secret' is required for cipher And try adding encryption fields to domainsnapshot, as shown below <?xml version='1.0' encoding='utf-8'?...

Hey When I want to take a snapshot for a Domain by using virDomainSnapshotCreateXML. The Error as below happen: libvir: QEMU error : Requested operation is not valid: Disk '/var/lib/libvirt/images/fedora-qcow.qcow2' does not support snapshotting The snapshot Configuration is : <domainsnapshot> <description>Snapshot of OS install and updates</description&...

...he guest are not of concern. Is it possible to accomplish this? I've looked at both the snapshot/checkpoint and migration APIs and it appears as though the pieces are there, but am having difficulty defining the proper workflow. For instance, an external online checkpoint can be created using virDomainSnapshotCreateXML, but is it possible to disassociate the snapshot from the source domain (effectively returning it to its pre-snapshot state) and at a later time instantiate new domains using the the disk/memory data from the snapshot files? Any recommendations, insight, or guidance is appreciated. Thanks, -Thom...

...g the libvirt command > snapshotCreateXML > > > > with no flag set. Does libvirt support consistent snapshotting or > shall I > > > > rely on QEMU backup new feature only? > > > > > > According to: http://wiki.libvirt.org/page/Snapshots > > > virDomainSnapshotCreateXML is only consistent if the guest is paused > > > during the operation. > > > > > > The new qemu feature is called drive-backup > > > (http://wiki.qemu.org/Features/IncrementalBackup). Unless things > > > changed recently, it is not exposed through libvir...

Thanks for your answer, I am trying to make a snapshot of whole virtual machine (disk, CPU state, memory). But I need to make this snapshot in matter of seconds. I have already try to create snapshot of disk, which is not problem. I use qcow2 format, and create new disk image using original disk image as backing file. But still I am not able to assign state of vm with new disk. I have found

Hi * Trying to get drive-backup command, getting permission denied. :( sudo virsh qemu-monitor-command --hmp my-instance --cmd drive_backup drive-virtio-disk0 /tmp/foo.vda.img Looks like apparmor issue. What can I modify to make this work ? * Couple of other questions drive-backup : * The doc seems to claim that it gives a point in time copy of

...> > do not see any options here. > > I have not yet had time to look into wiring up libvirt to drive the > command; the libvirt solution will probably have the optional ability to > quiesce the file system around the snapshot event, similar to the > existing --quiesce flag of virDomainSnapshotCreateXML (in fact, > virDomainSnaphostCreateXML might even BE the interface we use to wire up > the qemu drive-backup command) > > > * Suppose I have base <-- sn1 --<-- sn2 (QEMU active) . does > > it take data from sn2 only ? or base+sn1+sn2 .. full drive and creates...

2015-05-28 10:10 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > On Thu, May 28, 2015 at 09:48:41AM +0300, NoxDaFox wrote: > > 2015-05-27 15:21 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > > > > > On Wed, May 27, 2015 at 09:38:38AM +0300, NoxDaFox wrote: > > > > * RuntimeError: file receive cancelled by daemon - On r = > > >

...2015 at 10:33:48AM +0300, NoxDaFox wrote: > To create the snapshots I'm using the libvirt command snapshotCreateXML > with no flag set. Does libvirt support consistent snapshotting or shall I > rely on QEMU backup new feature only? According to: http://wiki.libvirt.org/page/Snapshots virDomainSnapshotCreateXML is only consistent if the guest is paused during the operation. The new qemu feature is called drive-backup (http://wiki.qemu.org/Features/IncrementalBackup). Unless things changed recently, it is not exposed through libvirt, so the only way to use it is by sending qemu monitor commands (http://k...

...nion one way how to accomplish my task is to create utility using > theese commands, and create snapshot of vm in RAM - I hope it would be > faster. > > But I wonder whether virsh contains similar functionality, so I won't > need to programm it again. > Yes, virsh wraps the virDomainSnapshotCreateXML() API. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org

...o create the snapshots I'm using the libvirt command snapshotCreateXML > > > with no flag set. Does libvirt support consistent snapshotting or shall I > > > rely on QEMU backup new feature only? > > > > According to: http://wiki.libvirt.org/page/Snapshots > > virDomainSnapshotCreateXML is only consistent if the guest is paused > > during the operation. > > > > The new qemu feature is called drive-backup > > (http://wiki.qemu.org/Features/IncrementalBackup). Unless things > > changed recently, it is not exposed through libvirt, so the only way > &...

...and does it automagically ? I > do not see any options here. I have not yet had time to look into wiring up libvirt to drive the command; the libvirt solution will probably have the optional ability to quiesce the file system around the snapshot event, similar to the existing --quiesce flag of virDomainSnapshotCreateXML (in fact, virDomainSnaphostCreateXML might even BE the interface we use to wire up the qemu drive-backup command) > * Suppose I have base <-- sn1 --<-- sn2 (QEMU active) . does > it take data from sn2 only ? or base+sn1+sn2 .. full drive and creates > a new qcow2 sparse...