virsh save vm_name memdump and then
virsh restore memdump restores a (running) VM all right.
However, a VM is shut off after
virsh save. I'm writing a "live" backup and restore script for KVM VMs, so in the backup part I obviously need a VM running after backup. It's not a problem to do
virsh restore memdump right after backup but it strikes me as essentially unnecessary - I "should" be able to pause a VM, save its memory to a file and then simply resume/unsuspend a VM.
This is not really a problem with VMs that have little memory, but if VM has sizable working memory, then it prolongs backup unnecessarily.
Unfortunately a VM is shut off even if I do
virsh suspend first, before
Is there a way to do this? (i.e. suspend, save, unsuspend)