Re: [libvirt] [PATCH] Add virConnectGetLibvirtVersion API

2009-11-12 Thread Cole Robinson
On 11/02/2009 03:52 PM, Cole Robinson wrote: > Hi all, > > The attached patch adds a new API call for retrieving the libvirt > version used by a connection: virConnectGetLibvirtVersion. Without this, > there is currently no way to determine the libvirt version of a remote > qemu connection for exa

Re: [libvirt] [PATCH] Add virConnectGetLibvirtVersion API

2009-11-12 Thread Cole Robinson
On 11/12/2009 06:49 AM, Daniel P. Berrange wrote: > On Mon, Nov 02, 2009 at 03:52:28PM -0500, Cole Robinson wrote: >> Hi all, >> >> The attached patch adds a new API call for retrieving the libvirt >> version used by a connection: virConnectGetLibvirtVersion. Without this, >> there is currently no

Re: [libvirt] [PATCH] Add virConnectGetLibvirtVersion API

2009-11-12 Thread Daniel P. Berrange
On Mon, Nov 02, 2009 at 03:52:28PM -0500, Cole Robinson wrote: > Hi all, > > The attached patch adds a new API call for retrieving the libvirt > version used by a connection: virConnectGetLibvirtVersion. Without this, > there is currently no way to determine the libvirt version of a remote > qemu

Re: [libvirt] [PATCH] Add virConnectGetLibvirtVersion API

2009-11-04 Thread Daniel Veillard
On Mon, Nov 02, 2009 at 03:52:28PM -0500, Cole Robinson wrote: > Hi all, > > The attached patch adds a new API call for retrieving the libvirt > version used by a connection: virConnectGetLibvirtVersion. Without this, > there is currently no way to determine the libvirt version of a remote > qemu

[libvirt] [PATCH] Add virConnectGetLibvirtVersion API

2009-11-02 Thread Cole Robinson
Hi all, The attached patch adds a new API call for retrieving the libvirt version used by a connection: virConnectGetLibvirtVersion. Without this, there is currently no way to determine the libvirt version of a remote qemu connection for example. This info can be useful for feature detection/enabl