I wonder if any extra setup is needed to run XenMon for 3.0.0. It looks like the patch was applied into the hypervisor a while back and that the python program xenmon.py starts xenbaked for you. But when I run XenMon, it prints: # python xenmon.py xenbaked: no process killed ms_per_sample = 100 Initialized with 2 cpu''s CPU Frequency = 1800.10 ERROR: Failure to get trace buffer pointer from Xen (22 = Invalid argument) -- Here it prints 0.0% for each CPU. -- Then after quitting: xenbaked: no process killed Thanks, Tim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tim Freeman wrote:>I wonder if any extra setup is needed to run XenMon for 3.0.0. It looks like >the patch was applied into the hypervisor a while back and that the python >program xenmon.py starts xenbaked for you. But when I run XenMon, it prints: > ># python xenmon.py >xenbaked: no process killed >ms_per_sample = 100 >Initialized with 2 cpu''s >CPU Frequency = 1800.10 >ERROR: Failure to get trace buffer pointer from Xen (22 = Invalid argument) > >Tim, There is an additional step needed to make xenmon work. I apologize for not documenting this. Xen starts out running with trace buffers disabled, and so the trace buffer size needs to be set and enabled before xenmon will run. In the tools/xentrace directory you will find two programs, setsize and tbctl. Try the following: setsize 10 tbctl 1 This will set the trace buffer size to 10 pages, which is a decent default value, and the tbctl command will turn on tracing in the hypervisor. I will make an addendum to the xenmon readme file with this information. Rob Gardner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, 04 Jan 2006 10:57:09 -0700 Rob Gardner <rob.gardner@hp.com> wrote:> Tim Freeman wrote: > > >I wonder if any extra setup is needed to run XenMon for 3.0.0. It looks like > >the patch was applied into the hypervisor a while back and that the python > >program xenmon.py starts xenbaked for you. But when I run XenMon, it prints: > > > > > ># python xenmon.py > >xenbaked: no process killed > >ms_per_sample = 100 > >Initialized with 2 cpu''s > >CPU Frequency = 1800.10 > >ERROR: Failure to get trace buffer pointer from Xen (22 = Invalid argument) > > > > > > > Tim, > > There is an additional step needed to make xenmon work. I apologize for > not documenting this. Xen starts out running with trace buffers > disabled, and so the trace buffer size needs to be set and enabled > before xenmon will run. > > In the tools/xentrace directory you will find two programs, setsize and > tbctl. Try the following: > setsize 10 > tbctl 1 > This will set the trace buffer size to 10 pages, which is a decent > default value, and the tbctl command will turn on tracing in the hypervisor.Aha, it''s working now. Thankyou, Tim> > I will make an addendum to the xenmon readme file with this information. > > Rob Gardner > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users