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-tools

RE: [Xen-tools] about XenMon

To: "Rob Gardner" <rob.gardner@xxxxxx>
Subject: RE: [Xen-tools] about XenMon
From: "Apparao, Padmashree K" <padmashree.k.apparao@xxxxxxxxx>
Date: Wed, 14 Jun 2006 16:14:34 -0700
Cc: xen-tools@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 14 Jun 2006 16:15:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-tools-request@lists.xensource.com?subject=help>
List-id: Xen control tools developers <xen-tools.lists.xensource.com>
List-post: <mailto:xen-tools@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-tools>, <mailto:xen-tools-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-tools>, <mailto:xen-tools-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-tools-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcaQBeYy6UoIjh9HS/m7HGPJBaNWcwAAck2g
Thread-topic: [Xen-tools] about XenMon

xenmon.py

xenbaked: no process killed

ms_per_sample = 100

Initialized with 4 cpu's

CPU Frequency = 3325.22

ERROR: Failed to mmap trace buffers (14 = Bad address)

xenbaked: no process killed

 

Did a make clean all install in the tools directory under xen-unstable

-          Padma

-           

 


From: Rob Gardner [mailto:rob.gardner@xxxxxx]
Sent: Wednesday, June 14, 2006 3:57 PM
To: Apparao, Padmashree K
Cc: xen-tools@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-tools] about XenMon

 

Apparao, Padmashree K wrote:

Hi,

 

Not sure what you mean by Try recompiling it or something. Maybe re-install windows

 

I am running RHEL 2.6.16.13 xenunstable version (latest one).

Neither xenmon nor xenbaked work

 

This was all freshly compiled on a new system

 


Sorry if I don't believe you, but if you are running the "latest" xen unstable, then there should be no such file "'tbctl'", so clearly you've got something out of sync or out of date on your "new" system. On a new system with the latest xen, all you have to do is run "xenmon.py" and it will automatically start xenbaked, which will automatically allocate and enable the trace buffers.

If that doesn't happen, then try "make clean all install" in the tools directory (ie, "recompile")

If nothing works, verify that you're actually running the xen that you built; Try "xm dmesg" and it will tell you that.

The "re-install windows" comment was simply a joke.

Rob

_______________________________________________
Xen-tools mailing list
Xen-tools@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-tools
<Prev in Thread] Current Thread [Next in Thread>