xenoprof: operation 9 failed for dom0 (status: -1)

xenoprof: operation 9 failed for dom0 (status: -1)

[Dante Cinco]

[-- Attachment #1.1: Type: text/plain, Size: 850 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 986 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: xenoprof: operation 9 failed for dom0 (status: -1)

[Dante Cinco]

[-- Attachment #1.1: Type: text/plain, Size: 2165 bytes --]

I initially tried OProfile 0.9.3 with the oprofile-0.9.3-xen-r2.patch but
when I tried running "opcontrol --status" in dom0, I got an error message
about cpu_set or cpu_type and prompted to use a newer version of OProfile (I
think OProfile 0.9.3 doesn't recognized the Core i7 CPU I'm using). So I
downloaded OProfile 0.9.5 and manually applied the same patch and it seems
to work except for the problems I described in my previous email. I'm also
using Jeremy's latest pvops 2.6.31.5 with Dulloor's xenoprof.patch. I'm also
using the patched OProfile 0.9.5 in domU (Linux 2.6.30.1).

I realize I'm using a lot of new stuff like pvops 2.6.31.5 (with Xen
3.5-unstable changeset 20330) and OProfile 0.9.5 but I thought I'd check
with you to see if the problems I'm having sound familiar.

Thanks.

Dante

On Thu, Nov 5, 2009 at 6:05 PM, Santos, Jose Renato G <
joserenato.santos@hp.com> 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@gmail.com]
> *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
>
>

[-- Attachment #1.2: Type: text/html, Size: 3443 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Re: xenoprof: operation 9 failed for dom0 (status: -1)

[Andrew Evans]

[-- Attachment #1.1: Type: text/plain, Size: 2970 bytes --]

I too am experiencing this problem. My setup is much less bleeding-edge, 
however:

RHEL 5.3 dom0 (2.6.18-128.el5xen kernel)
xen-3.3.1 from gitco
oprofile-0.9.3-18.el5

Same error message in Xen dmesg ring buffer.

-Andrew

On 11/06/2009 09:27 AM, Dante Cinco wrote:
> I initially tried OProfile 0.9.3 with the oprofile-0.9.3-xen-r2.patch 
> but when I tried running "opcontrol --status" in dom0, I got an error 
> message about cpu_set or cpu_type and prompted to use a newer version 
> of OProfile (I think OProfile 0.9.3 doesn't recognized the Core i7 CPU 
> I'm using). So I downloaded OProfile 0.9.5 and manually applied the 
> same patch and it seems to work except for the problems I described in 
> my previous email. I'm also using Jeremy's latest pvops 2.6.31.5 with 
> Dulloor's xenoprof.patch. I'm also using the patched OProfile 0.9.5 in 
> domU (Linux 2.6.30.1).
>
> I realize I'm using a lot of new stuff like pvops 2.6.31.5 (with Xen 
> 3.5-unstable changeset 20330) and OProfile 0.9.5 but I thought I'd 
> check with you to see if the problems I'm having sound familiar.
>
> Thanks.
>
> Dante
>
> On Thu, Nov 5, 2009 at 6:05 PM, Santos, Jose Renato G 
> <joserenato.santos@hp.com <mailto:joserenato.santos@hp.com>> 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@gmail.com
>         <mailto:dantecinco@gmail.com>]
>         *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-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>    


[-- Attachment #1.2: Type: text/html, Size: 4504 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Re: xenoprof: operation 9 failed for dom0 (status: -1)

[Dulloor]

Yeah, I had to modify 0.9.3 to use it with i7. Can send you the patch tomorrow.

-dulloor

On Fri, Nov 6, 2009 at 12:27 PM, Dante Cinco <dantecinco@gmail.com> wrote:
> I initially tried OProfile 0.9.3 with the oprofile-0.9.3-xen-r2.patch but
> when I tried running "opcontrol --status" in dom0, I got an error message
> about cpu_set or cpu_type and prompted to use a newer version of OProfile (I
> think OProfile 0.9.3 doesn't recognized the Core i7 CPU I'm using). So I
> downloaded OProfile 0.9.5 and manually applied the same patch and it seems
> to work except for the problems I described in my previous email. I'm also
> using Jeremy's latest pvops 2.6.31.5 with Dulloor's xenoprof.patch. I'm also
> using the patched OProfile 0.9.5 in domU (Linux 2.6.30.1).
>
> I realize I'm using a lot of new stuff like pvops 2.6.31.5 (with Xen
> 3.5-unstable changeset 20330) and OProfile 0.9.5 but I thought I'd check
> with you to see if the problems I'm having sound familiar.
>
> Thanks.
>
> Dante
>
> On Thu, Nov 5, 2009 at 6:05 PM, Santos, Jose Renato G
> <joserenato.santos@hp.com> 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@gmail.com]
>> 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-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>