This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Monitoring domU resource usage

To: Xen-users <Xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Monitoring domU resource usage
From: Andy Smith <andy@xxxxxxxxxxxxxx>
Date: Wed, 8 Jun 2005 16:09:48 +0000
Delivery-date: Wed, 08 Jun 2005 16:08:58 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Openpgp: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
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

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.


Attachment: signature.asc
Description: Digital signature

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>