From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>,
Juan Quintela <quintela@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] live migration between qemu-kvm 1.0 and 0.15
Date: Thu, 29 Mar 2012 17:25:34 +0200 [thread overview]
Message-ID: <4F747EEE.3050005@redhat.com> (raw)
In-Reply-To: <4F747DDF.5020105@codemonkey.ws>
On 03/29/2012 05:21 PM, Anthony Liguori wrote:
>> Option 1: make -M old force an old vmstate to be written out. Sounds
>> like a generally useful thing.
>> Option 2: ask those consumers to issue updates that bring their code up
>> to version 3. Require fully updated qemus on both sides. Easy to
>> achieve, result is less flexible but reasonable IMO (especially with a
>> long lead time, which we have).
>
>
> I prefer Option 2 presuming the bug is a legitimate bug fix.
>
> If it couldn't be done as a subsection, then there's really no choice
> IMHO.
qemu-kvm already has version 3, so our hand is forced. I too think
option 2 is the best here.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
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: Thu, 29 Mar 2012 17:25:34 +0200 [thread overview]
Message-ID: <4F747EEE.3050005@redhat.com> (raw)
In-Reply-To: <4F747DDF.5020105@codemonkey.ws>
On 03/29/2012 05:21 PM, Anthony Liguori wrote:
>> Option 1: make -M old force an old vmstate to be written out. Sounds
>> like a generally useful thing.
>> Option 2: ask those consumers to issue updates that bring their code up
>> to version 3. Require fully updated qemus on both sides. Easy to
>> achieve, result is less flexible but reasonable IMO (especially with a
>> long lead time, which we have).
>
>
> I prefer Option 2 presuming the bug is a legitimate bug fix.
>
> If it couldn't be done as a subsection, then there's really no choice
> IMHO.
qemu-kvm already has version 3, so our hand is forced. I too think
option 2 is the best here.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-03-29 15:25 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
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 [this message]
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=4F747EEE.3050005@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--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.