linux-kernel - Re: [PATCH 1/2] VMware guest detection for x86 and x86-64

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 25 Sep 2008 08:32:20 +0800
From:	Yan Li <elliot.li.tech@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Yan Li <elliot.li.tech@...il.com>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>, joerg.roedel@....com,
	rjmaomao@...il.com, Yinghai Lu <yhlu.kernel@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>, nancydreaming@...il.com
Subject: Re: [PATCH 1/2] VMware guest detection for x86 and x86-64

On Wed, Sep 24, 2008 at 09:19:19AM -0700, H. Peter Anvin wrote:
> Yan Li wrote:
>> I haven't used PCI vendor Id since that requires copying a trunk of
>> codes from early_quirks() and I think copying code is not good. And
>> reusing codes from early_quirks() needs intrivial change to present
>> codes structure. Comparatively, checking "VMware" string against DMI
>> manufacturer is a lot more simpler (one-line code). Also there's no
>> evidence indicating that VMware will change their vendor string in
>> near future. Therefore I choose to use simpler way.
>>
>> Tested on x86 and x86-64 VMs and machines.
>
> I'd like to make this a general VM platform detection subsystem.  We  
> have similar issues with Virtual PC, and again, DMI appears to be the  
> sanest way to detect it -- at least to a primary screen.

I think if Virtual PC has similar problems we should add codes to
detect Virtual PC to be used by mtrr/main.c. A general interface might
not be good for this specific problem (false MTRR blank warning) since
we have no way to know all VMs has MTRR set to blank thus handling
KVM, VMware and Virtual PC here should be enough for now.

If you can tell me what manufacture vendor string is in Virtual PC I
can make another similar patch using dmi_name_in_vendors().

So at first I'd like to see the false warning for VMware and Virtual
PC get fixed soon.

-- 
Li, Yan
--
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/