-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-9.7
-
libvirt-10.10.0-10.el9
-
No
-
Moderate
-
rhel-virt-core-libvirt-1
-
ssg_virtualization
-
13
-
2
-
False
-
False
-
-
None
-
None
-
Pass
-
RegressionOnly
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
On specific host , the virsh nodeinfo cmd get wrong host node number.
Please provide the package NVR for which the bug is seen:
# rpm -q libvirt libvirt-10.10.0-9.el9.aarch64
How reproducible is this bug?:100%
Steps to reproduce
1. On an nvidia grace hopper host like: nvidia-grace-hopper-xxx.redhat.com
2. Check the host numa info by lscpu:
# lscpu
Architecture: aarch64
CPU op-mode(s): 64-bit
Byte Order: Little Endian
CPU(s): 72
On-line CPU(s) list: 0-71
Vendor ID: ARM
BIOS Vendor ID: NVIDIA
Model name: Neoverse-V2
BIOS Model name: Grace A02
...
NUMA:
NUMA node(s): 9
NUMA node0 CPU(s): 0-71
NUMA node1 CPU(s):
NUMA node2 CPU(s):
NUMA node3 CPU(s):
NUMA node4 CPU(s):
NUMA node5 CPU(s):
NUMA node6 CPU(s):
NUMA node7 CPU(s):
NUMA node8 CPU(s):
3. Use virsh nodeinfo cmd to get host node info
# virsh nodeinfo
CPU model: aarch64
CPU(s): 72
CPU socket(s): 1
Core(s) per socket: 72
Thread(s) per core: 1
NUMA cell(s): 1
Memory size: 492807784 KiB
Expected results
virsh nodeinfo cmd can get 9 numa nodes, same from lscpu.
Actual results
We could see the virsh nodeinfo cmd get only 1 host numa nodes.
Additional info:
The virsh capabilities cmd can get 9 host numa nodes correctly:
# virsh capabilities <capabilities> <host> <uuid>6b14b3b6-498c-11ee-a723-74d4dd471e67</uuid> <cpu> <arch>aarch64</arch> ... <topology> <cells num='9'> <cell id='0'> <memory unit='KiB'>492807784</memory> <pages unit='KiB' size='4'>123201946</pages> ...
- links to
-
RHBA-2025:147349
libvirt bug fix and enhancement update