linux-kernel - Re: Problem with auto-detecting a HV environment from within Linux

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]

Date:	Fri, 26 Feb 2010 11:16:44 -0800
From:	Greg KH <greg@...ah.com>
To:	Haiyang Zhang <haiyangz@...rosoft.com>
Cc:	Hank Janssen <hjanssen@...rosoft.com>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Problem with auto-detecting a HV environment from within Linux

On Fri, Feb 26, 2010 at 07:07:14PM +0000, Haiyang Zhang wrote:
> > From: Greg KH [mailto:greg@...ah.com]
> > Sent: Thursday, February 25, 2010 9:57 PM
> > In looking at the second patch again, I think you will need to put some
> > spaces in the DMI strings to get it to match up properly.  Look at what
> > the files in:
> > 	/sys/class/dmi/id/
> > look like exactly to get it to line up.  The module id stuff strips
> > spaces out, so I can't get the real value there.
> 
> Thanks for your help! I have applied the two patches -- auto loading
> of hv_vmbus works fine after a space was inserted into the DMI strings
> ("Microsoft Corporation", "Virtual Machine").

Great, I'll add a space and then queue them up for the merge window.

> Also, according to our Hyper-V team, we have no plan to change the
> virtual VGA card id and DMI info.

That's good to know, but if it changes in the future, we can trivially
add new device ids.

thanks,

greg k-h
--
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/