From: Markus Armbruster <armbru@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>,
Avi Kivity <avi@redhat.com>
Subject: Re: live migration between qemu-kvm 1.0 and 0.15
Date: Mon, 02 Apr 2012 16:17:32 +0200 [thread overview]
Message-ID: <m3fwcmjk03.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <4F71ED3F.4030809@codemonkey.ws> (Anthony Liguori's message of "Tue, 27 Mar 2012 11:39:27 -0500")
Anthony Liguori <anthony@codemonkey.ws> writes:
> So, since we're approaching 1.1, we should really discuss release
> criteria for 1.1 with respect to live migration. I'd prefer to avoid
> surprises in this release.
>
> My expectation is that migration works from:
>
> qemu-1.0 -M 1.0 => qemu-1.1 -M 1.1
> qemu-1.1 -M 1.0 <= qemu-1.1 -M 1.0
>
> I would expect that migration works from:
>
> qemu-0.15 -M 0.15 => qemu-1.1 -M 0.15
>
> I'm okay if this fails gracefully:
>
> qemu-1.1 -M 0.15 <= qemu-0.15 -M 0.15
Until we have tools to mechanically verify migratability, such
expecations will remain just that: expectations :)
Vmstate describes the migration format (sort of), vmstate is data,
computers can process data, so at least some mechanical verification
should be possible, shouldn't it? And even something that can only
disprove migratability, but not prove it, could be incredibly useful.
prev parent reply other threads:[~2012-04-02 14:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 8:55 live migration between qemu-kvm 1.0 and 0.15 Vasilis Liaskovitis
2012-03-27 9:55 ` Jan Kiszka
2012-03-27 15:59 ` Avi Kivity
2012-03-27 16:22 ` Jan Kiszka
2012-03-27 16:39 ` [Qemu-devel] " Anthony Liguori
2012-03-27 16:46 ` Avi Kivity
2012-03-27 16:49 ` Anthony Liguori
2012-03-27 17:42 ` Jan Kiszka
2012-03-29 15:23 ` Anthony Liguori
2012-03-29 15:53 ` Jan Kiszka
2012-03-29 11:56 ` [Qemu-devel] " Jan Kiszka
2012-03-29 15:17 ` Avi Kivity
2012-03-29 15:21 ` Anthony Liguori
2012-03-29 15:25 ` Avi Kivity
2012-04-02 14:17 ` Markus Armbruster [this message]
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=m3fwcmjk03.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=vasilis.liaskovitis@profitbricks.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