public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Torcz <zdzichu@irc.pl>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: kvm-devel@lists.sourceforge.net
Subject: overriding BIOS (was: Re: [ANNOUNCE] kvm howto)
Date: Mon, 13 Nov 2006 21:34:21 +0100	[thread overview]
Message-ID: <20061113203421.GA5363@irc.pl> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E0321608EBF537@ehost011-8.exch011.intermedia.net>

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

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.

-- 
Tomasz Torcz       ,,(...) today's high-end is tomorrow's embedded processor.''
zdzichu@irc.-nie.spam-.pl                      -- Mitchell Blank on LKML


[-- Attachment #2: Type: application/pgp-signature, Size: 229 bytes --]

  reply	other threads:[~2006-11-13 20:34 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     ` Tomasz Torcz [this message]
2006-11-13 20:39       ` overriding BIOS (was: Re: [ANNOUNCE] kvm howto) Arjan van de Ven
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=20061113203421.GA5363@irc.pl \
    --to=zdzichu@irc.pl \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@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