Re: [libvirt] RFC: advertising graphics support (vnc, spice, sdl)
On 10/19/2012 02:31 AM, Doug Goldstein wrote:
Currently consumers of libvirt's APIs must assume/attempt to
define a
VM that uses spice, vnc, or sdl without knowing if the actual
hypervisor supports it. Obviously my discussion is very QEMU oriented
but it would be good to leave expansion for the future. I was thinking
that under the <guest> element for the capabilities we can add
something like:
<graphics>
<spice/>
<vnc/>
<sdl/>
</graphics>
This is something I've wanted to do for a long long time but my scope is much
bigger: libvirt really needs to report near everything it knows about qemu
emulator capabilities to the API user so we don't need to keep large
whitelists in apps like virt-manager. That doesn't mean we couldn't start here
though.
The simplest place to put it is capabilties for sure, but if the scope is
going to grow to cover more XML parameters it might be worth considering a
separate API (but maybe we don't care if capabilities output is 100 pages long).
The XML format could quickly get hairy if you assume that in the future maybe
we want to report what graphics types support password or other arbitrary XML
elements, but maybe that's getting into the realm of rng schema.
- Cole