From: Michael Riepe <michael-0QoEqw4nQxo@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [ANNOUNCE] kvm userspace release 6
Date: Tue, 12 Dec 2006 18:42:48 +0100 [thread overview]
Message-ID: <457EEA18.70204@mr511.de> (raw)
In-Reply-To: <457E939C.1030501-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Hi!
Avi Kivity wrote:
> Michael Riepe wrote:
>
>> By the way: I get myriads of "kvm: unhandled rdmsr: c0000081" messages
>> in my syslog, but they don't seem to cause any further harm.
>>
>
>
> Which guest does this happen with? AFAICT this should be handled well
> (vmx.c:vmx_get_msr() -> find_msr_entry())
With all of them.
> If you'd like to debug this, you can add printk()s to see where
> vmx_get_msr() loses its way.
vmx_get_msr() actually works fine. The problem is in vmx_vcpu_setup(),
in the loop starting at line 1142. It tries to read all the MSRs listed
in vmx_msr_index, but it fails for MSR_K6_STAR. With earlier releases, I
also used to see the kernel message "kvm: msrs: 1" - that is, only
MSR_EFER is found. According to Intel's docs, that's correct - the
register does not exist on a Core Duo which isn't 64-bit capable (but,
of course, on a Core 2 Duo - or a Xeon 51xx/53xx, aka "Woodcrest" and
"Clovertown").
--
Michael "Tired" Riepe <michael-0QoEqw4nQxo@public.gmane.org>
X-Tired: Each morning I get up I die a little
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-12-12 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 11:37 [ANNOUNCE] kvm userspace release 6 Avi Kivity
[not found] ` <457D42F3.3000000-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-12-11 17:39 ` Michael Riepe
[not found] ` <457D97ED.6090606-0QoEqw4nQxo@public.gmane.org>
2006-12-11 22:55 ` Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E03216097F009E-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2006-12-12 7:27 ` Michael Riepe
[not found] ` <457E59EB.5040506-0QoEqw4nQxo@public.gmane.org>
2006-12-12 7:52 ` Avi Kivity
[not found] ` <457E5FC0.7080303-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-12-12 8:00 ` Michael Riepe
[not found] ` <457E61B8.4030607-0QoEqw4nQxo@public.gmane.org>
2006-12-12 10:49 ` Avi Kivity
2006-12-12 9:25 ` Gerd Hoffmann
[not found] ` <457E756F.4070701-l3A5Bk7waGM@public.gmane.org>
2006-12-12 16:20 ` Michael Riepe
2006-12-12 7:52 ` Avi Kivity
2006-12-12 10:59 ` Avi Kivity
2006-12-12 11:33 ` Avi Kivity
[not found] ` <457E939C.1030501-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-12-12 17:42 ` Michael Riepe [this message]
[not found] ` <457EEA18.70204-0QoEqw4nQxo@public.gmane.org>
2006-12-12 18:05 ` Avi Kivity
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=457EEA18.70204@mr511.de \
--to=michael-0qoeqw4nqxo@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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