All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: TJ <linux-A+nqLdfjWwLR7s880joybQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Bug: cpu0 unhandled rdmsr: 0x1900 and	inject_general_protection
Date: Thu, 08 Nov 2007 15:02:40 +0200	[thread overview]
Message-ID: <473308F0.4050504@qumranet.com> (raw)
In-Reply-To: <1194523650.20087.16.camel@hephaestion>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

TJ wrote:
> Trying to run the latest OLPC XO guest image with kvm-intel on 2.6.22
> x86_64 (Ubuntu Gutsy) on a T7200 there are critical problems which don't
> occur if kvm-intel is not loaded/used.
>
> The same issue affects kvm-48, kvm-50 and kvm-51.
>
> I don't see these problems with Gutsy or Windows guests. The issues are:
>
> 1. Start-up of the image into GRUB is _slow_. The cursor can be seen
> scanning as the GRUB menu is drawn. It is *much* faster when kvm-intel
> isn't loaded/used.
>
> 2. After choosing a boot option the guest freezes and the host kern.log
> reports:
>
> kernel: [88380.014893] kvm: 12666: cpu0 unhandled rdmsr: 0x1900
> kernel: [88380.014900] inject_general_protection: rip 0xc07211ab
>
> 3. Guest locks up at this point with host CPU being driven 100% and requires killing.
>
>
> I'm guessing they may be related to the OLPC kernel expecting an AMD Geode CPU?
>
> ./include/asm-i386/msr.h
> #define MSR_GEODE_BUSCONT_CONF0 0x1900
>
>   

Very likely.  Try the attached patch.  The guest may hang later with 
another bad msr; you can simply add more registers as necessary.

I think we can add an API to do this from userspace, to avoid the need 
to patch the kernel for hundreds of no-op msrs.


-- 
error compiling committee.c: too many arguments to function


[-- Attachment #2: geode.patch --]
[-- Type: text/x-patch, Size: 377 bytes --]

diff --git a/kernel/x86.c b/kernel/x86.c
index e905d46..71307cb 100644
--- a/kernel/x86.c
+++ b/kernel/x86.c
@@ -460,6 +460,7 @@ int kvm_get_msr_common(struct kvm_vcpu *vcpu, u32 msr, u64 *pdata)
 	case MSR_IA32_UCODE_REV:
 	case MSR_IA32_PERF_STATUS:
 	case MSR_IA32_EBL_CR_POWERON:
+	case MSR_GEODE_BUSCONT_CONF0:
 		/* MTRR registers */
 	case 0xfe:
 	case 0x200 ... 0x2ff:

[-- Attachment #3: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #4: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

  reply	other threads:[~2007-11-08 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 12:07 Bug: cpu0 unhandled rdmsr: 0x1900 and inject_general_protection TJ
2007-11-08 13:02 ` Avi Kivity [this message]
     [not found]   ` <473308F0.4050504-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-09 14:05     ` TJ
2007-11-11 10:04       ` 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=473308F0.4050504@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-A+nqLdfjWwLR7s880joybQ@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 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.