Re: [Qemu-devel] [PATCH] [RFC] savevm only saves disk state

[Anthony Liguori]

On 09/09/2010 08:43 PM, address@hidden wrote:
> From: edison<address@hidden>
>
> Add a new option when "savevm": savevm -n snapshotName, which only takes 
> snapshot on disk, but doesn't save vm state(memory,cpu,devices...).
> Saving vm state on QCOW2 disk will take a long time, per my test, it will take 1~2 minutes to 
> "savevm" on VM with 1G memory. Even worse, the VM is wholely stopped at that time, makes 
> "savevm" not that useful.
> All we know the side effect of it:) but does it make sense to give user the 
> choice?
>    

I think it would be better to explore ways to make savevm live.  A round 
about option would be to combine a disk-only snapshot with a live 
migration to disk and somehow allow qcow2 to refer to an external memory 
snapshot.

A better alternative would be a live snapshot within qcow2.  I think 
Kevin has some good ideas about how to do this with qcow2 today but 
provided we had a nice interface to do this, the changes to the live 
migration code should be fairly straight forward.

Regards,

Anthony Liguori