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

[Xen-users] Xen and Oprofile

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen and Oprofile
From: "Bhatia, Nikhil" <bhatia@xxxxxxxx>
Date: Wed, 20 Sep 2006 18:55:44 -0400
Delivery-date: Wed, 20 Sep 2006 15:56:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbdB+dbUviTXzO3TYOzUh3GgwKk+w==
Thread-topic: Xen and Oprofile

Hello Xenoprof Users,

 

Can someone please verify the steps to get a oprofile session profile multiple sessions? I am using a file VBD for spawning two guest OS domains on the host. I am doing the following:

 

1.) On dom0

 

Opcontrol --xen=/boot/xen-syms-blah

 

2.) On domU domID: 41

 

Opcontrol --vmlinux=/boot/vmlinux-2..blah

 

3.) On domU domID: 42

 

Opcontrol --vmlinux=/boot/vmlinux-2..blah

 

 

4.) On dom0

 

Opcontrol --start-daemon --active-domains=41,42

 

 

5.) On domU, 41

 

Opcontrol --reset

Opcontrol --start

 

Error:

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

 

 

6.) On domU, 42

 

Opcontrol --reset

Opcontrol --start

 

 

Error:

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

 

7.) On dom0

 

Opcontrol --reset

Opcontrol --start

 

This works...

 

Thanks,

Nikhil

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Xen and Oprofile, Bhatia, Nikhil <=