On 04/07/2014 09:59 AM, Daniel P. Berrange wrote:
>>
>> The more I think about it the more it makes me wonder if we should
>> learn libvirt return list of all supported/enabled drivers.
>> Something like:
>>
>> char **virGetDrivers(virConnectPtr conn);
>>
>> if conn == NULL, the client side drivers are returned, e.g.
>> {"remote", "vbox", NULL}, if conn is not NULL, the daemon side
>> drivers are returned, e.g. {"qemu", "bhyve", "lxc", NULL}. But maybe
>> I'm over thinking it too much.
>
> You have a chicken+egg problem there in that you need to open a connection
> in order to invoke the API to get the list of connections you can open.
Although we have been talking about a meta-connection, for doing things
such as changing log settings, querying how many normal connections are
open, and so forth. The management connection could provide this
information. On the other hand, the idea of a management connection is
that is requires different privileges for connecting, so it might not be
the idea solution.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
