yeah, Daniel and Nikola, you are right.
Before, I find no numa in a host by the numactl --hardware, so I think that there may be no numa topo.
I made the following test, and find that the libvirt return a numa even if the value from the numactl is zero.
thanks.
yeah, Daniel and Nikola, you are right.
Before, I find no numa in a host by the numactl --hardware, so I think that there may be no numa topo.
I made the following test, and find that the libvirt return a numa even if the value from the numactl is zero.
thanks.
root@tralon- Vostro- 1400:~# virsh --version Vostro- 1400:~# numactl --hardware Vostro- 1400:~# virsh capabilities
1.2.2
root@tralon-
available: 0 nodes ()
root@tralon-
<capabilities>
<host> 44454c4c- 3500-1039- 8038-b4c04f4332 58</uuid> arch>i686< /arch> model>n270< /model> vendor> Intel</ vendor> management> suspend_ mem/> suspend_ disk/> suspend_ hybrid/ > management> features> uri_transports>
<uri_transport >tcp</uri_ transport> /uri_transports > _features> >3106852< /memory> model>apparmor< /model> model>dac< /model> >+117:+ 126</baselabel> >+117:+ 126</baselabel>
<uuid>
<cpu>
<
<
<
<topology sockets='1' cores='2' threads='1'/>
<feature name='lahf_lm'/>
<feature name='lm'/>
<feature name='pdcm'/>
<feature name='xtpr'/>
<feature name='cx16'/>
<feature name='tm2'/>
<feature name='est'/>
<feature name='vmx'/>
<feature name='ds_cpl'/>
<feature name='dtes64'/>
<feature name='pbe'/>
<feature name='tm'/>
<feature name='ht'/>
<feature name='ss'/>
<feature name='acpi'/>
<feature name='ds'/>
<feature name='pse36'/>
</cpu>
<power_
<
<
<
</power_
<migration_
<live/>
<
<
</migration
<topology>
<cells num='1'>
<cell id='0'>
<memory unit='KiB'
<cpus num='2'>
<cpu id='0' socket_id='0' core_id='0' siblings='0'/>
<cpu id='1' socket_id='0' core_id='1' siblings='1'/>
</cpus>
</cell>
</cells>
</topology>
<secmodel>
<
<doi>0</doi>
</secmodel>
<secmodel>
<
<doi>0</doi>
<baselabel type='kvm'
<baselabel type='qemu'
</secmodel>
</host>
</capabilities>