WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] xenmon

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] xenmon
From: "Serge Dubrouski" <sergeyfd@xxxxxxxxx>
Date: Thu, 11 May 2006 08:04:42 -0600
Delivery-date: Thu, 11 May 2006 07:05:21 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jwHTIVR0A7QMVhB4VPyQdRvjjsh67utEAF4t2hBr++zb0tT/hnW9VEoQkjiQCtswJYPesO4LsFqdDv9S3oy2OAXQ3M7VxkvURTBbCnIpeMzNZfYMiBc0PIsWHMUdGBHAy7fMWvnPz4KsIdQztX93SmBTlV6EyXGtI1zVRW28alA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200605102140.37956.kibab@xxxxxxxxxxxx>
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>
References: <200605101520.30133.raybry@xxxxxxxxxxxxxxxxx> <200605102140.37956.kibab@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
And what could be the reason fort this:

#xenmon.py
xenbaked: no process killed
ms_per_sample = 100
Initialized with 2 cpu's
CPU Frequency = 2388.52
ERROR: Failure to get trace buffer pointer from Xen (22 = Invalid argument)
xenbaked: no process killed


==========================0.00%===========

Thanks.

On 5/10/06, Kaleb Pederson <kibab@xxxxxxxxxxxx> wrote:
I haven't seen that behavior.  In 3.0.2, I had to change the xenbaked call in
xenmon so that it would redirect stdout to /dev/null as it kept outputting
some debugging code that I presume accidently was left in.

The output should look something like this (note, I'm only display the left
half of the screen as otherwise it would wrap in e-mail and look awful based
on my terminal width):

 CPU = 0        Last 10 seconds
 ============================================
 0   775.49 ns   0.00%       272.49 us/ex
 0                           6.24 ms/ex
 0   59.38 us    0.01%       0.00 ns/io
 0   13.87 ns    0.00%       4.87 us/ex
 0                           0/s
 0   0/s                     0/ex
 31  59.39 us    0.01%       20.87 ms/ex
 31                          992.84 ms/ex
 31  130.57 ns   0.00%       0.00 ns/io
 31  777.88 ns   0.00%       273.33 us/ex
 31                          0/s
 31  0/s                     0/ex
                  0.01%

I'm in the middle of playing with all the monitoring capabilities and am
writing up a tutorial, of sorts, on this functionality.

There are a few things that you might find relevant in the following:

http://kibab.homeip.net/hw/vienna_hw6/tutorial.html

It's a work in progress for one of my classes, but is hopefully decent.

--Kaleb

On Wednesday 10 May 2006 1:20 pm, Ray Bryant wrote:
> When I run xenmon.py on my x86_64 box (dual core, single socket),  I get a
> single line of incomprehensible output at the top of the screen.    It
> looks something like this (extra spaces & ='s removed to make it fit):
>
>  =     99.96%  99.98%======18.70ms/exx======Waitedd============
>
> Is this a known problem?    What is the output supposed to look like?


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




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

<Prev in Thread] Current Thread [Next in Thread>