search for: memspec

...; </disks> > Ah, that makes sense, thanks so much for clearing this up! > > > > Also, while looking at the manpage, does the --live option do anything > > different if used with the above command? > > --live only makes sense when mixed with memory snapshots (with --memspec); but > as you are doing a --disk-only snapshot, it doesn't help (I'm not sure if it > will error out as mutually exclusive or just be silently ignored, > without reading the code). I'm using this code in a script for creating live backups of VMs - would it make sense to includ...

...e improvements). Some of these new approaches may provide enough additional efficiency over the older methods that they are worth upgrading for - but if you can get things working to your needs with an older version, great. >> --live only makes sense when mixed with memory snapshots (with --memspec); but >> as you are doing a --disk-only snapshot, it doesn't help (I'm not sure if it >> will error out as mutually exclusive or just be silently ignored, >> without reading the code). > I'm using this code in a script for creating live backups of VMs - would it mak...

> >> --live only makes sense when mixed with memory snapshots (with --memspec); > >> but > >> as you are doing a --disk-only snapshot, it doesn't help (I'm not sure if > >> it > >> will error out as mutually exclusive or just be silently ignored, > >> without reading the code). > > I'm using this code in a script...

Hello, I am working on a script to automatically create live snapshots of running VMs using qemu-kvm 1.4.0 and libvirt 1.0.2. If a VM has multiple disks, I'd like to back them up individually with separate calls to snapshot-create-as, so I can more easily manage the disk images. The code I have now is essentially as follows: virsh snapshot-create-as --domain "vmname" --name

Hi all, I was trying to take live snapshot of VMs, but I got the following error: [root@localhost ~]# virsh snapshot-create-as 1 test desc --live --memspec file=mem.bak,snapshot=external --diskspec vda,snapshot=external,file=/root/root.bak.qcow2 error: Operation not supported: live disk snapshot not supported with this QEMU binary I upgraded my qemu-kvm 0.12.1 to qemu 1.2, the error still exists. Is this really the problem of my qemu version or I did...

...oes anyone know how I could > > achieve the above? > > With 'virsh', you _can_ save the live disk and memory state: > > $ virsh snapshot-create-as \ > --domain myvm snap1 \ > --diskspec vda,file=./disk-snap.qcow2,snapshot=external \ > --memspec file=./mem-snap.qcow2,snapshot=external \ > --atomic > > > -- > /kashyap >

...what we want. Since we are using libvirt to manage different >> VMs, could you give us some specific guides (or references) that how >> we could migrate memory state to file using virsh interfaces and do >> external snapshots? > > virsh snapshot-create-as $dom $name --live --memspec /path/to/memoryfile I have tried this command on libvirt v1.1.3 and it returns "error: invalid argument: qemuDomainSnapshotCreateXML: unsupported flags (0x100)". Looks like --live is not supported yet. Could you let us know which version we should of libvirt we should use in order to use...

Hi, My use case involves creating duplicates of saved virtual machines. Tried with virt-manager and with virsh but so far it seems like this case is not supported by these tools. Does anyone know how I could achieve the above? Thanks, Michael

...snapshots to restore it? I suppose I would also periodically merge the snapshots back into the a single snapshot to ease the process? # virsh snapshot-create-as --domain dave-win10a win10a-state01 --diskspec vda,file=/var/lib/libvirt/images/vm_snapshots/disk-overlay.qcow2,snapshot=external --memspec file=/var/lib/libvirt/images/vm_snapshots/mem-overlay.qcow2,snapshot=external --atomic Domain snapshot win10a-state01 created # ls -lh vm_snapshots/ total 3.3G -rw------- 1 qemu qemu 196K Jul 11 12:32 disk-overlay.qcow2 -rw------- 1 root root 3.3G Jul 11 12:32 mem-overlay.qcow2 Thanks, Alex

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

