[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Santos, Jose Renato G" <joserenato.santos@xxxxxx>
  • From: Dante Cinco <dantecinco@xxxxxxxxx>
  • Date: Mon, 9 Nov 2009 18:13:14 -0800
  • Cc: Xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 10 Nov 2009 07:31:38 -0800
  • 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=Nh5i8uoVNspEM42oRZ4TDzL0OgLJOzR0kx5fI/YWA8CdiNhJHLx2xUk430C6Mc0m0b 7GltiP13j6FSbw5rb9u/xVA3T7tKS5UBBjL55BAyjsvwO3oN0/9wjnCZJN0PtxKoZnVN 9zmRAQe+L1J+6657afCHG/1SoViQHo6qPEbl0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Renato,

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.

Dante

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 ?
 
Renato

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)

Renato,

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.

Dante

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.