Re: [libvirt] Paradox cpu topology in capabilities outputs

2017-01-11 17:38 GMT+08:00 Daniel P. Berrange : > On Wed, Jan 11, 2017 at 06:52:45AM +, Qiao, Liyong wrote: > > Hi, > > > > I observe that virsh capabilities give wrong cpu topology on a multiple > sockets host > > > > taget@jfz1r04h13:~/libvirt$ lscpu > > Architecture:

Re: [libvirt] Paradox cpu topology in capabilities outputs

On Wed, Jan 11, 2017 at 06:52:45AM +, Qiao, Liyong wrote: > Hi, > > I observe that virsh capabilities give wrong cpu topology on a multiple > sockets host > > taget@jfz1r04h13:~/libvirt$ lscpu > Architecture: x86_64 > CPU op-mode(s):32-bit, 64-bit > Byte Order:

Re: [libvirt] Paradox cpu topology in capabilities outputs

Okay, I got some answer myself. This indicate the topology in one of a numa node. But what if I want to get the node’s physical socket number? Best Regards Eli Qiao(乔立勇）OpenStack Core team OTC Intel. -- From: "Qiao, Liyong" Date: Wednesday, 11 January 2017 at 2:52

[libvirt] Paradox cpu topology in capabilities outputs

Hi, I observe that virsh capabilities give wrong cpu topology on a multiple sockets host taget@jfz1r04h13:~/libvirt$ lscpu Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):72 On-line CPU(s) list: 0-71 Thread(s) per