Many thanks !
It's more clear for me now.
I've forgot the mid (what a shame :o )
But despite VM_metrics.get_record works, the current used memory is
"missing" (or not implemented). Damned :/
I've got :
VCPUs_flags 0 blocked online
VCPUs_utilisation 0 0.00016007062223236292
VCPUs_CPU 0 2
Is it "normal" ?
On Fri, Sep 18, 2009 at 2:01 PM, Christopher Winslett
> Use "VM_metrics" to see the the hardware reported metrics.
> Use "VM_guest_metrics" to see the VM reported metrics. Probably need to
> install the XENSource kernel drivers on the guest OS to get these figures;
> all mine were null too.
> What type of figures are you looking for?
> The following RPC calls work for me:
> sid = Session ID
> mid = Metrics ID Associated with VM
> VM_metrics.get_record(sid, mid)
> It would return a value for memory_actual, VCPUs_number.
> In Ruby it would be the following RPC calls:
> require "XMLRPC/Client"
> s = XMLRPC::Client.new2("https://localhost")
> sid = s.call("session.login_with_password", "uname", "pass")["Value"]
> mid = "OpaqueRef:xxxxx"
> memory = s.call("VM_metrics.get_record", sid, mid)["Value"]["actual_memory"]
> That being said, to get utilization numbers, we use a network monitor system
> like Nagios.
> On Fri, Sep 18, 2009 at 5:33 AM, Olivier LAMBERT <lambert.olivier@xxxxxxxxx>
>> I'm reading the Xen Management API pdf (Version: API Revision 1.0.6,
>> Date: 24th July 2008, Stable Release).
>> It talks about class "VM metrics" (§2.9) and "VM guest metrics"
>> (§2.10). But all method call with these classes in RPC send me NULL
>> Despite it works fine for other classes, like VM, or network etc. All
>> classes with metrics seems to be not recognized by the API.
>> Configuration : Dom0 on Debian Lenny, with xen-hypervisor-3.2-1-amd64.
>> How can I do to gather informations about CPU, ram and network on
>> domU's with the API ?
>> Thank you,
>> xen-api mailing list
> Christopher Winslett
xen-api mailing list