From: Anthony Liguori <anthony@codemonkey.ws>
To: disheng.su@gmail.com
Cc: qemu-devel@nongnu.org, edison <edison@cloud.com>
Subject: Re: [Qemu-devel] [PATCH] [RFC] savevm only saves disk state
Date: Thu, 09 Sep 2010 21:08:28 -0500 [thread overview]
Message-ID: <4C89931C.1010605@codemonkey.ws> (raw)
In-Reply-To: <1284083014-8198-1-git-send-email-disheng.su@gmail.com>
On 09/09/2010 08:43 PM, disheng.su@gmail.com wrote:
> From: edison<edison@cloud.com>
>
> 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
next prev parent reply other threads:[~2010-09-10 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 1:43 [Qemu-devel] [PATCH] [RFC] savevm only saves disk state disheng.su
2010-09-10 2:08 ` Anthony Liguori [this message]
2010-09-15 18:24 ` edison
2010-09-16 10:03 ` Kevin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C89931C.1010605@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=disheng.su@gmail.com \
--cc=edison@cloud.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.