Description of problem: Libvirt: vpx:// driver can not get CPU topology from vmware guest when set multiple sockets and 1 core in CPU topology Version-Release number of selected component (if applicable): libvirt-4.3.0-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.Set 8 sockets and 1 core in guest's cpu topology on VMware host 2.Use virsh to check guest's cpu topology, but can't get CPU topology # virsh -c vpx://root.75.182/data/10.73.3.19/?no_verify=1 Enter root's password for 10.73.75.182: Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # dumpxml esx5.5-win2016-x86_64 <domain type='vmware' xmlns:vmware='http://libvirt.org/schemas/domain/vmware/1.0'> <name>esx5.5-win2016-x86_64</name> <uuid>42378dec-6f14-9ed3-ee28-7dcbfb703382</uuid> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static'>8</vcpu> <cputune> <shares>8000</shares> </cputune> .... Actual results: As above description Expected results: Libvirt: vpx:// driver can not get CPU topology from vmware guest when set multiple sockets and 1 core in CPU topology Additional info: 1.This bug comes from bug1568148
Created attachment 1453670 [details] window2016_8-sockets_1-core.vmx
Attached the VMX file from bug 1568148. Sadly, there seems to be no information in it about the CPU topology, other than the "numvcpus" key.
Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution.