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: Tue, 27 Mar 2012 18:46:36 +0200 Message-ID: <4F71EEEC.5000903@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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , Vasilis Liaskovitis , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" , Juan Quintela To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:50318 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753634Ab2C0Qqp (ORCPT ); Tue, 27 Mar 2012 12:46:45 -0400 In-Reply-To: <4F71ED3F.4030809@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: 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? > 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). -- error compiling committee.c: too many arguments to function