Xen devel - Aug 2011 - (XEN) traps.c:2430:d0 Domain attempted WRMSR 00000000c0010000 from 0x0000000000430076 to 0x0000000000030076.

Hello,

Where can I switch the following message off?
(XEN) traps.c:2430:d0 Domain attempted WRMSR 00000000c0010000 from 
0x0000000000430076 to 0x0000000000030076.

There are many such messages in the output of "xm dmesg". What is the 
reason?
Is it for debugging purposes or just an issue with my hardware? (HP 
DL385g7 / AMD CPUs)

Thank you / regards, Mark

-- 
ms@it-infrastrukturen.org



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

You can specify guest_loglvl=error to turn off warning messages, but that
would turn off other messages that might actually be interesting.
Alternatively you''d have to disable the message in source code and
rebuild
the hypervisor. Possibly we should reduce this message to debug loglevel
rather than warning logelevel: I agree the message is very much not a
rarity.

 -- Keir

On 14/08/2011 12:08, "Mark Schneider"
<ms@it-infrastrukturen.org> wrote:
> Hello,
> 
> Where can I switch the following message off?
> (XEN) traps.c:2430:d0 Domain attempted WRMSR 00000000c0010000 from
> 0x0000000000430076 to 0x0000000000030076.
> 
> There are many such messages in the output of "xm dmesg". What is
the
> reason?
> Is it for debugging purposes or just an issue with my hardware? (HP
> DL385g7 / AMD CPUs)
> 
> Thank you / regards, Mark


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

>>> On 14.08.11 at 15:48, Keir Fraser <keir.xen@gmail.com> wrote:
> You can specify guest_loglvl=error to turn off warning messages, but that
> would turn off other messages that might actually be interesting.
> Alternatively you''d have to disable the message in source code and
rebuild
> the hypervisor. Possibly we should reduce this message to debug loglevel
> rather than warning logelevel: I agree the message is very much not a
> rarity.
I tend to disagree - the kernel shouldn''t really attempt these writes.
One of the things addressing of which is more cumbersome in pv-ops
(which I assume is in use here) than "classic" kernels.

Jan
> On 14/08/2011 12:08, "Mark Schneider"
<ms@it-infrastrukturen.org> wrote:
> 
>> Hello,
>> 
>> Where can I switch the following message off?
>> (XEN) traps.c:2430:d0 Domain attempted WRMSR 00000000c0010000 from
>> 0x0000000000430076 to 0x0000000000030076.
>> 
>> There are many such messages in the output of "xm dmesg".
What is the
>> reason?
>> Is it for debugging purposes or just an issue with my hardware? (HP
>> DL385g7 / AMD CPUs)
>> 
>> Thank you / regards, Mark
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com 
> http://lists.xensource.com/xen-devel 



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

On Mon, Aug 15, 2011 at 08:40:36AM +0100, Jan Beulich
wrote:
> >>> On 14.08.11 at 15:48, Keir Fraser <keir.xen@gmail.com>
wrote:
> > You can specify guest_loglvl=error to turn off warning messages, but
that
> > would turn off other messages that might actually be interesting.
> > Alternatively you''d have to disable the message in source
code and rebuild
> > the hypervisor. Possibly we should reduce this message to debug
loglevel
> > rather than warning logelevel: I agree the message is very much not a
> > rarity.
> 
> I tend to disagree - the kernel shouldn''t really attempt these
writes.
> One of the things addressing of which is more cumbersome in pv-ops
> (which I assume is in use here) than "classic" kernels.
It might be good to find out what those calls are and see about actually
fixing it.
> 
> Jan
> 
> > On 14/08/2011 12:08, "Mark Schneider"
<ms@it-infrastrukturen.org> wrote:
> > 
> >> Hello,
> >> 
> >> Where can I switch the following message off?
> >> (XEN) traps.c:2430:d0 Domain attempted WRMSR 00000000c0010000 from
> >> 0x0000000000430076 to 0x0000000000030076.
> >> 
> >> There are many such messages in the output of "xm
dmesg". What is the
> >> reason?
> >> Is it for debugging purposes or just an issue with my hardware?
(HP
> >> DL385g7 / AMD CPUs)
> >> 
> >> Thank you / regards, Mark
> > 
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com 
> > http://lists.xensource.com/xen-devel 
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

>>> On 15.08.11 at 14:30, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Mon, Aug 15, 2011 at 08:40:36AM +0100, Jan Beulich wrote:
>> >>> On 14.08.11 at 15:48, Keir Fraser
<keir.xen@gmail.com> wrote:
>> > You can specify guest_loglvl=error to turn off warning messages,
but that
>> > would turn off other messages that might actually be interesting.
>> > Alternatively you''d have to disable the message in source
code and rebuild
>> > the hypervisor. Possibly we should reduce this message to debug
loglevel
>> > rather than warning logelevel: I agree the message is very much
not a
>> > rarity.
>> 
>> I tend to disagree - the kernel shouldn''t really attempt these
writes.
>> One of the things addressing of which is more cumbersome in pv-ops
>> (which I assume is in use here) than "classic" kernels.
> 
> It might be good to find out what those calls are and see about actually
> fixing it.
These are performance monitoring MSRs, and as we seem to agree the
whole perf subsystem is currently not usable with Xen.

Jan


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

On Mon, Aug 15, 2011 at 01:45:11PM +0100, Jan Beulich
wrote:
> >>> On 15.08.11 at 14:30, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> > On Mon, Aug 15, 2011 at 08:40:36AM +0100, Jan Beulich wrote:
> >> >>> On 14.08.11 at 15:48, Keir Fraser
<keir.xen@gmail.com> wrote:
> >> > You can specify guest_loglvl=error to turn off warning
messages, but that
> >> > would turn off other messages that might actually be
interesting.
> >> > Alternatively you''d have to disable the message in
source code and rebuild
> >> > the hypervisor. Possibly we should reduce this message to
debug loglevel
> >> > rather than warning logelevel: I agree the message is very
much not a
> >> > rarity.
> >> 
> >> I tend to disagree - the kernel shouldn''t really attempt
these writes.
> >> One of the things addressing of which is more cumbersome in pv-ops
> >> (which I assume is in use here) than "classic" kernels.
> > 
> > It might be good to find out what those calls are and see about
actually
> > fixing it.
> 
> These are performance monitoring MSRs, and as we seem to agree the
> whole perf subsystem is currently not usable with Xen.
I would like to see it getting usuable with Xen. Not sure if that is just
a "wish" vs a reality. The folks that published the
(http://people.cs.vt.edu/~rnikola/files/vee2011.pdf)

http://lists.xensource.com/archives/html/xen-devel/2011-05/msg01233.html

seemed to have done some work.

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