Actually we don't directly call libvirt api, we call it from the wrapped libvirtconnection like other functions do in vdsm. Thanks & Best Regards Shi, Xiao-Lei (Bruce) Hewlett-Packard Co., Ltd. HP Servers Core Platform Software China Telephone +86 23 65683093 Mobile +86 18696583447 Email xiao-lei.shi@hp.com -----Original Message----- From: devel-bounces@ovirt.org [mailto:devel-bounces@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 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
-- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel