From: Arjan van de Ven <arjan@infradead.org>
To: Tomasz Torcz <zdzichu@irc.pl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
kvm-devel@lists.sourceforge.net
Subject: Re: overriding BIOS (was: Re: [ANNOUNCE] kvm howto)
Date: Mon, 13 Nov 2006 21:39:05 +0100 [thread overview]
Message-ID: <1163450346.15249.209.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20061113203421.GA5363@irc.pl>
On Mon, 2006-11-13 at 21:34 +0100, Tomasz Torcz wrote:
> On Mon, Nov 06, 2006 at 12:15:02AM -0800, Dor Laor wrote:
> > The BIOS check is a must, it checks bit #0 of MSR_IA32_FEATURE_CONTROL,
> > if it set this means that software cannot write to the MSR. If bit #2 is
> > clear too then when executing vmxon you'll get #GP.
> >
> > So the check should better be there...
>
> You were right, just writing to this MSR (via kvm_enable) halts my laptop.
> Which is kinda strange, as this solution works on Intel Mac Minis.
>
> Anyway, complaint to Lenovo sent and got ignored.
>
the linux-ready firmware developer kit now tries to test for this; with
some luck the bios people will run this and fix it ;)
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2006-11-13 20:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 13:25 [ANNOUNCE] kvm howto Avi Kivity
2006-11-02 14:27 ` Hesse, Christian
2006-11-02 14:32 ` Avi Kivity
2006-11-02 15:14 ` Magnus Damm
2006-11-02 15:19 ` Avi Kivity
2006-11-05 17:14 ` Tomasz Torcz
2006-11-06 8:15 ` Dor Laor
2006-11-13 20:34 ` overriding BIOS (was: Re: [ANNOUNCE] kvm howto) Tomasz Torcz
2006-11-13 20:39 ` Arjan van de Ven [this message]
2006-11-06 8:51 ` [ANNOUNCE] kvm howto Avi Kivity
2006-11-06 10:14 ` Arjan van de Ven
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=1163450346.15249.209.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zdzichu@irc.pl \
/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
all inboxes | Powered by JetHome®