[Xen-users] Re: [Xen-devel] Oprofile-0.9.2 problem with xen-unstable

[William Cohen <wcohen@xxxxxxxxxx>]

Bhatia, Nikhil wrote:
> Hello Will, Padma and All,
>
> I will try the patch the oprofile-0.9.2 by the new patch given by you.
> For now, I am trying to use the oprofile-0.9.1 and am able to start
> oprofile profiler on the host OS. However, when I try to do it on the
> guest OS, I get the following error: 
>
> This worked !!!!!
> vm01:~# opcontrol --vmlinux=/boot/vmlinux-syms-2.6.16.13-xen
>
> however this failed !!!
> vm01:~# opcontrol --start
> Using default event: CPU_CLK_UNHALTED:100000:0:1:1
> Using 2.6+ OProfile kernel interface.
> Reading module info.
> Failed to open profile device: Operation not permitted
> Couldn't start oprofiled.
> Check the log file "/var/lib/oprofile/oprofiled.log" and kernel syslog
>
> Do you have any ideas?
>
> Thanks,
> Nikhil
Was there any interesting information in /var/lib/oprofile/oprofiled.log?

OProfile stores configuration in /root/.oprofile/daemonrc. Does it make any 
difference whether there was a successful configuration before running?
For the time that it didn't work did the oprofile kernel module get loaded?
One trick that you can do to find out what is being executed in opcontrol script 
is put "-x" at the end of the first line of opcontrol:
#!/bin/sh -x

This should give a trace of opcontrol.

-Will

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