[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Monitoring domU resource usage


  • To: Xen-users <Xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
  • Date: Wed, 8 Jun 2005 16:09:48 +0000
  • Delivery-date: Wed, 08 Jun 2005 16:08:58 +0000
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Openpgp: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc

Using 2.0-testing, what methods are people using to monitor
individual domU CPU usage?

Obviously I can run an snmpd in each domU and see how busy the CPU
is, but that could be tampered with from inside the domU, and as the
domU doesn't know it doesn't have the whole cpu needs some
interpretation.

I can see CPU time used in "xm list" but that looks like rather a
blunt tool - would I have to do something like this for example:

Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      507    0  r----   7644.0
foo                1      127    1  -b---   2585.9    9601
bar                2       63    1  -b---    147.6    9602

(5 minutes later)

Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      507    0  r----   7841.5
foo                1      127    1  -b---   2593.2    9601
bar                2       63    1  -b---    184.9    9602

dom0 has used 7841.5-7644.0=197.5 seconds, foo used 7.3s, bar used
37.3s.  In 5 minutes there are 300 seconds so dom0 used
197.5/300*100=65.83% CPU, foo 2.43%, bar 12.43%, machine was 19.31%
idle or overhead.

That still doesn't give a way to tell how much CPU a domU *wanted*
to have, though.  i.e. if a domU could make use of more CPU share if
given it.

Andy

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.