From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:35144)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1SDHEQ-0008TW-6z
	for qemu-devel@nongnu.org; Thu, 29 Mar 2012 11:25:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1SDHEJ-0005te-Sp
	for qemu-devel@nongnu.org; Thu, 29 Mar 2012 11:25:45 -0400
Received: from mx1.redhat.com ([209.132.183.28]:29944)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1SDHEJ-0005tY-KH
	for qemu-devel@nongnu.org; Thu, 29 Mar 2012 11:25:39 -0400
Message-ID: <4F747EEE.3050005@redhat.com>
Date: Thu, 29 Mar 2012 17:25:34 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <20120327085521.GA4567@dhcp-192-168-178-175.profitbricks.localdomain>
	<4F718E8B.5090601@siemens.com> <4F71E3CC.9070103@redhat.com>
	<4F71E95C.3070100@siemens.com> <4F71ED3F.4030809@codemonkey.ws>
	<4F744E00.9020901@siemens.com> <4F747CF4.3040503@redhat.com>
	<4F747DDF.5020105@codemonkey.ws>
In-Reply-To: <4F747DDF.5020105@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] live migration between qemu-kvm 1.0 and 0.15
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

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