kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Young <hidave.darkstar@gmail.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: unhandled wrmsr
Date: Thu, 3 Jun 2010 10:24:27 +0800	[thread overview]
Message-ID: <AANLkTinWnVYsuchYqNL1HUw84MpItwEtk8Y1O16FeGks@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinA-naETj6uDepdE5dF8gyPi4dWOTuGNwjMOKAx@mail.gmail.com>

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

  reply	other threads:[~2010-06-03  2:24 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
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 [this message]
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=AANLkTinWnVYsuchYqNL1HUw84MpItwEtk8Y1O16FeGks@mail.gmail.com \
    --to=hidave.darkstar@gmail.com \
    --cc=andre.przywara@amd.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 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).