[libvirt] Unable to find node's mem and cpu api

jovialGuy _ jovialguy at gmail.com
Mon Sep 1 15:26:28 UTC 2008


I have Xen hypervisor. Can I can memory information from "domain 0" instance
as well.  How to get physical utilization of each CPU attached  to host? I
know this is being handled in virt-top but how?

- Jovial

On Mon, Sep 1, 2008 at 5:04 PM, Richard W.M. Jones <rjones at redhat.com>wrote:

> On Mon, Sep 01, 2008 at 04:54:04PM +0200, jovialGuy _ wrote:
> > I am unable to find the api in java and perl binding to find the host
> node's
> > current memory and cpu information. Any body has any idea where I can
> find
> > the information?
> I'm not certain about whether the Java & Perl bindings support them,
> but these are the calls you should use:
> http://libvirt.org/html/libvirt-libvirt.html#virNodeGetInfo
> http://libvirt.org/html/libvirt-libvirt.html#virNodeGetCellsFreeMemory
> http://libvirt.org/html/libvirt-libvirt.html#virNodeGetFreeMemory
> For CPU usage of the host, libvirt doesn't specifically provide that
> information.  If the hypervisor is Xen, then you can get information
> about CPU usage of Dom0 (usually what is meant by "the host") using:
> http://libvirt.org/html/libvirt-libvirt.html#virDomainGetInfo
> but that won't work for QEMU/KVM where "the host node" is just the
> Linux kernel.  (In the local case, you can extract that information
> you need just by looking in /proc or using ordinary Linux tools).
> Also read this: http://et.redhat.com/~rjones/virt-top/faq.html#calccpu<http://et.redhat.com/%7Erjones/virt-top/faq.html#calccpu>
> Rich.
> --
> Richard Jones, Emerging Technologies, Red Hat
> http://et.redhat.com/~rjones
> virt-top <http://et.redhat.com/%7Erjonesvirt-top> is 'top' for virtual
> machines.  Tiny program with many
> powerful monitoring features, net stats, disk stats, logging, etc.
> http://et.redhat.com/~rjones/virt-top<http://et.redhat.com/%7Erjones/virt-top>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20080901/2fd74836/attachment-0001.htm>

More information about the libvir-list mailing list