I cannot confirm, but then there are many differences:
Kernel: 3.13.0-52-generic #85-Ubuntu libvirt: 1.2.2-0ubuntu13.1.10 CPU: AMD Opteron(tm) Processor 6128 Board: Supermicro H8SGL-F
virsh nodeinfo CPU model: x86_64 CPU(s): 8 CPU frequency: 800 MHz CPU socket(s): 1 Core(s) per socket: 4 Thread(s) per core: 1 NUMA cell(s): 2 Memory size: 32881044 KiB
numactl -H available: 2 nodes (0-1) node 0 cpus: 0 1 2 3 node 0 size: 15983 MB node 0 free: 15727 MB node 1 cpus: 4 5 6 7 node 1 size: 16126 MB node 1 free: 15726 MB node distances: node 0 1 0: 10 20 1: 20 10
I wonder, whether the wrong info persists a restart of libvirtd (service libvirt-bin restart)...
I cannot confirm, but then there are many differences:
Kernel: 3.13.0-52-generic #85-Ubuntu .1.10
libvirt: 1.2.2-0ubuntu13
CPU: AMD Opteron(tm) Processor 6128
Board: Supermicro H8SGL-F
virsh nodeinfo
CPU model: x86_64
CPU(s): 8
CPU frequency: 800 MHz
CPU socket(s): 1
Core(s) per socket: 4
Thread(s) per core: 1
NUMA cell(s): 2
Memory size: 32881044 KiB
numactl -H
available: 2 nodes (0-1)
node 0 cpus: 0 1 2 3
node 0 size: 15983 MB
node 0 free: 15727 MB
node 1 cpus: 4 5 6 7
node 1 size: 16126 MB
node 1 free: 15726 MB
node distances:
node 0 1
0: 10 20
1: 20 10
I wonder, whether the wrong info persists a restart of libvirtd (service libvirt-bin restart)...