XenMon failure to get trace buffers

XenMon failure to get trace buffers

[JP S]

[-- Attachment #1.1: Type: text/plain, Size: 536 bytes --]

I am attempting to try out xenmon and am getting a error when I start it.

ERROR: Failure to get trace buffer pointer from Xen (22 = invalid argument)

I also tried running "tbctl 1" but get "Enable/Disable hypercall failure:
Invaid argument"

Granted I am a new to running xenmon/xentrace/xenbaked so I may be missing a
fundamental step here, but I documentation suggests that all I need to do is
run xenmon.py.

Can anyone shed some light on this, or just point out where I went wrong?

C/S 9515 SMP Dom0

Thanks,
js

[-- Attachment #1.2: Type: text/html, Size: 743 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: XenMon failure to get trace buffers

[Rob Gardner]

JP S wrote:

> I am attempting to try out xenmon and am getting a error when I start it.
>  
> ERROR: Failure to get trace buffer pointer from Xen (22 = invalid 
> argument)
>  
> I also tried running "tbctl 1" but get "Enable/Disable hypercall 
> failure: Invaid argument"
>  



Sorry about the documentation; It leaves out an important step. You have 
to run "setsize" to allocate the trace buffer memory. The argument is in 
number of pages, ie, "setsize 20". Then you can run tbctl. This is one 
of the things I am fixing in the next release of xenmon- it will do this 
automatically.

Rob

RE: XenMon failure to get trace buffers

[Zhao, Yunfeng]

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]

I guess you didn’t assign a buffer size to xen trace.
This can be done through modifying "xen/common/trace.c" and assigning a value to opt_tbuf_size.

Thanks
Yunfeng

________________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of JP S
Sent: 2006年4月4日 22:06
To: xen-devel@lists.xensource.com
Cc: rob.gardner@hp.com
Subject: [Xen-devel] XenMon failure to get trace buffers

I am attempting to try out xenmon and am getting a error when I start it.
 
ERROR: Failure to get trace buffer pointer from Xen (22 = invalid argument)
 
I also tried running "tbctl 1" but get "Enable/Disable hypercall failure: Invaid argument"
 
Granted I am a new to running xenmon/xentrace/xenbaked so I may be missing a fundamental step here, but I documentation suggests that all I need to do is run xenmon.py.
 
Can anyone shed some light on this, or just point out where I went wrong?
 
C/S 9515 SMP Dom0
 
Thanks,
js

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: XenMon failure to get trace buffers

[Tim Freeman]

You can do it without recompiling too.  Before running tbctl, run 'setsize 20',
setsize is in the same directory as tbctl. 

Tim 

On Fri, 7 Apr 2006 08:26:47 +0800
"Zhao, Yunfeng" <yunfeng.zhao@intel.com> wrote:

> I guess you didn’t assign a buffer size to xen trace.
> This can be done through modifying "xen/common/trace.c" and assigning a value
> to opt_tbuf_size.
> 
> Thanks
> Yunfeng
> 
> ________________________________________
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of JP S Sent:
> 2006年4月4日 22:06 To: xen-devel@lists.xensource.com
> Cc: rob.gardner@hp.com
> Subject: [Xen-devel] XenMon failure to get trace buffers
> 
> I am attempting to try out xenmon and am getting a error when I start it.
>  
> ERROR: Failure to get trace buffer pointer from Xen (22 = invalid argument)
>  
> I also tried running "tbctl 1" but get "Enable/Disable hypercall failure:
> Invaid argument"  
> Granted I am a new to running xenmon/xentrace/xenbaked so I may be missing a
> fundamental step here, but I documentation suggests that all I need to do is
> run xenmon.py.  
> Can anyone shed some light on this, or just point out where I went wrong?
>  
> C/S 9515 SMP Dom0
>  
> Thanks,
> js