#VERIFICATION XENIAL
Using the test case described in the description, where a VM has 128
vcpus assigned, the version in -updates does not list the topology:
$ dpkg -l | grep libvirt
ii libvirt-bin 1.3.1-1ubuntu10.30
amd64 programs for the libvirt library
ii libvirt0:amd64 1.3.1-1ubuntu10.30
amd64 library for interfacing with different virtualization
systems
$ virsh capabilities | xmllint --xpath '/capabilities/host/topology' -
XPath set is empty
The package in -proposed fixes the issue (output shortened):
$ dpkg -l | grep libvirt
ii libvirt-bin 1.3.1-1ubuntu10.31
amd64 programs for the libvirt library
ii libvirt0:amd64 1.3.1-1ubuntu10.31
amd64 library for interfacing with different virtualization
systems
$ virsh capabilities | xmllint --xpath '/capabilities/host/topology' -
<topology>
<cells num="1">
<cell id="0">
<memory unit="KiB">4998464</memory>
<pages unit="KiB" size="4">1249616</pages>
<pages unit="KiB" size="2048">0</pages>
<pages unit="KiB" size="1048576">0</pages>
<distances>
<sibling id="0" value="10"/>
</distances>
<cpus num="128">
<cpu id="0" socket_id="0" core_id="0" siblings="0"/>
...
<cpu id="127" socket_id="127" core_id="0" siblings="127"/>
</cpus>
</cell>
</cells>
</topology>
NOTE: if the machine is running a 4.4 kernel, numa_all_cpus_ptr->size
(used to set max_n_cpus in libvirt) is 512 instead of 128 and the issue
cannot be triggered (libvirt max vcpu is 255). Any newer kernel, such as
HWE, sets the value to 128, triggering the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915811
Title:
Empty NUMA topology in machines with high number of CPUs
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1915811/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
