From: Wenchao Xia <wenchaoqemu@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
"kwolf@redhat.com" <kwolf@redhat.com>,
Pavel Hrdina <phrdina@redhat.com>,
Zhanghailiang <zhang.zhanghailiang@huawei.com>,
KVM devel mailing list <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC]VM live snapshot proposal
Date: Tue, 04 Mar 2014 19:28:10 +0800 [thread overview]
Message-ID: <5315B8CA.8010408@gmail.com> (raw)
In-Reply-To: <5315976B.5070608@redhat.com>
于 2014/3/4 17:05, Paolo Bonzini 写道:
> Il 04/03/2014 09:54, Stefan Hajnoczi ha scritto:
>>> Is there any other proposals to implement vm-snapshot?
>> See the discussion by Paolo and Andrea about post-copy migration, which
>> adds kernel memory management features for tracking userspace page
>> faults. Perhaps you can use that infrastructure to trap guest writes.
>
> That infrastructure actually traps guest reads too. But it's fine, as
> they are a superset of guest writes and the image will still be
> consistent.
>
> Paolo
>
I heard that Kernel going to have API to let userspace catch memory
operation, which originally
can be only caught by kernel code. I am not sure how it is now, but if
kernel have it, qemu
can use it more gracefully than modifing migration code.
WARNING: multiple messages have this Message-ID (diff)
From: Wenchao Xia <wenchaoqemu@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
Pavel Hrdina <phrdina@redhat.com>,
Zhanghailiang <zhang.zhanghailiang@huawei.com>,
KVM devel mailing list <kvm@vger.kernel.org>,
Stefan Hajnoczi <stefanha@gmail.com>,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC]VM live snapshot proposal
Date: Tue, 04 Mar 2014 19:28:10 +0800 [thread overview]
Message-ID: <5315B8CA.8010408@gmail.com> (raw)
In-Reply-To: <5315976B.5070608@redhat.com>
于 2014/3/4 17:05, Paolo Bonzini 写道:
> Il 04/03/2014 09:54, Stefan Hajnoczi ha scritto:
>>> Is there any other proposals to implement vm-snapshot?
>> See the discussion by Paolo and Andrea about post-copy migration, which
>> adds kernel memory management features for tracking userspace page
>> faults. Perhaps you can use that infrastructure to trap guest writes.
>
> That infrastructure actually traps guest reads too. But it's fine, as
> they are a superset of guest writes and the image will still be
> consistent.
>
> Paolo
>
I heard that Kernel going to have API to let userspace catch memory
operation, which originally
can be only caught by kernel code. I am not sure how it is now, but if
kernel have it, qemu
can use it more gracefully than modifing migration code.
next prev parent reply other threads:[~2014-03-04 11:28 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 1:13 [RFC]VM live snapshot proposal Huangpeng (Peter)
2014-03-03 1:13 ` [Qemu-devel] " Huangpeng (Peter)
2014-03-03 12:32 ` Stefan Hajnoczi
2014-03-03 12:32 ` [Qemu-devel] " Stefan Hajnoczi
2014-03-03 12:55 ` Kevin Wolf
2014-03-03 12:55 ` [Qemu-devel] " Kevin Wolf
2014-03-03 13:19 ` Paolo Bonzini
2014-03-03 13:19 ` [Qemu-devel] " Paolo Bonzini
2014-03-03 13:30 ` Kevin Wolf
2014-03-03 13:30 ` [Qemu-devel] " Kevin Wolf
2014-03-03 13:47 ` Paolo Bonzini
2014-03-03 13:47 ` [Qemu-devel] " Paolo Bonzini
2014-03-03 14:04 ` Kevin Wolf
2014-03-03 14:04 ` [Qemu-devel] " Kevin Wolf
2014-03-03 14:55 ` Dr. David Alan Gilbert
2014-03-03 14:55 ` Dr. David Alan Gilbert
2014-03-03 19:52 ` Andrea Arcangeli
2014-03-03 19:52 ` [Qemu-devel] " Andrea Arcangeli
2014-03-04 1:35 ` Huangpeng (Peter)
2014-03-04 1:35 ` [Qemu-devel] " Huangpeng (Peter)
2014-03-05 14:46 ` Andrea Arcangeli
2014-03-05 14:46 ` [Qemu-devel] " Andrea Arcangeli
2014-03-05 1:52 ` Huangpeng (Peter)
2014-03-05 1:52 ` [Qemu-devel] " Huangpeng (Peter)
2014-03-05 14:55 ` Andrea Arcangeli
2014-03-05 14:55 ` [Qemu-devel] " Andrea Arcangeli
2014-03-04 1:28 ` Huangpeng (Peter)
2014-03-04 1:28 ` [Qemu-devel] " Huangpeng (Peter)
2014-03-04 9:40 ` Dr. David Alan Gilbert
2014-03-04 9:40 ` Dr. David Alan Gilbert
2014-03-05 1:00 ` Huangpeng (Peter)
2014-03-05 1:00 ` Huangpeng (Peter)
2014-03-05 9:09 ` Paolo Bonzini
2014-03-06 1:42 ` Huangpeng (Peter)
2014-03-06 1:42 ` Huangpeng (Peter)
2014-03-06 9:14 ` Dr. David Alan Gilbert
2014-03-04 1:06 ` Huangpeng (Peter)
2014-03-04 1:06 ` [Qemu-devel] " Huangpeng (Peter)
2014-03-03 13:18 ` Paolo Bonzini
2014-03-03 13:18 ` [Qemu-devel] " Paolo Bonzini
2014-03-04 1:02 ` Huangpeng (Peter)
2014-03-04 1:02 ` [Qemu-devel] " Huangpeng (Peter)
2014-03-04 8:54 ` Stefan Hajnoczi
2014-03-04 8:54 ` [Qemu-devel] " Stefan Hajnoczi
2014-03-04 9:05 ` Paolo Bonzini
2014-03-04 9:05 ` [Qemu-devel] " Paolo Bonzini
2014-03-04 11:28 ` Wenchao Xia [this message]
2014-03-04 11:28 ` Wenchao Xia
2014-03-05 0:46 ` Huangpeng (Peter)
2014-03-05 0:46 ` [Qemu-devel] " Huangpeng (Peter)
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=5315B8CA.8010408@gmail.com \
--to=wenchaoqemu@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=phrdina@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=xiawenc@linux.vnet.ibm.com \
--cc=zhang.zhanghailiang@huawei.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 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.