[systemd-bugs] [Bug 78312] Microsoft Surface tablet detected as Virtual Machine through sysfs DMI string

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon May 5 22:49:03 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=78312

--- Comment #2 from reyad.attiyat at gmail.com <reyad.attiyat at gmail.com> ---
Sorry about the initial comment it contains so many wording/spelling errors.

(In reply to comment #1)
> It seems like this patch would switch the bug to failing to detect Hyper-V
> when present, unless there's reason to believe this check is redundant.

I have tested Fedora 20 in a Hyper-V VM and it gets detected by the cpuid x86
instructions and does not ever check the DMI values. These Microsoft hypervisor
detection steps can be found here (link found in source code comment):
http://www.microsoft.com/en-ca/download/details.aspx?id=39289
as well as here:
http://lwn.net/Articles/301888/

Should this cpuid method be enough to detect Hyper-V? I can't really think of
any other device that would have a Microsoft BIOS/EFI.

I also checked the DMI information in the Hyper-V VM. The
/sys/class/dmi/id/bios_vendor reads "American Megatrends Inc." on both the
surface tablet and virtual machine. I was hoping this could be used to
differentiate virtual from real hardware. The values that did differ were
/sys/class/dmi/id/product_name and /sys/class/dmi/id/board_name. They read
"Virtual Machine" when on the vm. Would it make more sense, instead of deleting
the DMI Microsoft vendor string , to also check if board_name is equal to
"Virtual Machine"?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140506/ddaea3d4/attachment-0001.html>


More information about the systemd-bugs mailing list