Re: [ovirt-devel] [Bug fix of NUMA feature] Add vNode run in pNode runtime information

2014-05-22 Thread Sven Kieske
afaik you should not directly call libvirt api but use the vdsm api? but someone with more insight into vdsm can provide better information than me. Am 22.05.2014 04:13, schrieb Shi, Xiao-Lei (Bruce, HP Servers-PSC-CQ): from libvirt api, we can get each vcpu run in which physical cpu runtime --

Re: [ovirt-devel] [Bug fix of NUMA feature] Add vNode run in pNode runtime information

2014-05-22 Thread Shi, Xiao-Lei (Bruce, HP Servers-PSC-CQ)
-lei@hp.com -Original Message- From: devel-boun...@ovirt.org [mailto:devel-boun...@ovirt.org] On Behalf Of Sven Kieske Sent: Thursday, May 22, 2014 3:20 PM To: devel@ovirt.org Subject: Re: [ovirt-devel] [Bug fix of NUMA feature] Add vNode run in pNode runtime information afaik you

[ovirt-devel] [Bug fix of NUMA feature] Add vNode run in pNode runtime information

2014-05-21 Thread Shi, Xiao-Lei (Bruce, HP Servers-PSC-CQ)
Hi all, I'm working on the NUMA feature of oVirt. The feature is already merged in oVirt 3.5.0 alpha 1. Currently, it only has the virtual numa node (vNode) pin to host numa node(pNode) information which is configured by user. We plan to collect the runtime information from vdsm that vNode run