From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] live migration between qemu-kvm 1.0 and 0.15 Date: Thu, 29 Mar 2012 17:25:34 +0200 Message-ID: <4F747EEE.3050005@redhat.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , Vasilis Liaskovitis , Juan Quintela , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:5224 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933179Ab2C2PZm (ORCPT ); Thu, 29 Mar 2012 11:25:42 -0400 In-Reply-To: <4F747DDF.5020105@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: 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