...sers@redhat.com > Onderwerp: [libvirt-users] Can't take live snapshot, not supported with this > QEMU binary > > Hi all, > > I was trying to take live snapshot of VMs, but I got the following error: > > [root@localhost ~]# virsh snapshot-create-as 1 test desc --live --memspec > file=mem.bak,snapshot=external --diskspec > vda,snapshot=external,file=/root/root.bak.qcow2 > error: Operation not supported: live disk snapshot not supported with this > QEMU binary > > I upgraded my qemu-kvm 0.12.1 to qemu 1.2, the error still exists. Is this really > the...

...shot option in source tag, and that I need to pre-create this snapshot using rbd so the vm can start. But then I tried: # virsh snapshot-create-as vm-test error: unsupported configuration: internal snapshot for disk vda unsupported for storage type raw # virsh snapshot-create-as vm-test snap1 --memspec file=/tmp/vm-test.mem --diskspec vda,snapshot=internal error: unsupported configuration: internal snapshot for disk vda unsupported for storage type raw # virsh snapshot-create-as vm-test snap1 --disk-only --atomic --diskspec vda,snapshot=internal error: unsupported configuration: active qemu doma...

...se is not supported by these tools. Does anyone know how I could > achieve the above? With 'virsh', you _can_ save the live disk and memory state: $ virsh snapshot-create-as \ --domain myvm snap1 \ --diskspec vda,file=./disk-snap.qcow2,snapshot=external \ --memspec file=./mem-snap.qcow2,snapshot=external \ --atomic -- /kashyap

...hem here: `man virsh`). [...] > > With 'virsh', you _can_ save the live disk and memory state: > > > > $ virsh snapshot-create-as \ > > --domain myvm snap1 \ > > --diskspec vda,file=./disk-snap.qcow2,snapshot=external \ > > --memspec file=./mem-snap.qcow2,snapshot=external \ > > --atomic > > > > > > -- > > /kashyap > > -- /kashyap

Everyone, I am trying to create external snapshots of a kvm guest machine and have not been able to do so. In accordance with : https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-troubleshooting-workaround_for_creating_external_snapshots_with_libvirt I have used the command line : snapshot-create-as --diskspec

what the difference between ` virsh save ` and `virsh snapshot`? are they all used for backup for vm?have any details articles to introduce vm bakcup or image bakcup with libvirt? thanks in advance. liuzhijun -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20121112/931d27a2/attachment.htm>

...memory image is stored >> separately), but the support for external snapshots isn't finished yet >> (they can't be reverted automatically). > > How can I create an external snapshot? Add '--disk-only' for an offline domain, or use 'virsh snapshot-create-as --memspec' instead of 'snapshot-create' for an online guest (you can also use snapshot-create for an external snapshot, but you have to write appropriate XML for the case, rather than relying on the no-arg option that provides a default XML for an internal snapshot; so I find snapshot-create-as a...

[dropping qemu-devel] On 10/28/2013 11:30 AM, Xinyang Ge wrote: >> virsh snapshot-create-as $dom $name --live --memspec /path/to/memoryfile > > I have tried this command on libvirt v1.1.3 and it returns "error: > invalid argument: qemuDomainSnapshotCreateXML: unsupported flags > (0x100)". Looks like --live is not supported yet. Could you let us > know which version we should of libvirt we s...

On 10/28/2013 12:12 PM, Xinyang Ge wrote: >>> That's odd, because we have supported --live since 1.0.5. Are you sure >>> you are running the right libvirtd version and not just reporting the >>> version of your virsh? >> >> You are right. I am running an old libvirtd but with a new virsh. It >> works now! Thank you so much! > > Another

...operation takes as long as a migration to file, but the guest continues to operate throughout that phase. The actual guest downtime is a mere fraction of a second at the point where the disk snapshots are taken once the migration to file completed. virsh snapshot-create-as $dom $snapname --live --memspec /path/to/file will store the memory state into /path/to/file, and create an external disk snapshot of each disk (you may need to use the --diskspec option if you want to control the filenames of those disk snapshots). > > I have already try to create snapshot of disk, which is not problem...