On Thu, Mar 01, 2018 at 03:28:57PM +0100, Peter Krempa wrote:
> On Thu, Mar 01, 2018 at 15:12:39 +0100, Michal Privoznik wrote:
> > On 03/01/2018 02:15 PM, Peter Krempa wrote:
> > > On Thu, Mar 01, 2018 at 14:08:29 +0100, Michal Privoznik wrote:
> > >> Signed-off-by: --help <mprivozn@xxxxxxxxxx>
> > >
> > > Hmm.
> > >
> > >> ---
> > >> docs/news.xml | 102 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > >> 1 file changed, 102 insertions(+)
> > >>
> > >> diff --git a/docs/news.xml b/docs/news.xml
> > >> index 86a0c8d18..53bf9a49c 100644
> > >> --- a/docs/news.xml
> > >> +++ b/docs/news.xml
> > >> @@ -44,6 +44,28 @@
> > >> using the <code>cachetune</code> element in <code>cputune</code>.
> > >> </description>
> > >> </change>
> > >> + <change>
> > >> + <summary>
> > >> + Allow opening secondary drivers
> > >> + </summary>
> > >> + <description>
> > >> + Up until now it was possible to connect to only hypervisor drivers
> > >> + (e.g. qemu:///system, lxc:///, vbox:///system, and so on). The
> > >> + internal drivers (like network driver, node device driver, etc.) were
> > >> + hidden from users and users could use them only indirectly. Starting
> > >> + with this release new connection URIs are accepted. For instance
> > >> + network:///system, storage:///system and so on.
> > >> + </description>
> > >
> > > Isn't this an internal change not really used for consumption of
> > > clients?
> >
> > Not really. Try it yourself:
> >
> > virsh -c network:///system net-list --all
>
> Well, that obviously has to work. But it's not exactly useful for
> general usage:
>
> $ virsh -c network:///system list --all
> error: Failed to list active domains
> error: this function is not supported by the connection driver: virConnectNumOfDomains
>
> [...]
Note that in general we don't promise *any* API is supported by *any*
URI. The set of APIs provided by any given driver are documented in
our page
https://libvirt.org/hvsupport.html
So the fact that the network:/// URI doesn't support the listing
of domains is not a bug. It is just an expected gap in the support
matrix for that driver.
IOW, this is largely a documentation task - I still need to provide
docs for the secondary drivers to describe this better.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list
