* unhandled wrmsr @ 2010-06-02 8:44 Dave Young 2010-06-02 12:45 ` Andre Przywara 0 siblings, 1 reply; 12+ messages in thread From: Dave Young @ 2010-06-02 8:44 UTC (permalink / raw) To: kvm Hi, With today's git version (qemu-kvm), I got following message in kernel dmesg [168344.215605] kvm: 27289: cpu0 unhandled wrmsr: 0x198 data 0 bash-3.1$ /home/dave/tmp/qemu-system-x86_64 --version QEMU emulator version 0.12.50 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard bash-3.1$ uname -a Linux darkstar 2.6.35-rc1 #35 SMP Mon May 31 16:50:15 CST 2010 x86_64 Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz GenuineIntel GNU/Linux host distribution is slackware64-13.0 0.12.3 works well BTW the guest is a tiny core linux image -- Regards dave ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: unhandled wrmsr 2010-06-02 8:44 unhandled wrmsr Dave Young @ 2010-06-02 12:45 ` Andre Przywara 2010-06-02 13:22 ` Peter Lieven 2010-06-03 1:34 ` Dave Young 0 siblings, 2 replies; 12+ messages in thread From: Andre Przywara @ 2010-06-02 12:45 UTC (permalink / raw) To: Dave Young; +Cc: kvm@vger.kernel.org Dave Young wrote: > Hi, > > With today's git version (qemu-kvm), I got following message in kernel dmesg > > [168344.215605] kvm: 27289: cpu0 unhandled wrmsr: 0x198 data 0 Are you sure about that? 0x198 is an Intel architectural perfmon MSR and it is read-only. The Linux kernel source I grep'ed obeys this and does only rdmsr. You can work around this by changing the error to a warning with: # modprobe kvm ignore_msrs=1 I'd like to see more details about the guest Linux kernel, at least the version you used to see why there is a wrmsr on this address. Best is you provide the kernel (just the vmlinuz file) somewhere so that we can reproduce this. Also the qemu-kvm command line would be interesting. Regards, Andre. > > bash-3.1$ /home/dave/tmp/qemu-system-x86_64 --version > QEMU emulator version 0.12.50 (qemu-kvm-devel), Copyright (c) > 2003-2008 Fabrice Bellard > > > bash-3.1$ uname -a > Linux darkstar 2.6.35-rc1 #35 SMP Mon May 31 16:50:15 CST 2010 x86_64 > Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz GenuineIntel GNU/Linux > > host distribution is slackware64-13.0 > > 0.12.3 works well > > BTW the guest is a tiny core linux image > -- Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany Tel: +49 351 448-3567-12 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: unhandled wrmsr 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 1 sibling, 1 reply; 12+ messages in thread From: Peter Lieven @ 2010-06-02 13:22 UTC (permalink / raw) To: Andre Przywara; +Cc: Dave Young, kvm@vger.kernel.org Andre Przywara wrote: > Dave Young wrote: >> Hi, >> >> With today's git version (qemu-kvm), I got following message in >> kernel dmesg >> >> [168344.215605] kvm: 27289: cpu0 unhandled wrmsr: 0x198 data 0 > Are you sure about that? 0x198 is an Intel architectural perfmon MSR > and it is read-only. The Linux kernel source I grep'ed obeys this and > does only rdmsr. > You can work around this by changing the error to a warning with: > # modprobe kvm ignore_msrs=1 > > I'd like to see more details about the guest Linux kernel, at least > the version you used to see why there is a wrmsr on this address. Best > is you provide the kernel (just the vmlinuz file) somewhere so that we > can reproduce this. Also the qemu-kvm command line would be interesting. I see the same with Ubuntu 10.04 64-bit (2.6.32-21-server) cmdline: /usr/bin/qemu-kvm-devel -net tap,vlan=141,script=no,downscript=no,ifname=tap0 -net nic,vlan=141,model=e1000,macaddr=52:54:00:ff:00:73 -drive format=host_device,file=/dev/mapper/iqn.2001-05.com.equallogic:0-8a0906-c0c61b105-db8000e7e954bf65-migration-test-2,if=ide,boot=on,cache=none,aio=native -m 1024 -cpu qemu64,model_id='Intel(R) Xeon(R) CPU E5520 @ 2.27GHz',-kvmclock -monitor tcp:0:4001,server,nowait -vnc :1 -name 'migration-test-10-04' -boot order=dc,menu=on -k de -pidfile /var/run/qemu/vm-156.pid -mem-path /hugepages -mem-prealloc -rtc base=utc,clock=host -usb -usbdevice tablet > > Regards, > Andre. > >> >> bash-3.1$ /home/dave/tmp/qemu-system-x86_64 --version >> QEMU emulator version 0.12.50 (qemu-kvm-devel), Copyright (c) >> 2003-2008 Fabrice Bellard >> >> >> bash-3.1$ uname -a >> Linux darkstar 2.6.35-rc1 #35 SMP Mon May 31 16:50:15 CST 2010 x86_64 >> Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz GenuineIntel GNU/Linux >> >> host distribution is slackware64-13.0 >> >> 0.12.3 works well >> >> BTW the guest is a tiny core linux image >> > -- Mit freundlichen Grüßen/Kind Regards Peter Lieven .......................................................................................................... KAMP Netzwerkdienste GmbH Vestische Str. 89-91 | 46117 Oberhausen Tel: +49 (0) 208.89 402-50 | Fax: +49 (0) 208.89 402-40 mailto:pl@kamp.de | http://www.kamp.de Geschäftsführer: Heiner Lante | Michael Lante Amtsgericht Duisburg | HRB Nr. 12154 USt-Id-Nr.: DE 120607556 ......................................................................................................... ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: unhandled wrmsr 2010-06-02 13:22 ` Peter Lieven @ 2014-12-04 9:58 ` Praveen 0 siblings, 0 replies; 12+ messages in thread From: Praveen @ 2014-12-04 9:58 UTC (permalink / raw) To: kvm Peter Lieven <pl <at> dlh.net> writes: > > Andre Przywara wrote: > > Dave Young wrote: > >> Hi, > >> > >> With today's git version (qemu-kvm), I got following message in > >> kernel dmesg > >> > >> [168344.215605] kvm: 27289: cpu0 unhandled wrmsr: 0x198 data 0 > > Are you sure about that? 0x198 is an Intel architectural perfmon MSR > > and it is read-only. The Linux kernel source I grep'ed obeys this and > > does only rdmsr. > > You can work around this by changing the error to a warning with: > > # modprobe kvm ignore_msrs=1 > > > > I'd like to see more details about the guest Linux kernel, at least > > the version you used to see why there is a wrmsr on this address. Best > > is you provide the kernel (just the vmlinuz file) somewhere so that we > > can reproduce this. Also the qemu-kvm command line would be interesting. > > I see the same with Ubuntu 10.04 64-bit (2.6.32-21-server) > > cmdline: > /usr/bin/qemu-kvm-devel -net > tap,vlan=141,script=no,downscript=no,ifname=tap0 -net > nic,vlan=141,model=e1000,macaddr=52:54:00:ff:00:73 -drive > > format=host_device,file=/dev/mapper/iqn.2001-05.com.equallogic:0-8a0906- c0c61b105-db8000e7e954bf65-migration-test- 2,if=ide,boot=on,cache=none,aio=native > > -m 1024 -cpu qemu64,model_id='Intel(R) Xeon(R) CPU E5520 <at> > 2.27GHz',-kvmclock -monitor tcp:0:4001,server,nowait -vnc :1 -name > 'migration-test-10-04' -boot order=dc,menu=on -k de -pidfile > /var/run/qemu/vm-156.pid -mem-path /hugepages -mem-prealloc -rtc > base=utc,clock=host -usb -usbdevice tablet > > > > > Regards, > > Andre. > > > >> > >> bash-3.1$ /home/dave/tmp/qemu-system-x86_64 --version > >> QEMU emulator version 0.12.50 (qemu-kvm-devel), Copyright (c) > >> 2003-2008 Fabrice Bellard > >> > >> > >> bash-3.1$ uname -a > >> Linux darkstar 2.6.35-rc1 #35 SMP Mon May 31 16:50:15 CST 2010 x86_64 > >> Intel(R) Core(TM)2 Duo CPU E7500 <at> 2.93GHz GenuineIntel GNU/Linux > >> > >> host distribution is slackware64-13.0 > >> > >> 0.12.3 works well > >> > >> BTW the guest is a tiny core linux image > >> > > > Hi i am also getting the same errors, When i start he kvm, i was getting the error messages related to wrmsr, from a little bit of google i found out these are harmless and the workaround suggested was to make the errors to warning. but still i can see the warnings coming every time i started the kvm is there an actual fix to remove them. or just simply mask these errors. I am calling the kvm arguments from inside a bash script so the redirecting the output is not working well. my host os is ubuntu 14-04. Thanks in Advance praveen ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: unhandled wrmsr 2010-06-02 12:45 ` Andre Przywara 2010-06-02 13:22 ` Peter Lieven @ 2010-06-03 1:34 ` Dave Young 2010-06-03 2:23 ` Dave Young 2010-06-03 9:30 ` Andre Przywara 1 sibling, 2 replies; 12+ messages in thread From: Dave Young @ 2010-06-03 1:34 UTC (permalink / raw) To: Andre Przywara; +Cc: kvm@vger.kernel.org On Wed, Jun 2, 2010 at 8:45 PM, Andre Przywara <andre.przywara@amd.com> wrote: > Dave Young wrote: >> >> Hi, >> >> With today's git version (qemu-kvm), I got following message in kernel >> dmesg >> >> [168344.215605] kvm: 27289: cpu0 unhandled wrmsr: 0x198 data 0 > > Are you sure about that? Sure 0x198 is an Intel architectural perfmon MSR and it > is read-only. The Linux kernel source I grep'ed obeys this and does only > rdmsr. > You can work around this by changing the error to a warning with: > # modprobe kvm ignore_msrs=1 with this param, appear following warning: kvm: 28520: cpu0 ignored wrmsr: 0x198 data 0 > > I'd like to see more details about the guest Linux kernel, at least the > version you used to see why there is a wrmsr on this address. Best is you > provide the kernel (just the vmlinuz file) somewhere so that we can > reproduce this. Also the qemu-kvm command line would be interesting. Actually I tried different guest image, recreate this problem is easy. one of them is slackware 13.0 kernel version 2.6.29.6, you can download from: http://www.slackware.at/data/slackware64-13.0/kernels/huge.s/ kvm cmdline: qemu-system-x86_64 -net nic -net tap,ifname=tap0,script=no slack64.img > > Regards, > Andre. > >> >> bash-3.1$ /home/dave/tmp/qemu-system-x86_64 --version >> QEMU emulator version 0.12.50 (qemu-kvm-devel), Copyright (c) >> 2003-2008 Fabrice Bellard >> >> >> bash-3.1$ uname -a >> Linux darkstar 2.6.35-rc1 #35 SMP Mon May 31 16:50:15 CST 2010 x86_64 >> Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz GenuineIntel GNU/Linux >> >> host distribution is slackware64-13.0 >> >> 0.12.3 works well >> >> BTW the guest is a tiny core linux image >> > > -- > Andre Przywara > AMD-Operating System Research Center (OSRC), Dresden, Germany > Tel: +49 351 448-3567-12 > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Regards dave ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: unhandled wrmsr 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 1 sibling, 1 reply; 12+ messages in thread From: Dave Young @ 2010-06-03 2:23 UTC (permalink / raw) To: Andre Przywara; +Cc: kvm@vger.kernel.org On Thu, Jun 3, 2010 at 9:34 AM, Dave Young <hidave.darkstar@gmail.com> wrote: > On Wed, Jun 2, 2010 at 8:45 PM, Andre Przywara <andre.przywara@amd.com> wrote: >> Dave Young wrote: >>> >>> Hi, >>> >>> With today's git version (qemu-kvm), I got following message in kernel >>> dmesg >>> >>> [168344.215605] kvm: 27289: cpu0 unhandled wrmsr: 0x198 data 0 >> >> Are you sure about that? > > Sure > > 0x198 is an Intel architectural perfmon MSR and it >> is read-only. The Linux kernel source I grep'ed obeys this and does only >> rdmsr. >> You can work around this by changing the error to a warning with: >> # modprobe kvm ignore_msrs=1 > > with this param, appear following warning: > kvm: 28520: cpu0 ignored wrmsr: 0x198 data 0 > >> >> I'd like to see more details about the guest Linux kernel, at least the >> version you used to see why there is a wrmsr on this address. Best is you >> provide the kernel (just the vmlinuz file) somewhere so that we can >> reproduce this. Also the qemu-kvm command line would be interesting. > > Actually I tried different guest image, recreate this problem is easy. > > one of them is slackware 13.0 kernel version 2.6.29.6, you can download from: > http://www.slackware.at/data/slackware64-13.0/kernels/huge.s/ > > kvm cmdline: > qemu-system-x86_64 -net nic -net tap,ifname=tap0,script=no slack64.img > >> >> Regards, >> Andre. >> >>> >>> bash-3.1$ /home/dave/tmp/qemu-system-x86_64 --version >>> QEMU emulator version 0.12.50 (qemu-kvm-devel), Copyright (c) >>> 2003-2008 Fabrice Bellard Another problem with this build is I can not boot from virtio-blk, cmdline: qemu-system-x86_64 -boot c -drive file=slack64.img,if-virtio,boot=on qemu just complain about: Could not read the boot disk Anything missing by me? >>> >>> >>> bash-3.1$ uname -a >>> Linux darkstar 2.6.35-rc1 #35 SMP Mon May 31 16:50:15 CST 2010 x86_64 >>> Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz GenuineIntel GNU/Linux >>> >>> host distribution is slackware64-13.0 >>> >>> 0.12.3 works well >>> >>> BTW the guest is a tiny core linux image >>> >> >> -- >> Andre Przywara >> AMD-Operating System Research Center (OSRC), Dresden, Germany >> Tel: +49 351 448-3567-12 >> >> -- >> To unsubscribe from this list: send the line "unsubscribe kvm" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > > > > -- > Regards > dave > -- Regards dave ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: unhandled wrmsr 2010-06-03 2:23 ` Dave Young @ 2010-06-03 2:24 ` Dave Young 0 siblings, 0 replies; 12+ messages in thread From: Dave Young @ 2010-06-03 2:24 UTC (permalink / raw) To: Andre Przywara; +Cc: kvm@vger.kernel.org On Thu, Jun 3, 2010 at 10:23 AM, Dave Young <hidave.darkstar@gmail.com> wrote: > On Thu, Jun 3, 2010 at 9:34 AM, Dave Young <hidave.darkstar@gmail.com> wrote: >> On Wed, Jun 2, 2010 at 8:45 PM, Andre Przywara <andre.przywara@amd.com> wrote: >>> Dave Young wrote: >>>> >>>> Hi, >>>> >>>> With today's git version (qemu-kvm), I got following message in kernel >>>> dmesg >>>> >>>> [168344.215605] kvm: 27289: cpu0 unhandled wrmsr: 0x198 data 0 >>> >>> Are you sure about that? >> >> Sure >> >> 0x198 is an Intel architectural perfmon MSR and it >>> is read-only. The Linux kernel source I grep'ed obeys this and does only >>> rdmsr. >>> You can work around this by changing the error to a warning with: >>> # modprobe kvm ignore_msrs=1 >> >> with this param, appear following warning: >> kvm: 28520: cpu0 ignored wrmsr: 0x198 data 0 >> >>> >>> I'd like to see more details about the guest Linux kernel, at least the >>> version you used to see why there is a wrmsr on this address. Best is you >>> provide the kernel (just the vmlinuz file) somewhere so that we can >>> reproduce this. Also the qemu-kvm command line would be interesting. >> >> Actually I tried different guest image, recreate this problem is easy. >> >> one of them is slackware 13.0 kernel version 2.6.29.6, you can download from: >> http://www.slackware.at/data/slackware64-13.0/kernels/huge.s/ >> >> kvm cmdline: >> qemu-system-x86_64 -net nic -net tap,ifname=tap0,script=no slack64.img >> >>> >>> Regards, >>> Andre. >>> >>>> >>>> bash-3.1$ /home/dave/tmp/qemu-system-x86_64 --version >>>> QEMU emulator version 0.12.50 (qemu-kvm-devel), Copyright (c) >>>> 2003-2008 Fabrice Bellard > > Another problem with this build is I can not boot from virtio-blk, cmdline: > qemu-system-x86_64 -boot c -drive file=slack64.img,if-virtio,boot=on typo, if=virtio > > qemu just complain about: > Could not read the boot disk > > Anything missing by me? > >>>> >>>> >>>> bash-3.1$ uname -a >>>> Linux darkstar 2.6.35-rc1 #35 SMP Mon May 31 16:50:15 CST 2010 x86_64 >>>> Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz GenuineIntel GNU/Linux >>>> >>>> host distribution is slackware64-13.0 >>>> >>>> 0.12.3 works well >>>> >>>> BTW the guest is a tiny core linux image >>>> >>> >>> -- >>> Andre Przywara >>> AMD-Operating System Research Center (OSRC), Dresden, Germany >>> Tel: +49 351 448-3567-12 >>> >>> -- >>> To unsubscribe from this list: send the line "unsubscribe kvm" in >>> the body of a message to majordomo@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> >> >> >> >> -- >> Regards >> dave >> > > > > -- > Regards > dave > -- Regards dave ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: unhandled wrmsr 2010-06-03 1:34 ` Dave Young 2010-06-03 2:23 ` Dave Young @ 2010-06-03 9:30 ` Andre Przywara 2010-06-03 9:52 ` Dave Young 1 sibling, 1 reply; 12+ messages in thread From: Andre Przywara @ 2010-06-03 9:30 UTC (permalink / raw) To: Dave Young; +Cc: kvm@vger.kernel.org Dave Young wrote: > On Wed, Jun 2, 2010 at 8:45 PM, Andre Przywara <andre.przywara@amd.com> wrote: >> Dave Young wrote: >>> Hi, >>> >>> With today's git version (qemu-kvm), I got following message in kernel >>> dmesg >>> >>> [168344.215605] kvm: 27289: cpu0 unhandled wrmsr: 0x198 data 0 >> Are you sure about that? > > Sure > > 0x198 is an Intel architectural perfmon MSR and it >> is read-only. The Linux kernel source I grep'ed obeys this and does only >> rdmsr. >> You can work around this by changing the error to a warning with: >> # modprobe kvm ignore_msrs=1 > > with this param, appear following warning: > kvm: 28520: cpu0 ignored wrmsr: 0x198 data 0 As suspected. Did the boot succeed, then? > >> I'd like to see more details about the guest Linux kernel, at least the >> version you used to see why there is a wrmsr on this address. Best is you >> provide the kernel (just the vmlinuz file) somewhere so that we can >> reproduce this. Also the qemu-kvm command line would be interesting. > > Actually I tried different guest image, recreate this problem is easy. > > one of them is slackware 13.0 kernel version 2.6.29.6, you can download from: > http://www.slackware.at/data/slackware64-13.0/kernels/huge.s/ Ah, nice to meet the other Slackware user ;-) > kvm cmdline: > qemu-system-x86_64 -net nic -net tap,ifname=tap0,script=no slack64.img I tried: $ x86_64-softmmu/qemu-system-x86_64 -kernel /boot/vmlinuz-huge-2.6.29.6 -nographic -append "console=ttyS0,115200n8" -cpu core2duo,model=26,stepping=5,vendor=GenuineIntel This booted fine. Sadly I had no access to an Intel box this morning, so I had to use vendor override, but I guess this misses some features which an original Intel box has. Can you post the /proc/cpuinfo output from the guest? It seems that some feature bits trigger the behavior in the guest. The host was an Xeon5520, right? Regards, Andre. -- Andre Przywara AMD-Operating System Research Center (OSRC), Dresden, Germany Tel: +49 351 448-3567-12 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: unhandled wrmsr 2010-06-03 9:30 ` Andre Przywara @ 2010-06-03 9:52 ` Dave Young 2010-06-03 9:54 ` Dave Young 0 siblings, 1 reply; 12+ messages in thread From: Dave Young @ 2010-06-03 9:52 UTC (permalink / raw) To: Andre Przywara; +Cc: kvm@vger.kernel.org On Thu, Jun 3, 2010 at 5:30 PM, Andre Przywara <andre.przywara@amd.com> wrote: > Dave Young wrote: >> >> On Wed, Jun 2, 2010 at 8:45 PM, Andre Przywara <andre.przywara@amd.com> >> wrote: >>> >>> Dave Young wrote: >>>> >>>> Hi, >>>> >>>> With today's git version (qemu-kvm), I got following message in kernel >>>> dmesg >>>> >>>> [168344.215605] kvm: 27289: cpu0 unhandled wrmsr: 0x198 data 0 >>> >>> Are you sure about that? >> >> Sure >> >> 0x198 is an Intel architectural perfmon MSR and it >>> >>> is read-only. The Linux kernel source I grep'ed obeys this and does only >>> rdmsr. >>> You can work around this by changing the error to a warning with: >>> # modprobe kvm ignore_msrs=1 >> >> with this param, appear following warning: >> kvm: 28520: cpu0 ignored wrmsr: 0x198 data 0 > > As suspected. Did the boot succeed, then? Yes, boot ok even without "ignore_msrs=1" >> >>> I'd like to see more details about the guest Linux kernel, at least the >>> version you used to see why there is a wrmsr on this address. Best is you >>> provide the kernel (just the vmlinuz file) somewhere so that we can >>> reproduce this. Also the qemu-kvm command line would be interesting. >> >> Actually I tried different guest image, recreate this problem is easy. >> >> one of them is slackware 13.0 kernel version 2.6.29.6, you can download >> from: >> http://www.slackware.at/data/slackware64-13.0/kernels/huge.s/ > > Ah, nice to meet the other Slackware user ;-) me too :) > >> kvm cmdline: >> qemu-system-x86_64 -net nic -net tap,ifname=tap0,script=no slack64.img > > I tried: > $ x86_64-softmmu/qemu-system-x86_64 -kernel /boot/vmlinuz-huge-2.6.29.6 > -nographic -append "console=ttyS0,115200n8" -cpu > core2duo,model=26,stepping=5,vendor=GenuineIntel > This booted fine. > Sadly I had no access to an Intel box this morning, so I had to use vendor > override, but I guess this misses some features which an original Intel box > has. > Can you post the /proc/cpuinfo output from the guest? It seems that some > feature bits trigger the behavior in the guest. The host was an Xeon5520, > right? Here it is: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 2 model name : QEMU Virtual CPU version 0.12.50 stepping : 3 cpu MHz : 2925.956 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm up rep_good pni cx16 hypervisor lahf_lm bogomips : 5854.74 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: > > Regards, > Andre. > > -- > Andre Przywara > AMD-Operating System Research Center (OSRC), Dresden, Germany > Tel: +49 351 448-3567-12 > > -- Regards dave ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: unhandled wrmsr 2010-06-03 9:52 ` Dave Young @ 2010-06-03 9:54 ` Dave Young 0 siblings, 0 replies; 12+ messages in thread From: Dave Young @ 2010-06-03 9:54 UTC (permalink / raw) To: Andre Przywara; +Cc: kvm@vger.kernel.org On Thu, Jun 3, 2010 at 5:52 PM, Dave Young <hidave.darkstar@gmail.com> wrote: > On Thu, Jun 3, 2010 at 5:30 PM, Andre Przywara <andre.przywara@amd.com> wrote: >> Dave Young wrote: >>> >>> On Wed, Jun 2, 2010 at 8:45 PM, Andre Przywara <andre.przywara@amd.com> >>> wrote: >>>> >>>> Dave Young wrote: >>>>> >>>>> Hi, >>>>> >>>>> With today's git version (qemu-kvm), I got following message in kernel >>>>> dmesg >>>>> >>>>> [168344.215605] kvm: 27289: cpu0 unhandled wrmsr: 0x198 data 0 >>>> >>>> Are you sure about that? >>> >>> Sure >>> >>> 0x198 is an Intel architectural perfmon MSR and it >>>> >>>> is read-only. The Linux kernel source I grep'ed obeys this and does only >>>> rdmsr. >>>> You can work around this by changing the error to a warning with: >>>> # modprobe kvm ignore_msrs=1 >>> >>> with this param, appear following warning: >>> kvm: 28520: cpu0 ignored wrmsr: 0x198 data 0 >> >> As suspected. Did the boot succeed, then? > > Yes, boot ok even without "ignore_msrs=1" > >>> >>>> I'd like to see more details about the guest Linux kernel, at least the >>>> version you used to see why there is a wrmsr on this address. Best is you >>>> provide the kernel (just the vmlinuz file) somewhere so that we can >>>> reproduce this. Also the qemu-kvm command line would be interesting. >>> >>> Actually I tried different guest image, recreate this problem is easy. >>> >>> one of them is slackware 13.0 kernel version 2.6.29.6, you can download >>> from: >>> http://www.slackware.at/data/slackware64-13.0/kernels/huge.s/ >> >> Ah, nice to meet the other Slackware user ;-) > > me too :) > >> >>> kvm cmdline: >>> qemu-system-x86_64 -net nic -net tap,ifname=tap0,script=no slack64.img >> >> I tried: >> $ x86_64-softmmu/qemu-system-x86_64 -kernel /boot/vmlinuz-huge-2.6.29.6 >> -nographic -append "console=ttyS0,115200n8" -cpu >> core2duo,model=26,stepping=5,vendor=GenuineIntel >> This booted fine. >> Sadly I had no access to an Intel box this morning, so I had to use vendor >> override, but I guess this misses some features which an original Intel box >> has. >> Can you post the /proc/cpuinfo output from the guest? It seems that some >> feature bits trigger the behavior in the guest. The host was an Xeon5520, >> right? Forgot to tell host cpu is Intel Core2 Duo E7500 > > Here it is: > > processor : 0 > vendor_id : GenuineIntel > cpu family : 6 > model : 2 > model name : QEMU Virtual CPU version 0.12.50 > stepping : 3 > cpu MHz : 2925.956 > cache size : 4096 KB > fpu : yes > fpu_exception : yes > cpuid level : 4 > wp : yes > flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca > cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm up rep_good pni > cx16 hypervisor lahf_lm > bogomips : 5854.74 > clflush size : 64 > cache_alignment : 64 > address sizes : 40 bits physical, 48 bits virtual > power management: > >> >> Regards, >> Andre. >> >> -- >> Andre Przywara >> AMD-Operating System Research Center (OSRC), Dresden, Germany >> Tel: +49 351 448-3567-12 >> >> > > > > -- > Regards > dave > -- Regards dave ^ permalink raw reply [flat|nested] 12+ messages in thread
* unhandled wrmsr @ 2010-11-01 19:13 Ross Boylan 2010-11-03 13:51 ` Marcelo Tosatti 0 siblings, 1 reply; 12+ messages in thread From: Ross Boylan @ 2010-11-01 19:13 UTC (permalink / raw) To: kvm; +Cc: ross 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? Thanks. Ross P.S. Please cc me on reply. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: unhandled wrmsr 2010-11-01 19:13 Ross Boylan @ 2010-11-03 13:51 ` Marcelo Tosatti 0 siblings, 0 replies; 12+ messages in thread From: Marcelo Tosatti @ 2010-11-03 13:51 UTC (permalink / raw) To: Ross Boylan; +Cc: kvm 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. ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2014-12-04 10:05 UTC | newest] Thread overview: 12+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2010-06-02 8:44 unhandled wrmsr 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 -- strict thread matches above, loose matches on Subject: below -- 2010-11-01 19:13 Ross Boylan 2010-11-03 13:51 ` Marcelo Tosatti
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).