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/
Home Products Support Community News


[Xen-users] Re: xenoprof: operation 9 failed for dom0 (status: -1)

To: "Santos, Jose Renato G" <joserenato.santos@xxxxxx>
Subject: [Xen-users] Re: xenoprof: operation 9 failed for dom0 (status: -1)
From: Dante Cinco <dantecinco@xxxxxxxxx>
Date: Tue, 10 Nov 2009 10:12:49 -0800
Cc: Xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 10 Nov 2009 10:17:55 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=2W3DKIn6KFhJIGH6QBiTIXI4V7XEhQdnJN2fnQuTkB8=; b=fkGqs6ZkA8KQz/w7wtPLgXxdE1k/reQ2SmJpopk/kV035IKSZNgrrQ00DTv7TIfvnw LVitebRRD14wrBHZ7nmXM3Dx6Okpjc1PH03FpH8Gm0k5YqLYZ0JLee88oyD1wahl6wNh VCWX9s9sKkuMqBxkbrvolsBt2rDVNRjp09Uqg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=WuJGLmpKO0VHx6fBtJbhCDPfd+a6p9xTegRPMWU1arKp1JiHEsnY6WWevx42bIQpiy SFD6QJG0IiYvGOwLvlAcUHCE1zs5cZ43hE7nDorlWfmh9yqOBNbZ8UY8KJ26iECNAzrj xZSaic/O5QUZun1YLXxZxTOEWW/pQ+VAdDC10=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EF547E542C520A4D858CFEF5B404D0536080DFF2CB@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <8d2cca230911051715n5b9c1050g12bdf49c80b59053@xxxxxxxxxxxxxx> <EF547E542C520A4D858CFEF5B404D05360805E78A1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <8d2cca230911091813v17ef8427ga6fa960c77bb8389@xxxxxxxxxxxxxx> <EF547E542C520A4D858CFEF5B404D0536080DFF2CB@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I think I'm making progress. I followed your suggestion of using --passive-domains and --passive-images. When I run opreport, it is unable to find /domain1-modules and /domain1-xen-unknown. Where or how do I specify the kernel modules I have running in domU/domain1? I tried copying the *.ko files in /boot in dom0 and used --image-path=/boot in opreport and it is still not finding them.



On Mon, Nov 9, 2009 at 6:44 PM, Santos, Jose Renato G <joserenato.santos@xxxxxx> wrote:
Try replacing "--active-domains=1" with "--passive-domains=1 passive-images=<domU-kernel-image>" (use the uncompressed version of your kernel image for the guest,  vmlinux-*)
To use "active-domains" you need to run opcontrol in the guest in addition to running it in dom0 and you need to coordinate the execution of both instances.. This require the guest opcontrol to be ready before running "opcontrol --start" in dom0. That is why it is failing. I suspect you have not executed opcontrol in the guest
Using active-domains is very tricky. I suggest that you use --passive-domains, unless you really need active domains (it is only useful in case you need detailed profiles for user processes running in the guest)

From: Dante Cinco [mailto:dantecinco@xxxxxxxxx]
Sent: Monday, November 09, 2009 6:13 PM

To: Santos, Jose Renato G
Cc: Xen-users
Subject: Re: xenoprof: operation 9 failed for dom0 (status: -1)


I've narrowed down the opcontrol command sequence that causes the "write error" I'm having. If I just run "opcontrol --start" in dom0, it runs with no error and after "opcontrol --shutdown" I can run "opreport" and get a real report.

If I run "opcontrol --start-daemon --active-domains=1" in dom0, run "opcontrol --start" in domU (ID#1) and go back to dom0 and run "opcontrol --start" I get the "write error" message. It's as if "--start-daemon" is grabbing the file handle for /dev/oprofile/enable so when "--start" tries to write "1" to /dev/oprofile/enable, it is unable to do so because it is already locked.

So I can run OProfile in normal (non-Xen) mode but as soon I start using "--start-daemon" I have problems. To me it seems like a Xenoprofile problem.

I'm using OProfile 0.9.3 and oprofile-0.9.3-xen-r2.patch applied successfully.


On Thu, Nov 5, 2009 at 6:05 PM, Santos, Jose Renato G <joserenato.santos@xxxxxx> wrote:
What version of OProfile are you using?
Did you apply the Xen patch available in http://xenoprof.sourceforge.net ?

From: Dante Cinco [mailto:dantecinco@xxxxxxxxx]
Sent: Thursday, November 05, 2009 5:16 PM
To: Santos, Jose Renato G
Cc: Xen-devel
Subject: xenoprof: operation 9 failed for dom0 (status: -1)


When I tried running "opcontrol --start" (after previously running "opcontrol --start-daemon") in dom0, I get this error message:

/usr/local/bin/opcontrol: line 1639: echo: write error: Operation not permitted

and this message in the Xen console:

(XEN) xenoprof: operation 9 failed for dom 0 (status : -1)

It looks like opcontrol is trying to do this: echo 1 > /dev/oprofile/enable

and it is failing. "operation 9" maps to XENOPROF_start which is consistent with running "opcontrol --start." At first, I ignored the error because it gave the indication "Profiler running" but after I ran "opcontrol --shutdown" followed by "opreport" in dom0, I got this error message:

error: no sample files found: profile specification too strict ?

Do you know why the write error is occurring? I followed the steps in xenoprof_tutorial.ppt.


Xen-users mailing list