From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] More robust migration
Date: Fri, 20 Feb 2009 16:47:26 +0000 [thread overview]
Message-ID: <200902201647.27138.paul@codesourcery.com> (raw)
In-Reply-To: <20090220163820.GC9726@shareable.org>
On Friday 20 February 2009, Jamie Lokier wrote:
> Paul Brook wrote:
> > I suspect that in practice live migration of a VM between different qemu
> > versions ends up comparable to in-place live kernel upgrades. i.e. it
> > takes an awful lot of work and care to make it happen, and in practice
> > isn't going to happen for any particularly useful span of versions.
>
> On the other hand, stored snapshots of guests which are ready to run
> in a particular state are quite useful. I'm under the impression the
> migration code is/will be useful for storing snapshots of system (not
> disk) state too. Is that right?
I don't think there's any real difference between snapshotting and migration
in this case. It's basically the same code.
I'm not saying it's a useless feature, just that it's very extremely to do
reliably, and for that reason unlikely to happen. An unreliable
implementation (i.e. one that claims to migrate/snapshot, then breaks some of
the time) is IMHO worse than nothing.
Paul
next prev parent reply other threads:[~2009-02-20 16:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 14:36 [Qemu-devel] [RFC] More robust migration Andre Przywara
2009-02-20 15:15 ` Anthony Liguori
2009-02-20 16:09 ` Paul Brook
2009-02-20 16:38 ` Jamie Lokier
2009-02-20 16:47 ` Paul Brook [this message]
2009-02-23 3:51 ` Jamie Lokier
2009-02-23 11:55 ` Paul Brook
2009-02-23 22:07 ` Jamie Lokier
2009-02-23 23:21 ` Paul Brook
2009-02-24 1:15 ` Anthony Liguori
2009-02-24 10:18 ` Avi Kivity
2009-02-20 16:37 ` Jamie Lokier
2009-02-20 18:27 ` Anthony Liguori
2009-02-20 17:06 ` [Qemu-devel] " Charles Duffy
2009-02-23 3:54 ` Jamie Lokier
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=200902201647.27138.paul@codesourcery.com \
--to=paul@codesourcery.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 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).