[libvirt] [PATCH 0/4] Fix the domain capabilities wrt maxvcpus

This series addresses the comments to my patch in http://www.redhat.com/archives/libvir-list/2016-May/msg00218.html The v2 got quite a lot of criticism to not to change the virConnectGetMaxVCPUS() instead document to use the virConnectGetDomainCapabilities(). The virConnectGetDomainCapabilities() is extended to check for the host limits and the NR_CPUs are also returned. I am planning to follow up this series with possible fixes to maxvcpus command once this merged. --- Shivaprasad G Bhat (4): Document to not rely on virConnectGetMaxVcpus API Rename and move kvmGetMaxVCPUs to utils and extend it Check for VFIO too where the Legacy passthrough is checked Check the kvm host cpu max limits in virConnectGetDomainCapabilities() docs/formatdomaincaps.html.in | 4 +-- src/conf/domain_capabilities.c | 10 +++++-- src/conf/domain_capabilities.h | 1 + src/libvirt-host.c | 6 ++++ src/libvirt_private.syms | 1 + src/qemu/qemu_capabilities.c | 13 +++++++-- src/qemu/qemu_capabilities.h | 3 +- src/qemu/qemu_driver.c | 57 +++------------------------------------- src/util/virhostcpu.c | 37 ++++++++++++++++++++++++++ src/util/virhostcpu.h | 7 +++++ tests/domaincapstest.c | 3 +- 11 files changed, 78 insertions(+), 64 deletions(-) -- Signature