6:15 a.m.
Hello
Is there an easy way to get supported feature (API) list in each driver?
The function would be to return a list which describes which APIs are
supported and which APIs are not.
Thanks in advance
ozaki-r
2:29 a.m.
On Sat, Jun 19, 2010 at 08:15:44PM +0900, Ryota Ozaki wrote:
Hello
Is there an easy way to get supported feature (API) list in each driver?
The function would be to return a list which describes which APIs are
supported and which APIs are not.
No, and it's somehow painful. If unsupported you will get a specific
error code back though, so maybe that can be automated in some ways.
There is the manually maintained page for driver support at
http://libvirt.org/hvsupport.html
but being manual means it's often outdated :-\
Also there is some subtleties, for example on Xen the main driver is
actually implemenbted as a set of 3 sub-drivers for hv/xend/xenstore
so just checking for NULL values in the driver entry point is not
completely sufficient to assert support of a feature.
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library http://libvirt.org/
4:52 a.m.
On Mon, Jun 21, 2010 at 4:29 PM, Daniel Veillard <veillard(a)redhat.com> wrote:
On Sat, Jun 19, 2010 at 08:15:44PM +0900, Ryota Ozaki wrote:
> Hello
>
> Is there an easy way to get supported feature (API) list in each driver?
> The function would be to return a list which describes which APIs are
> supported and which APIs are not.
No, and it's somehow painful. If unsupported you will get a specific
error code back though, so maybe that can be automated in some ways.
Indeed. I agree it is an easy way (not smart though).
There is the manually maintained page for driver support at
http://libvirt.org/hvsupport.html
but being manual means it's often outdated :-\
There is not even entry for lxc!
Also there is some subtleties, for example on Xen the main driver is
actually implemenbted as a set of 3 sub-drivers for hv/xend/xenstore
so just checking for NULL values in the driver entry point is not
completely sufficient to assert support of a feature.
Oh, I didn't know that. I though I could use the entry point.
OK, trial and error seems a easy and solid way.
Thanks for your explanation.
ozaki-r
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library http://libvirt.org/
5300
days inactive
5302
days old
2 comments
2 participants
participants (2)
-
Daniel Veillard -
Ryota Ozaki