From: Paolo Bonzini <pbonzini@redhat.com>
To: "Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Kevin Wolf <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>,
"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: Wed, 05 Mar 2014 10:09:06 +0100 [thread overview]
Message-ID: <5316E9B2.3050208@redhat.com> (raw)
In-Reply-To: <615092B2FD0E7648B6E4B43E029BCFB84D57B3C4@SZXEMA503-MBS.china.huawei.com>
Il 05/03/2014 02:00, Huangpeng (Peter) ha scritto:
>>> One question:
>>> Can post-copy fallback if exceptions happen during post-copy?
>>
>> What do you mean by 'exceptions' here? Generally postcopy can't fall back to
>> precopy because once you're in postcopy mode the state is split between the
>> two machines.
>
> Like destination VM interrupted due to memory-copy error or other exceptions,
> with pre-copy scheme, we can fall-back to the source-vm.
No, postcopy cannot do that.
However, this is a limitation of postcopy, not of the kernel interfaces
that Andrea is adding. If you use those interfaces to implement live VM
point-in-time snapshots, you can drop the snapshotting operation safely
and keep the VM running.
> One simple question(may be discussed before), what kind of scenario does post-copy
> aim for?
Mostly cases where pre-copy migration doesn't converge because the guest
is too big, or when you require a really, really small downtime.
It can be useful when you have to evacuate a host as fast as possible
(due to detecting an intrusion or impending hardware failure), because
the alternative is to shutdown the VM immediately. It can also be used
for upgrading QEMU on the host where the VM is running; in this case you
can use a Unix socket for transport, and eliminate the chance of
migration failing due to a network problem.
Paolo
next prev parent reply other threads:[~2014-03-05 9:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 1:13 [Qemu-devel] [RFC]VM live snapshot proposal Huangpeng (Peter)
2014-03-03 12:32 ` Stefan Hajnoczi
2014-03-03 12:55 ` Kevin Wolf
2014-03-03 13:19 ` Paolo Bonzini
2014-03-03 13:30 ` Kevin Wolf
2014-03-03 13:47 ` Paolo Bonzini
2014-03-03 14:04 ` Kevin Wolf
2014-03-03 14:55 ` Dr. David Alan Gilbert
2014-03-03 19:52 ` Andrea Arcangeli
2014-03-04 1:35 ` Huangpeng (Peter)
2014-03-05 14:46 ` Andrea Arcangeli
2014-03-05 1:52 ` Huangpeng (Peter)
2014-03-05 14:55 ` Andrea Arcangeli
2014-03-04 1:28 ` Huangpeng (Peter)
2014-03-04 9:40 ` Dr. David Alan Gilbert
2014-03-05 1:00 ` Huangpeng (Peter)
2014-03-05 9:09 ` Paolo Bonzini [this message]
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-03 13:18 ` Paolo Bonzini
2014-03-04 1:02 ` Huangpeng (Peter)
2014-03-04 8:54 ` Stefan Hajnoczi
2014-03-04 9:05 ` Paolo Bonzini
2014-03-04 11:28 ` Wenchao Xia
2014-03-05 0:46 ` 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=5316E9B2.3050208@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@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 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).