From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M9fWx-000231-Bh for qemu-devel@nongnu.org; Thu, 28 May 2009 09:20:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M9fWs-0001vM-N7 for qemu-devel@nongnu.org; Thu, 28 May 2009 09:20:22 -0400 Received: from [199.232.76.173] (port=35162 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M9fWs-0001v3-Ed for qemu-devel@nongnu.org; Thu, 28 May 2009 09:20:18 -0400 Received: from mx20.gnu.org ([199.232.41.8]:31118) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M9fWs-0001uq-63 for qemu-devel@nongnu.org; Thu, 28 May 2009 09:20:18 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M9fWr-0005sl-6O for qemu-devel@nongnu.org; Thu, 28 May 2009 09:20:17 -0400 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH] Change virtio-console to PCI_CLASS_SERIAL_OTHER Date: Thu, 28 May 2009 14:20:07 +0100 References: <1243012478.29542.18.camel@blaa> <200905281353.50463.paul@codesourcery.com> <20090528130419.GC24488@redhat.com> In-Reply-To: <20090528130419.GC24488@redhat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905281420.14840.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: Mark McLoughlin , Anthony Liguori , Dor Laor , ajax@redhat.com, qemu-devel@nongnu.org > > IMHO think the only sane response is "don't do that". Trying to support > > migration between different qemu versions just isn't worth the pain. > > I think that further more, we shouldn't make a change like altering > the PCI device class in the stable branch, only in the unstable > branch. If we restrict the stable branch to bug fixes, then it ought > to be (more?) practical to support save under 0.10 and restore under > 0.11, without needing to support the hard problem of save under 0.10 > and restore under 1.00 (or whatever next major release branch is) 0.11 is the next major release series. The current stable releases are 0.10.x. I agree we shouldn't be making this sort of change on the stable branch, precisely because it's reasonable to expect stable releases to be backwards compatible. Paul