Re: [Xen-tools] about XenMon

[Rob Gardner <rob.gardner@xxxxxx>]

Apparao, Padmashree K wrote:

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

What does 'xm dmesg' say about the hypervisor you're running, ie, date of latest changeset? Does it match the version of xenmon you're running? Why do you have 'tbctl' on your system when you think it's a new system, freshly installed and built with the latest bits?


Rob

 

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