From: Greg KH <greg@kroah.com>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: Hank Janssen <hjanssen@microsoft.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Problem with auto-detecting a HV environment from within Linux
Date: Thu, 25 Feb 2010 09:36:11 -0800 [thread overview]
Message-ID: <20100225173611.GA14124@kroah.com> (raw)
In-Reply-To: <1FB5E1D5CA062146B38059374562DF725B6A4277@TK5EX14MBXC130.redmond.corp.microsoft.com>
On Thu, Feb 25, 2010 at 05:30:29PM +0000, Haiyang Zhang wrote:
> > From: Greg KH [mailto:greg@kroah.com]
> > So, is there a way to "know" ahead of time if we are in a HV guest
> > environment?
>
> Here is some info from dmesg, which shows "VRTUAL MICROSFT".
> ACPI: RSDT (v001 VRTUAL MICROSFT 0x03000919 MSFT 0x00000097) @ 0x000000001fff0000
> ACPI: FADT (v002 VRTUAL MICROSFT 0x03000919 MSFT 0x00000097) @ 0x000000001fff0200
> ACPI: WAET (v001 VRTUAL MICROSFT 0x03000919 MSFT 0x00000097) @ 0x000000001fff0b00
> ACPI: SLIC (v001 VRTUAL MICROSFT 0x03000919 MSFT 0x00000097) @ 0x000000001fff0b40
> ACPI: OEM0 (v001 VRTUAL MICROSFT 0x03000919 MSFT 0x00000097) @ 0x000000001fff0d40
> ACPI: SRAT (v002 VRTUAL MICROSFT 0x03000919 MSFT 0x00000097) @ 0x000000001fff0600
> ACPI: MADT (v001 VRTUAL MICROSFT 0x03000919 MSFT 0x00000097) @ 0x000000001fff0300
> ACPI: OEMB (v001 VRTUAL MICROSFT 0x03000919 MSFT 0x00000097) @ 0x000000001ffff240
> ACPI: DSDT (v001 MSFTVM MSFTVM02 0x00000002 INTL 0x02002026) @ 0x0000000000000000
That's a good start, so which device can we key off of here?
What does the following command output in a HV virtual system:
grep . /sys/bus/acpi/devices/*/modalias
That might give us something that we can use.
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
And you are sure no PCI devices are present to key off of that are never
going to show up in a "physical" machine?
What do you recommend doing here?
thanks,
greg k-h
next prev parent reply other threads:[~2010-02-25 17:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 16:44 Problem with auto-detecting a HV environment from within Linux Greg KH
2010-02-25 17:30 ` Haiyang Zhang
2010-02-25 17:36 ` Greg KH [this message]
2010-02-25 18:37 ` Haiyang Zhang
2010-02-25 23:06 ` Greg KH
2010-02-25 23:40 ` Haiyang Zhang
2010-02-26 0:21 ` Greg KH
2010-02-26 0:46 ` Greg KH
2010-02-26 2:14 ` Hank Janssen
2010-02-26 2:57 ` Greg KH
2010-02-26 19:07 ` Haiyang Zhang
2010-02-26 19:16 ` Greg KH
2010-02-26 9:47 ` Ameya Palande
2010-02-26 14:54 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100225173611.GA14124@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox