From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 102651] New: vcpuX unhandled rdmsr: 0x570
Date: Tue, 11 Aug 2015 04:09:59 +0000 [thread overview]
Message-ID: <bug-102651-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=102651
Bug ID: 102651
Summary: vcpuX unhandled rdmsr: 0x570
Product: Virtualization
Version: unspecified
Kernel Version: 4.1.4
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: jamespharvey20@gmail.com
Regression: No
Host: Intel Xeon CPU E5335 @ 2.00GHz, stepping 7, microcode 0x6b
Up to date arch, using kernel 4.1.4 (-1 Arch) x86_64
Guest: Up to date arch x86_64
Every time I start the vm, tty0/dmesg gets:
==========
[11681.871378] kvm [2469]: vcpu0 unhandled rdmsr: 0x570
[11681.871915] kvm [2469]: vcpu1 unhandled rdmsr: 0x570
[11681.872559] kvm [2469]: vcpu2 unhandled rdmsr: 0x570
[11681.873057] kvm [2469]: vcpu3 unhandled rdmsr: 0x570
[11681.873536] kvm [2469]: vcpu4 unhandled rdmsr: 0x570
[11681.874033] kvm [2469]: vcpu5 unhandled rdmsr: 0x570
[11681.874525] kvm [2469]: vcpu6 unhandled rdmsr: 0x570
==========
(It is a 7 virtual cpu system.)
Looks like this was supposed to have been changed a while ago so it shows in
dmesg, but not tty0. But, it's still showing in tty0.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2015-08-11 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 4:09 bugzilla-daemon [this message]
2015-08-11 4:12 ` [Bug 102651] vcpuX unhandled rdmsr: 0x570 bugzilla-daemon
2015-08-14 10:18 ` bugzilla-daemon
2015-11-02 17:00 ` bugzilla-daemon
2015-11-03 0:58 ` bugzilla-daemon
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=bug-102651-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox