From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NzEgB-0000ZE-DX for qemu-devel@nongnu.org; Tue, 06 Apr 2010 15:43:19 -0400 Received: from [140.186.70.92] (port=47364 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NzEg9-0000Xk-IE for qemu-devel@nongnu.org; Tue, 06 Apr 2010 15:43:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NzEg7-0004rk-UE for qemu-devel@nongnu.org; Tue, 06 Apr 2010 15:43:17 -0400 Received: from mail2.shareable.org ([80.68.89.115]:55020) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NzEg7-0004rd-PI for qemu-devel@nongnu.org; Tue, 06 Apr 2010 15:43:15 -0400 Date: Tue, 6 Apr 2010 20:43:12 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] Re: libvirt vs. in-qemu management Message-ID: <20100406194311.GA4510@shareable.org> References: <20100406104704.GJ28689@redhat.com> <4BBB2C83.50103@suse.de> <20100406133939.GP28689@redhat.com> <4BBB3CCC.3000208@suse.de> <20100406140633.GQ28689@redhat.com> <4BBB4DEF.4070407@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BBB4DEF.4070407@suse.de> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Anthony Liguori , qemu-devel Developers , Avi Kivity Alexander Graf wrote: > So what if you had a special section that gives you the necessary > information to do that mapping? A vendor specific section so to say. > That would make it a perfect master config format, right? XML with XML Namespaces is quite good for mixing data intended for different applications. In some ways it's better than a .ini style file with an extra section, because you can easily associate the extra data wherever - for example in this case putting management disk info close to the qemu configuration for the guest disk. Then again there's something to be said for explicitly naming things like "disk 1" etc. and referring to extra data out of line - making the linkages more explicit. I wonder, if libvirt's configs were in YAML or something like samba's ini style, instead of XML, and if the guest machine config part was expressive enough to accomodate all of qemu's device attributes, would that work as a happy medium? That sounds not unlike machine configs already discussed, except being a bit more explicit to make the syntax human friendly and to accomodate libivirt/other management config on an equal footing with guest machine config. -- Jamie