From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: quintela@redhat.com
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Pavel Hrdina <phrdina@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Dietmar Maurer <dietmar@proxmox.com>
Subject: Re: [Qemu-devel] [RFC] lively write vmstate with predictable size
Date: Sat, 05 Jan 2013 16:21:14 +0800 [thread overview]
Message-ID: <50E7E27A.8050209@linux.vnet.ibm.com> (raw)
In-Reply-To: <87623ca7up.fsf@elfo.mitica>
于 2013-1-5 6:42, Juan Quintela 写道:
> Stefan Hajnoczi <stefanha@gmail.com> wrote:
>> On Fri, Dec 21, 2012 at 10:25:51AM +0800, Wenchao Xia wrote:
>>> resent the mail to mail-list.
>>> -------------------
>>>
>>> Hi, Paolo and Juan
>>> Currently savevm needs pause vm, and I am working on that make it
>>> lively.
>>
>> What is the benefit over migrating to file? I thought we can already do
>> that today?
>
> Load is faster.
>
> He wants to "overwrite" the memory, so, if we dirty one page during
> migration, it overwrite it, instead of having two copies that only make
> the image bigger and slower to load. Problem is that we need a new
> "format" to be able to do that.
>
> Later, Juan.
>
I guess migration to file makes vm stopped, and lack a step
to take snapshot in the end of migration, also the usage seems
strange makes me feel something is lacking. I'd like to
have:
1 take blk snapshot internal/external lively.
2 take vmstate snapshot internal/external lively.
3 combination.
--
Best Regards
Wenchao Xia
next prev parent reply other threads:[~2013-01-05 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50D2CC22.1060900@linux.vnet.ibm.com>
2012-12-21 2:25 ` [Qemu-devel] [RFC] lively write vmstate with predictable size Wenchao Xia
2012-12-21 18:36 ` Juan Quintela
2012-12-25 5:07 ` Wenchao Xia
2012-12-27 2:40 ` Wenchao Xia
2013-01-04 17:35 ` Stefan Hajnoczi
2013-01-04 22:42 ` Juan Quintela
2013-01-05 8:21 ` Wenchao Xia [this message]
2013-01-06 3:28 ` Eric Blake
2013-01-07 12:35 ` Stefan Hajnoczi
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=50E7E27A.8050209@linux.vnet.ibm.com \
--to=xiawenc@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=dietmar@proxmox.com \
--cc=pbonzini@redhat.com \
--cc=phrdina@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).