From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MFkeJ-0001F2-Bz for qemu-devel@nongnu.org; Sun, 14 Jun 2009 04:01:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MFkeE-0001Ee-D7 for qemu-devel@nongnu.org; Sun, 14 Jun 2009 04:01:06 -0400 Received: from [199.232.76.173] (port=46917 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MFkeE-0001Eb-9G for qemu-devel@nongnu.org; Sun, 14 Jun 2009 04:01:02 -0400 Received: from mx2.redhat.com ([66.187.237.31]:38109) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MFkeD-0005ct-NA for qemu-devel@nongnu.org; Sun, 14 Jun 2009 04:01:01 -0400 Message-ID: <4A34ADA9.80709@redhat.com> Date: Sun, 14 Jun 2009 10:58:33 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: Configuration vs. compat hints [was Re: [Qemu-devel] [PATCHv3 03/13] qemu: add routines to manage PCI capabilities] References: <20090610145540.GI19375@poweredge.glommer> <20090610150129.GC28601@redhat.com> <200906101624.30659.paul@codesourcery.com> <20090610174301.GC7416@shareable.org> <20090610182227.GN28601@redhat.com> <20090610192702.GH7416@shareable.org> <1244796209.16425.20.camel@blaa> <4A326C7E.3020309@codemonkey.ws> <1244822007.30522.68.camel@blaa> <4A327E87.6080005@codemonkey.ws> <1244825333.26769.20.camel@blaa> In-Reply-To: <1244825333.26769.20.camel@blaa> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mark McLoughlin Cc: Carsten Otte , kvm@vger.kernel.org, "Michael S. Tsirkin" , Glauber Costa , Rusty Russell , qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Blue Swirl , Christian Borntraeger , Paul Brook Mark McLoughlin wrote: >> I think the point is that you don't need version numbers if you have a >> proper device tree. >> > > How do you add a new attribute to the device tree and, when a supplied > device tree lacking said attribute, distinguish between a device tree > from an old version of qemu (i.e. use the old default) and a partial > device tree from the VM manager (i.e. use the new default) ? > -baseline 0.10 > >> NB the device tree contains no host configuration information. >> > > So, it wouldn't e.g. include the path to the image file for a block > device? That would always be specified on the command line? > Or in a different file. I agree splitting host and guest configuration is a must-have, this ensures portability of virtual machines across hosts and time. -- error compiling committee.c: too many arguments to function