Re: [libvirt] [PATCH v2 3/3] Document to not rely on virConnectGetMaxVcpus API

2016-06-24 Thread Andrea Bolognani
On Fri, 2016-06-24 at 20:34 +0530, Shivaprasad G Bhat wrote: > The API virConnectGetMaxVcpus doesn't really reflect the actual usable number > of cpus as the maximum limits can be different for kvm and/or qemu. So update > the documentation to use virConnectGetDomainCapabilities() instead. > >

[libvirt] [PATCH v2 3/3] Document to not rely on virConnectGetMaxVcpus API

2016-06-24 Thread Shivaprasad G Bhat
The API virConnectGetMaxVcpus doesn't really reflect the actual usable number of cpus as the maximum limits can be different for kvm and/or qemu. So update the documentation to use virConnectGetDomainCapabilities() instead. Signed-off-by: Shivaprasad G Bhat ---