search for: quiese

...; >> without reading the code). > > I'm using this code in a script for creating live backups of VMs - would it > > make > > sense to include --memspec to capture the memory state so that an fsck on > > boot > > isn't necessary? I remember you explained --quiese awhile back: > > https://www.redhat.com/archives/libvirt-users/2013-February/msg00020.html > > --memspec and --quiesce are orthogonal, you only need one or the other > (in fact, they do NOT work together in the current implementation). > --memspec says to capture the domain memor...

...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 include --memspec to capture the memory state so that an fsck on boot isn't necessary? I remember you explained --quiese awhile back: https://www.redhat.com/archives/libvirt-users/2013-February/msg00020.html However I don't have qemu-guest-agent installed on the guests, so would using --memspec instead of --disk-only produce a snapshot that is consistent (since it would "resume" with the same memory st...

...nks, that was a helpful overview. To clarify, block commit is changing the backing files,but even though it is doing that, the data is consistent even if it is interrupted? Reviewing the presentation brought up another question. I have been thinking about installing qemu-guest-agent so I can use --quiese with snapshot-create-as, however I have a couple of questions: * does the guest agent always report back to libvirt on the host if it succeeds, fails, or has an error when attempting to sync(2)? * isn't it a security risk to allow the guest the ability to communicate to the host via the guest a...

...Intermediate backing files may have contents that don't correspond to any historical state seen by the guest, but the guest view is never compromised. > > Reviewing the presentation brought up another question. I have been thinking > about installing qemu-guest-agent so I can use --quiese with snapshot-create-as, > however I have a couple of questions: > * does the guest agent always report back to libvirt on the host if it succeeds, > fails, or has an error when attempting to sync(2)? Guest agents only work if you can trust the guest (a malicious guest could just lie), bu...

...ew Martin wrote: >> --quiesce requires the guest to be running to work, while --memspec >> forceably stops the guest (the migration algorithm must pause, even if >> --live minimizes the pause to a fraction of a second). > Would calling snapshot-create-as with --disk-only and --quiese still succeed > on a VM that is stopped (since the disk would already be consistent, it would > just call "qemu-img create")? For an offline guest, --disk-only makes no difference (there is no memory to worry about); and you are correct that the disk is consistent (assuming the OS...

...clusive 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 include --memspec to capture the memory state so that an fsck on boot > isn't necessary? I remember you explained --quiese awhile back: > https://www.redhat.com/archives/libvirt-users/2013-February/msg00020.html --memspec and --quiesce are orthogonal, you only need one or the other (in fact, they do NOT work together in the current implementation). --memspec says to capture the domain memory state (migrate to file;...

Hello, I use snapshot-create-as followed by blockpull when creating external snapshots of VMs. This works well, however I am curious about the behavior of blockpull after an unexpected shutdown (or SIGKILL). If a blockpull is in progress and an unexpected power loss occurs, will the VM continue to reference the backing file for the parts of it that have not yet been copied? Or, will will the disk

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