Description of problem:
$ sudo virsh capabilities
<topology sockets='1' cores='8' threads='1'/>
However the real host has 2 sockets.
Cores and threads are correct.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. See above.
Host is this one:
As you can see from the photograph, there are two sockets.
Is this a NUMA machine? The number of sockets is counted per NUMA node. It is similar to what virNodeGetInfo returns, just the number of NUMA cells are completely ignored here. Use other parts of the capabilities XML if you want to see the real CPU topology.
Created attachment 1265346 [details]
It is a NUMA machine (in as much as every machine with > 1 sockets
these days is NUMA). This is a bit unexpected as I'd expect
"sockets" to be the number of sockets. It does show
<cells num='2'> which I guess refers to NUMA cells.
Full capabilities XML attached.
I am new here. It seems to me it's a design decision when it was implemented, it maybe a design flaw as we see it today.
I am simply practicing to contribute some code. Do we need to actually fix it or leave as it is?
As Jirka said, this was a wrong decision originally and it can't be changed now.
If you are unsure how to aggregate data from the topology XML, you can check out libvirt-python.git/examples/topology.py