From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Huangpeng (Peter)" <peter.huangpeng@huawei.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>,
Paolo Bonzini <pbonzini@redhat.com>,
Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC]VM live snapshot proposal
Date: Tue, 4 Mar 2014 09:40:32 +0000 [thread overview]
Message-ID: <20140304094031.GC2711@work-vm> (raw)
In-Reply-To: <615092B2FD0E7648B6E4B43E029BCFB84D57953F@SZXEMA503-MBS.china.huawei.com>
* Huangpeng (Peter) (peter.huangpeng@huawei.com) wrote:
> > > I think this is different in the same way that block-backup and
> > > block-mirror are different. Huangpeng's proposal would let you make a
> > > consistent snapshot of disks and RAM.
> >
> > Right. Though the point isn't about consistency (doing the disk snapshot when
> > memory has converged would be consistent as well), but about having the
> > snapshot semantically right at the time when the monitor command is issued
> > instead of only starting it then and being consistent at the point of completion.
> >
> > This is indeed like pre/post-copy live migration, and probably both options have
> > their uses. I would suggest starting with the easy one, and adding the
> > post-copy feature on top.
> >
>
> Good suggestion, The latest patches of post-copy seems updated 2 years ago.
> https://github.com/yamahata/qemu
I'm working on post-copy at the moment, using Andrea's kernel code,
using bits of Yamahata's code base as well; hopefully it won't
be too long until we have something to post.
> 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.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-03-04 9:40 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 [this message]
2014-03-05 1:00 ` Huangpeng (Peter)
2014-03-05 9:09 ` Paolo Bonzini
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=20140304094031.GC2711@work-vm \
--to=dgilbert@redhat.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 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).