linux-kernel - Re: overriding BIOS (was: Re: [ANNOUNCE] kvm howto)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1163450346.15249.209.camel@laptopd505.fenrus.org>
Date:	Mon, 13 Nov 2006 21:39:05 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Tomasz Torcz <zdzichu@....pl>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	kvm-devel@...ts.sourceforge.net
Subject: Re: overriding BIOS (was: Re: [ANNOUNCE] kvm howto)

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/