Comment 0 for bug 1768104

It appears that Xen-based VMs sometimes report themselves as Microsoft Hyper-V via CPUID — apparently this is for compatibility with Windows guests. systemd 237 (as found in Bionic) gives preference to this CPUID information when detecting Xen, and thus it erroneously assumes that the guest is running under Hyper-V. This causes Xen-related services (and anything else that relies on systemd's VM-detection functionality) to fail.

I *believe* this is a regression from systemd 229 as used in Xenial — we have at least a few Xen-based VMs that report as Hyper-V via CPUID and don't have this issue on that version — but i haven't confirmed that for certain.

Anyway, i've submitted a ticket with more details to the up-stream project, and that has now been resolved through a fairly simple change which applies cleanly to the Bionic systemd sources:

https://github.com/systemd/systemd/issues/8844

Would it be possible to pull this down? As mentioned, Xen-based Ubuntu VMs can seriously misbehave without it.

Thanks!

See also: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573

---

% lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04

% apt-cache policy systemd
systemd:
  Installed: 237-3ubuntu10
  Candidate: 237-3ubuntu10
  Version table:
 *** 237-3ubuntu10 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status