* [Bug 102651] New: vcpuX unhandled rdmsr: 0x570
@ 2015-08-11 4:09 bugzilla-daemon
2015-08-11 4:12 ` [Bug 102651] " bugzilla-daemon
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: bugzilla-daemon @ 2015-08-11 4:09 UTC (permalink / raw)
To: kvm
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.
^ permalink raw reply [flat|nested] 5+ messages in thread* [Bug 102651] vcpuX unhandled rdmsr: 0x570 2015-08-11 4:09 [Bug 102651] New: vcpuX unhandled rdmsr: 0x570 bugzilla-daemon @ 2015-08-11 4:12 ` bugzilla-daemon 2015-08-14 10:18 ` bugzilla-daemon ` (2 subsequent siblings) 3 siblings, 0 replies; 5+ messages in thread From: bugzilla-daemon @ 2015-08-11 4:12 UTC (permalink / raw) To: kvm https://bugzilla.kernel.org/show_bug.cgi?id=102651 --- Comment #1 from jamespharvey20@gmail.com --- The libvirt/qemu log shows: 2015-08-11 03:29:38.508+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.94 LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/sbin/qemu-system-x86_64 -name servo -S -machine pc-q35-2.3,accel=kvm,usb=off,vmport=off -cpu core2duo,+lahf_lm,+dca,+pdcm,+xtpr,+cx16,+tm2,+vmx,+ds_cpl,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds -m 3300 -realtime mlock=off -smp 7,sockets=7,cores=1,threads=1 -uuid f6defdf1-369a-47e2-9611-92c04a0ff933 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/servo.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -boot strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x3 -drive file=/dev/disk1/servo1,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.2,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/dev/disk2/servo2,if=none,id=drive-virtio-disk1,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.2,addr=0x6,drive=drive-virtio-disk1,id=virtio-disk1,bootindex=2 -drive file=/dev/disk3/servo3,if=none,id=drive-virtio-disk2,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.2,addr=0x7,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=3 -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:61:7a:4e,bus=pci.2,addr=0x1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channel/target/servo.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.2,addr=0x4 -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) -- You are receiving this mail because: You are watching the assignee of the bug. ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug 102651] vcpuX unhandled rdmsr: 0x570 2015-08-11 4:09 [Bug 102651] New: vcpuX unhandled rdmsr: 0x570 bugzilla-daemon 2015-08-11 4:12 ` [Bug 102651] " bugzilla-daemon @ 2015-08-14 10:18 ` bugzilla-daemon 2015-11-02 17:00 ` bugzilla-daemon 2015-11-03 0:58 ` bugzilla-daemon 3 siblings, 0 replies; 5+ messages in thread From: bugzilla-daemon @ 2015-08-14 10:18 UTC (permalink / raw) To: kvm https://bugzilla.kernel.org/show_bug.cgi?id=102651 Huaitong Han <oenhan@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oenhan@gmail.com --- Comment #2 from Huaitong Han <oenhan@gmail.com> --- it's just warning, current KVM does not support intel PT feature, you can ignore it, and I will fix the warning in native kernel. -- You are receiving this mail because: You are watching the assignee of the bug. ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug 102651] vcpuX unhandled rdmsr: 0x570 2015-08-11 4:09 [Bug 102651] New: vcpuX unhandled rdmsr: 0x570 bugzilla-daemon 2015-08-11 4:12 ` [Bug 102651] " bugzilla-daemon 2015-08-14 10:18 ` bugzilla-daemon @ 2015-11-02 17:00 ` bugzilla-daemon 2015-11-03 0:58 ` bugzilla-daemon 3 siblings, 0 replies; 5+ messages in thread From: bugzilla-daemon @ 2015-11-02 17:00 UTC (permalink / raw) To: kvm https://bugzilla.kernel.org/show_bug.cgi?id=102651 Joachim Namislow <jfrieben@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfrieben@hotmail.com --- Comment #3 from Joachim Namislow <jfrieben@hotmail.com> --- I do see this warning by kernel-4.2.3-300.fc23 of a Fedora 23 system. -- You are receiving this mail because: You are watching the assignee of the bug. ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug 102651] vcpuX unhandled rdmsr: 0x570 2015-08-11 4:09 [Bug 102651] New: vcpuX unhandled rdmsr: 0x570 bugzilla-daemon ` (2 preceding siblings ...) 2015-11-02 17:00 ` bugzilla-daemon @ 2015-11-03 0:58 ` bugzilla-daemon 3 siblings, 0 replies; 5+ messages in thread From: bugzilla-daemon @ 2015-11-03 0:58 UTC (permalink / raw) To: kvm https://bugzilla.kernel.org/show_bug.cgi?id=102651 --- Comment #4 from Huaitong Han <oenhan@gmail.com> --- (In reply to Joachim Frieben from comment #3) > I do see this warning by kernel-4.2.3-300.fc23 of a Fedora 23 system. You can patch it on guest kernel, https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=73fdeb66592ee80dffb16fb8a9b7378a00c1a826, although the warning has no effect on your guest. -- You are receiving this mail because: You are watching the assignee of the bug. ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-11-03 0:58 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2015-08-11 4:09 [Bug 102651] New: vcpuX unhandled rdmsr: 0x570 bugzilla-daemon 2015-08-11 4:12 ` [Bug 102651] " bugzilla-daemon 2015-08-14 10:18 ` bugzilla-daemon 2015-11-02 17:00 ` bugzilla-daemon 2015-11-03 0:58 ` bugzilla-daemon
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.