[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100225230639.GB20900@kroah.com>
Date: Thu, 25 Feb 2010 15:06:39 -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 Thu, Feb 25, 2010 at 06:37:05PM +0000, Haiyang Zhang wrote:
> > From: Greg KH [mailto:greg@...ah.com]
> > Sent: Thursday, February 25, 2010 12:36 PM
> > What does the following command output in a HV virtual system:
> > grep . /sys/bus/acpi/devices/*/modalias
>
> /sys/bus/acpi/devices/VMBus:00/modalias:acpi:VMBus:
>
> > How about DMI data? Does the Host export any info there? Is there
> > anything in the /sys/class/dmi/id/ directory? If so, can you send the
> > output of:
> > cat /sys/class/dmi/id/modalias
>
> dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
Nice, can we rely on this to be static? Will the following structure always
match properly?
static struct dmi_system_id __initdata microsoft_hyperv_table[] = {
{
.ident = "hyperv",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "MicrosoftCorporation"),
DMI_MATCH(DMI_PRODUCT_NAME, "VirtualMachine"),
DMI_MATCH(DMI_BOARD_NAME, "VirtualMachine"),
},
},
};
That would be good to match with, but I don't know if all distro tools
can properly handle DMI module stuff just yet.
> > And you are sure no PCI devices are present to key off of that are
> > never going to show up in a "physical" machine?
>
> There is also a pci device as you said:
> 00:08.0 VGA compatible controller: Microsoft Corporation Device 5353 (prog-if 00 [VGA controller])
> Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 11
> Region 0: Memory at f8000000 (32-bit, non-prefetchable) [size=64M]
Ah, nice. Can we rely on this always being present?
If so, what is the vendor and product id of this device?
Is it:
Vendor id 0x1414
or:
Vendor id 0x045e
Microsoft has both assigned to them, and probably others.
Is the device id 0x5353?
You can see this by doing the following:
lspci -n | grep 08\\.0
what is the output of that?
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/
Powered by blists - more mailing lists