External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-22 04:25:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document to not rely on virConnectGetMaxVcpus API

Browse Source 
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 <sbhat@linux.vnet.ibm.com>
This commit is contained in:
Shivaprasad G Bhat 2016-06-24 20:34:34 +05:30 committed by Andrea Bolognani
parent 8dbb347816
commit e6806d7938
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/libvirt-host.c
View File

@ -313,7 +313,10 @@ virConnectGetSysinfo(virConnectPtr conn, unsigned int flags)
* *
* Provides the maximum number of virtual CPUs supported for a guest VM of a * Provides the maximum number of virtual CPUs supported for a guest VM of a
* specific type. The 'type' parameter here corresponds to the 'type' * specific type. The 'type' parameter here corresponds to the 'type'
* attribute in the <domain> element of the XML. * attribute in the <domain> element of the XML. This API doesn't take emulator
* limits into consideration, hence the returned value is not guaranteed to be
* usable. It is recommended to use virConnectGetDomainCapabilities() and look
* for "<vcpu max='...'>" in its output instead.
* *
* Returns the maximum of virtual CPU or -1 in case of error. * Returns the maximum of virtual CPU or -1 in case of error.
*/ */