From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nu2Tc-0000bO-Hw for qemu-devel@nongnu.org; Tue, 23 Mar 2010 07:40:52 -0400 Received: from [199.232.76.173] (port=32997 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nu2Tb-0000as-UR for qemu-devel@nongnu.org; Tue, 23 Mar 2010 07:40:51 -0400 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Nu2Tb-0000JN-2U for qemu-devel@nongnu.org; Tue, 23 Mar 2010 07:40:51 -0400 Received: from mx20.gnu.org ([199.232.41.8]:28948) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Nu2Ta-0000JJ-Sy for qemu-devel@nongnu.org; Tue, 23 Mar 2010 07:40:50 -0400 Received: from mail.codesourcery.com ([38.113.113.100]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Nu2TZ-00087G-TX for qemu-devel@nongnu.org; Tue, 23 Mar 2010 07:40:50 -0400 From: Paul Brook Subject: Re: [Qemu-devel] Re: [PATCH 0/9] Virtio cleanups Date: Tue, 23 Mar 2010 11:40:46 +0000 References: <4BA81651.1070801@codemonkey.ws> <20100323104724.GA23512@redhat.com> In-Reply-To: <20100323104724.GA23512@redhat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201003231140.46924.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Gerd Hoffmann , qemu-devel@nongnu.org, Juan Quintela > > Right. The only real challenge is dealing with legacy save/restore and > > command line syntax. For save/restore, we can possibly have a dummy > > device that can split the VirtioPCI device state from the virtio device > > states and do the right thing. > > > > I'm not sure what we should do for command line syntax. We can keep > > -drive working as is. Do we need to support -device based creation? I > > don't think we've really considered what to do in a situation like this. > > If we need to change command line because of an implementation > change, IMO something is wrong with the design. > Users shouldn't care about non-existent virtio bus. I don't find this argument convincing. If we need to change the internal structure of a machine, then users who manipulate the machine configuration are going to have to compensate for this. This kind of change is pretty much unavoidable when we get the device model wrong. The best we can realistically do is avoid making these changes on a stable branch, and arrange for outdated configs to be rejected rather than silently doing the wrong thing. Paul