Bug#1000396: systemd-detect-virt falsely detects "Microsoft" virtualisation

[Liban Parker Hannan]

Hi Michael,

I can see from the upstream issue that the problem has been fixed with
a fairly small code change. Would it be possible to carry the fix as a
patch in the debian package until the fix makes it into a stable
release?

https://github.com/systemd/systemd/commit/76eec0649936d9ae2f9087769f463feaf0cf5cb4.patch



On Mon, 22 Nov 2021 17:40:05 +0100 Michael Biebl <biebl at debian.org>
wrote:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/21468
> 
> Am 22.11.21 um 16:37 schrieb Michael Biebl:
> > On 22.11.21 14:06, Liban Hannan wrote:
> > 
> >> systemd-detect-virt checks /sys/class/dmi/id/sys_vendor as part of
its
> >> attempt to detect if the system is virtualised. I am using a
Surface
> >> Laptop so sys_vendor returns "Microsoft Corporation" which (as far
as I
> >> can tell) the program assumes indicates the presence of hyper-v
rather
> >> than Microsoft produced hardware. One of the consequences is that
> >> systemd units that won't run in a VM fail, such as thermald.
> > 
> > Would you mind forwarding this issue to upstream by filing an issue
at 
> > https://github.com/systemd/systemd/issues
> 
> I've filed it as https://github.com/systemd/systemd/issues/21468
> 
> Please consider subscribing to this upstream bug report in case
upstream 
> has further questions.
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20211128/509f311b/attachment.htm>