Received: from eggs.gnu.org ([2001:4830:134:3::10]:44128) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wkw0W-0005hd-Jy for qemu-devel@nongnu.org; Thu, 15 May 2014 09:47:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wkw0P-0007Xb-03 for qemu-devel@nongnu.org; Thu, 15 May 2014 09:47:36 -0400 Received: from mx1.redhat.com ([209.132.183.28]:4053) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wkw0O-0007XX-OF for qemu-devel@nongnu.org; Thu, 15 May 2014 09:47:28 -0400 From: Markus Armbruster References: <20140515062351.GB14456@redhat.com> <20140515064635.GB31192@grmbl.mre> <20140515090449.2db0cbe0@bahia.local> <537486D2.1060609@suse.de> <20140515095208.GB16405@redhat.com> <53748FC1.5010702@suse.de> <20140515100309.GA22407@redhat.com> <537492C0.9030100@suse.de> <20140515101651.GB22512@redhat.com> <5374AC4F.4000507@suse.de> <20140515122052.GA23018@redhat.com> Date: Thu, 15 May 2014 15:47:20 +0200 In-Reply-To: <20140515122052.GA23018@redhat.com> (Michael S. Tsirkin's message of "Thu, 15 May 2014 15:20:52 +0300") Message-ID: <87siob6tnb.fsf@blackfin.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH RFC 1/8] virtio: add subsections to the migration stream List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Kevin Wolf , Fam Zheng , Anthony Liguori , Juan Quintela , Alexander Graf , qemu-devel@nongnu.org, Stefan Hajnoczi , Amit Shah , Paolo Bonzini , Andreas =?utf-8?Q?F=C3=A4rber?= , Greg Kurz "Michael S. Tsirkin" writes: > On Thu, May 15, 2014 at 02:00:15PM +0200, Andreas F=C3=A4rber wrote: [...] >> Either subsections work >> with your downstream or they don't; if they don't, then you have much >> larger problems than can be solved by blocking this one section for ppc. >> Therefore I was saying if your downstream forgot to handle the case of a >> non-VMState device having subsections, then it may be easier to fix >> exactly that than make Greg jump through more hoops here for a >> theoretical problem you are unlikely to encounter on your downstream. >>=20 >> Andreas > > I only mentioned downstream because it's a requirement coming from > users most of whom never interact with upstream. > There shouldn't be any difference and people building clusters > using upstream qemu will have same needs: clusters can't be > completely brought down for version upgrades, so need to be able to run > a mix of versions, and be able to migrate in any direction > while in the process. Okay, I'll have world peace, a cluster, and a pony, please. Seriously, no matter how much your cluster management software wants to migrate backwards, it's not going to work reliably, except in very narrow cases, at least not today. If you want to migrate freely, stick to an ultra-stable (downstream) branch of QEMU. When that branch EOLs, scrap your cluster and start over. If you want to upgrade QEMU in more interesting ways, keep track of what your cluster nodes are running, and migrate only forward.