From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] live migration between qemu-kvm 1.0 and 0.15
Date: Tue, 27 Mar 2012 11:49:47 -0500 [thread overview]
Message-ID: <4F71EFAB.4070304@codemonkey.ws> (raw)
In-Reply-To: <4F71EEEC.5000903@redhat.com>
On 03/27/2012 11:46 AM, Avi Kivity wrote:
> On 03/27/2012 06:39 PM, Anthony Liguori wrote:
>>
>> 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.
>
> Agree strongly.
>
>>
>> My expectation is that migration works from:
>>
>> qemu-1.0 -M 1.0 => qemu-1.1 -M 1.1
>
> Why do you expect that? Maybe you meant -M 1.0 at the end?
Sorry, I did mean -M 1.0.
>
>> 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
>>
>
> Ack.
>
>> I'm okay if this fails gracefully:
>>
>> qemu-1.1 -M 0.15<= qemu-0.15 -M 0.15
>
> RHEL has more stringent requirements (going back to its heavily patched
> 0.12). I think we should have the infrastructure that allow one to add
> the hacks to make this work, even if we don't actually do the compat
> work for the release (I think it's fine for qemu to support just one
> version going back; and unreasonable to require it to go as far back as
> RHEL).
This is reasonable to me.
Regards,
Anthony Liguori
>
next prev parent reply other threads:[~2012-03-27 16:49 UTC|newest]
Thread overview: 29+ 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 8:55 ` [Qemu-devel] " Vasilis Liaskovitis
2012-03-27 9:55 ` Jan Kiszka
2012-03-27 9:55 ` [Qemu-devel] " Jan Kiszka
2012-03-27 15:59 ` Avi Kivity
2012-03-27 15:59 ` [Qemu-devel] " Avi Kivity
2012-03-27 16:22 ` Jan Kiszka
2012-03-27 16:22 ` [Qemu-devel] " Jan Kiszka
2012-03-27 16:39 ` Anthony Liguori
2012-03-27 16:39 ` Anthony Liguori
2012-03-27 16:46 ` Avi Kivity
2012-03-27 16:46 ` Avi Kivity
2012-03-27 16:49 ` Anthony Liguori [this message]
2012-03-27 17:42 ` Jan Kiszka
2012-03-27 17:42 ` Jan Kiszka
2012-03-29 15:23 ` Anthony Liguori
2012-03-29 15:23 ` [Qemu-devel] " Anthony Liguori
2012-03-29 15:53 ` Jan Kiszka
2012-03-29 15:53 ` [Qemu-devel] " Jan Kiszka
2012-03-29 11:56 ` Jan Kiszka
2012-03-29 11:56 ` Jan Kiszka
2012-03-29 15:17 ` Avi Kivity
2012-03-29 15:17 ` Avi Kivity
2012-03-29 15:21 ` Anthony Liguori
2012-03-29 15:21 ` Anthony Liguori
2012-03-29 15:25 ` Avi Kivity
2012-03-29 15:25 ` Avi Kivity
2012-04-02 14:17 ` Markus Armbruster
2012-04-02 14:17 ` [Qemu-devel] " Markus Armbruster
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=4F71EFAB.4070304@codemonkey.ws \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.