From: Marcelo Tosatti <mtosatti@redhat.com>
To: Ross Boylan <ross@biostat.ucsf.edu>
Cc: kvm@vger.kernel.org
Subject: Re: unhandled wrmsr
Date: Wed, 3 Nov 2010 11:51:57 -0200 [thread overview]
Message-ID: <20101103135157.GA20269@amt.cnet> (raw)
In-Reply-To: <1288638813.24358.17.camel@corn.betterworld.us>
On Mon, Nov 01, 2010 at 12:13:33PM -0700, Ross Boylan wrote:
> I built from qemu-kvm-0.13.0.tar.gz on a Debian system with kernel
> linux-image-2.6.32-5-amd64 2.6.32-26
> (but otherwise basically the stable/lenny version) and now see
> Oct 26 16:57:38 markov kernel: [ 5757.672426] kvm: 23063: cpu0 unhandled wrmsr: 0x198 data 0
> Oct 26 16:57:38 markov kernel: [ 5757.672454] kvm: 23063: cpu1 unhandled wrmsr: 0x198 data 0
> Oct 26 16:57:38 markov kernel: [ 5757.672476] kvm: 23063: cpu2 unhandled wrmsr: 0x198 data 0
> Oct 26 16:57:38 markov kernel: [ 5757.672497] kvm: 23063: cpu3 unhandled wrmsr: 0x198 data 0
> on startup. I have 4 CPUs with 8 cores:
> Intel(R) Xeon(R) CPU E5420 @ 2.50GHz stepping 06.
> Note this means the kernel side is from the Debian package, and so might
> be older.
>
> google shows this message has popped up several times in the past and
> been fixed several times. Most of the messages indicate it is harmless,
> but https://bugs.launchpad.net/ubuntu/+source/linux/+bug/325851 on
> 2009-07-01 says it's "not benign". There also seems to be a current bug
> open about it,
> http://sourceforge.net/tracker/index.php?func=detail&aid=3056363&group_id=180599&atid=893831, which is also marked as fixed.
>
> Can anyone tell me anything more about these messages? Do they indicate
> a problem I need to fix? If so, any advice on how to fix it?
Its harmless. KVM included MSR_IA32_PERF_STATUS (0x198) in the msr
save/restore list, but there is no write emulation for it, which
generates the warning.
next prev parent reply other threads:[~2010-11-03 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 19:13 unhandled wrmsr Ross Boylan
2010-11-03 13:51 ` Marcelo Tosatti [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-02 8:44 Dave Young
2010-06-02 12:45 ` Andre Przywara
2010-06-02 13:22 ` Peter Lieven
2014-12-04 9:58 ` Praveen
2010-06-03 1:34 ` Dave Young
2010-06-03 2:23 ` Dave Young
2010-06-03 2:24 ` Dave Young
2010-06-03 9:30 ` Andre Przywara
2010-06-03 9:52 ` Dave Young
2010-06-03 9:54 ` Dave Young
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101103135157.GA20269@amt.cnet \
--to=mtosatti@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=ross@biostat.ucsf.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.