Messages in this thread | | | Date | Fri, 26 Feb 2010 11:16:44 -0800 | From | Greg KH <> | 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@kroah.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
| |