From: Peter Lieven <pl@dlh.net>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Dave Young <hidave.darkstar@gmail.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: unhandled wrmsr
Date: Wed, 02 Jun 2010 15:22:48 +0200 [thread overview]
Message-ID: <4C065B28.8080003@dlh.net> (raw)
In-Reply-To: <4C065257.5010809@amd.com>
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
.........................................................................................................
next prev parent reply other threads:[~2010-06-02 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 8:44 unhandled wrmsr Dave Young
2010-06-02 12:45 ` Andre Przywara
2010-06-02 13:22 ` Peter Lieven [this message]
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
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=4C065B28.8080003@dlh.net \
--to=pl@dlh.net \
--cc=andre.przywara@amd.com \
--cc=hidave.darkstar@gmail.com \
--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 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.