Re: [libvirt] [PATCH 2/2] esx:Fix esxDomainGetMaxVcpus to return correct vcpus

2018-08-14 Thread Marcos Paulo de Souza
On Mon, Aug 13, 2018 at 11:21:05PM +0200, Matthias Bolte wrote: > 2018-08-10 5:56 GMT+02:00 Marcos Paulo de Souza : > > Before this change, esxDomainGetMaxVcpus returned -1, which in turn > > fails in libvirt. This commit reimplements esxDomainGetMaxVcpus instead > > of calling

Re: [libvirt] [PATCH 2/2] esx:Fix esxDomainGetMaxVcpus to return correct vcpus

2018-08-13 Thread Matthias Bolte
2018-08-10 5:56 GMT+02:00 Marcos Paulo de Souza : > Before this change, esxDomainGetMaxVcpus returned -1, which in turn > fails in libvirt. This commit reimplements esxDomainGetMaxVcpus instead > of calling esxDomainGetVcpusFlags. The implementation checks for > capability.maxSupportedVcpus, but

[libvirt] [PATCH 2/2] esx:Fix esxDomainGetMaxVcpus to return correct vcpus

2018-08-09 Thread Marcos Paulo de Souza
Before this change, esxDomainGetMaxVcpus returned -1, which in turn fails in libvirt. This commit reimplements esxDomainGetMaxVcpus instead of calling esxDomainGetVcpusFlags. The implementation checks for capability.maxSupportedVcpus, but as this one can be ommited in ESXi, we also check for