Sense available hypervisors (was: Re: [Libvir] RFC: Broadcast our presence with avahi)
Daniel P. Berrange wrote:
- I advertise two subtypes, of '_xen.libvirtd._tcp' and
'_qemu.libvirtd._tcp'
What I actually want todo is to be able to probe the libvirt local drivers
to auto-discover what virtualization platforms are available. A sort of
lightweight virConnectOpen which merely returns TRUE/FALSE and doesn't
actually allocate a virConnectPtr object. Need to extend the internal
driver API for this.
I wanted this feature too, however I don't think the way that you're
proposing is right.
Just as virConnectGetCapabilities returns the capabilities of the
current hypervisor, I think there should be a call like 'virGetInfo' (or
something like that) which returns the capabilities of the node, which
would include what hypervisors are supported.
Rich.
--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903
Attachments:
- smime.p7s (application/x-pkcs7-signature — 3.2 KB)