I'm in the middle of a VirtualBox/phpVirtualBox -> KVM/Kimchi migration for a small company with tens of VMs, mostly build slaves. One thing we miss from VirtualBox is the possibility to save/restore a VM. This is akin to suspending a VM, as it saves to disk the content of the guest's RAM and frees RAM for the host.
I just found out libvirt has support for this, have tested it with virsh save and virsh restore, works as expected. It would be nice to have Kimchi expose this to users via the pull-down menu of each guest. Basically, for a running guest, there should be a Save state entry to save the running image. Then for saved guests, there should be two entries: Restore saved state and Discard saved state (the last one for forcing a clean start).
Hi,
And thanks for Kimchi!
I'm in the middle of a VirtualBox/phpVirtualBox -> KVM/Kimchi migration for a small company with tens of VMs, mostly build slaves. One thing we miss from VirtualBox is the possibility to save/restore a VM. This is akin to suspending a VM, as it saves to disk the content of the guest's RAM and frees RAM for the host.
I just found out libvirt has support for this, have tested it with
virsh saveandvirsh restore, works as expected. It would be nice to have Kimchi expose this to users via the pull-down menu of each guest. Basically, for a running guest, there should be a Save state entry to save the running image. Then for saved guests, there should be two entries: Restore saved state and Discard saved state (the last one for forcing a clean start).What do you think?