From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M9fZU-0003Ba-KN for qemu-devel@nongnu.org; Thu, 28 May 2009 09:23:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M9fZP-00038K-Ks for qemu-devel@nongnu.org; Thu, 28 May 2009 09:22:59 -0400 Received: from [199.232.76.173] (port=35215 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M9fZP-000385-EU for qemu-devel@nongnu.org; Thu, 28 May 2009 09:22:55 -0400 Received: from mx20.gnu.org ([199.232.41.8]:31290) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M9fZP-0002Rf-7o for qemu-devel@nongnu.org; Thu, 28 May 2009 09:22:55 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M9fZO-00061s-Gg for qemu-devel@nongnu.org; Thu, 28 May 2009 09:22:54 -0400 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH] Change virtio-console to PCI_CLASS_SERIAL_OTHER Date: Thu, 28 May 2009 14:22:51 +0100 References: <1243012478.29542.18.camel@blaa> <200905281353.50463.paul@codesourcery.com> <4A1E8A16.3060101@us.ibm.com> In-Reply-To: <4A1E8A16.3060101@us.ibm.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905281422.52420.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Mark McLoughlin , Anthony Liguori , Dor Laor , ajax@redhat.com > >> - the device model cannot change or the guest OS will get confused > > > > 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. > > It is very worth the pain. I consider it a core requirement. We disagree then. You're effectively requiring bug-compatibility. This may be reasonable for a stable branch, but is not something I have any interest in across different release cycles. IMHO major VM upgrades should be considered the same as real hardware or firmware upgrades. Paul