Re: [Qemu-devel] Re: libvirt vs. in-qemu management

[Jamie Lokier <jamie@shareable.org>]

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