From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] More robust migration
Date: Mon, 23 Feb 2009 11:55:08 +0000 [thread overview]
Message-ID: <200902231155.09093.paul@codesourcery.com> (raw)
In-Reply-To: <20090223035140.GA23719@shareable.org>
On Monday 23 February 2009, Jamie Lokier wrote:
> Paul Brook wrote (about resuming snapshots on a different QEMU):
> > 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.
>
> Well, one which cannot resume from a snapshot at all unless you have
> the original host and original QEMU/KVM around is pretty bad.
I never said you need the same host. All the save/restore code should be host
independent. It should be possible to save state on (say) i386 and restore on
ppc64. Anything that prevents this is IMO a bug.
For KVM you're likely to need a cpu with at least as many features as the old
one, but that's the price you pay for using host hardware features.
However different versions of qemu (i.e. qemu built from different sources)
are a different question altogether. If you can't reproduce your old qemu
binaries you have much larger problems.
Paul
next prev parent reply other threads:[~2009-02-23 11:55 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
2009-02-23 3:51 ` Jamie Lokier
2009-02-23 11:55 ` Paul Brook [this message]
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=200902231155.09093.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).