public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Michael Hanselmann
	<linux-kernel-ujPHhMiOvBLtRgLqZ5aouw@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Panic when loading kvm-amd.ko
Date: Sun, 17 Jun 2007 18:37:19 +0300	[thread overview]
Message-ID: <4675552F.9000204@qumranet.com> (raw)
In-Reply-To: <20070617152725.GA18777-ujPHhMiOvBLtRgLqZ5aouw@public.gmane.org>

Michael Hanselmann wrote:
> Hello
>
> When loading kvm-amd.ko on an HP DL-145 G5 with one AMD Opteron 2216 HE
> (2 cores, 2.4 GHz), I get a kernel panic. I tried to find the exact
> cause but was unable to do so. It doesn't crash when I add a "return"
> before "wrmsrl(MSR_EFER, efer | MSR_EFER_SVME_MASK);" in
> svm_hardware_enable. The backtrace always originates from different
> functions, but ends up in interrupt handling every time. This isn't a
> regression because it has been happening since at least
> 2.6.20.something, but I never bothered to look into it. If you need any
> more info, please let me know.
>
> I reproduced it with vanilla-2.6.21.5, vanilla-2.6.22-rc5 and current
> KVM git. Architecture is x86_64. GCC version is "gcc (GCC) 3.4.6 (Gentoo
> Hardened 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10)".
>   

This looks remarkably similar to 
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/3399.  The 
conclusion was

> I went through my BIOS settings and found:
> "Advanced BIOS Features" -> "CPU Feature" -> Virtualization
>
> However this was already set to "Enabled". I tried changing the value 
> to "Disabled" and now KVM works fine. Stupid ABIT...

I suggest trying the same, as well as a bios upgrade.

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


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

  parent reply	other threads:[~2007-06-17 15:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17 15:27 Panic when loading kvm-amd.ko Michael Hanselmann
     [not found] ` <20070617152725.GA18777-ujPHhMiOvBLtRgLqZ5aouw@public.gmane.org>
2007-06-17 15:37   ` Avi Kivity [this message]
     [not found]     ` <4675552F.9000204-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-17 17:54       ` Michael Hanselmann
     [not found]         ` <20070617175417.GA19120-ujPHhMiOvBLtRgLqZ5aouw@public.gmane.org>
2007-06-17 18:31           ` Avi Kivity
     [not found]             ` <46757DF3.9030306-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-18 10:55               ` Joerg Roedel
     [not found]                 ` <20070618105543.GB32587-5C7GfCeVMHo@public.gmane.org>
2007-06-18 11:09                   ` Michael Hanselmann
2007-06-18 16:32               ` Joerg Roedel
2007-06-18  7:57   ` René Nussbaumer
     [not found]     ` <20070618075744.GB15801-VjcCyyTFwywzTaTVwmJQuKeUGLeIa1b/@public.gmane.org>
2007-06-18  9:34       ` 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=4675552F.9000204@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-ujPHhMiOvBLtRgLqZ5aouw@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