<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Microsoft Surface tablet detected as Virtual Machine through sysfs DMI string"
href="https://bugs.freedesktop.org/show_bug.cgi?id=78312">78312</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>Microsoft Surface tablet detected as Virtual Machine through sysfs DMI string
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>reyad.attiyat@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=98517" name="attach_98517" title="[PATCH] Remove Microsft DMI string from virtual detection">attachment 98517</a> <a href="attachment.cgi?id=98517&action=edit" title="[PATCH] Remove Microsft DMI string from virtual detection">[details]</a></span>
[PATCH] Remove Microsft DMI string from virtual detection
I have a Microsoft Surface 2 table and it is being detected as a virtual
machine with the Visualization attribute set to "microsoft". It is my
understanding that Microsoft offers virtuosity support via Hyper-V, and systemd
detects for this by checking cpuinfo and /sys/class/dmi/id/ sysinfo strings.
These heuristics incorrectly identity my device as a virtual machine because
the string "Microsoft Corporation\0" is found in /sys/class/dmi/id/board_vendor
and sys_vendor.
I have attached the a patch that removes this string from the array
dmi_vendor_table[]. Other possible solutions might be to send a kernel command
argument, or do more sophisticated DMI testing to ensure Hyper-V presence and
not a real hw device.
The only negative side effects I experienced by this bug were
gnome-settings-daemon would disable suspend but there might be other services
that act differently because of this.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>