This bug was fixed in the package systemd - 237-3ubuntu10.53
---------------
systemd (237-3ubuntu10.53) bionic; urgency=medium
[ Ratchanan Srirattanamet ]
* d/p/debian/timedatectl-lp1650688.patch,
d/p/debian/UBUNTU-Fix-timezone-setting-on-read-only-etc.patch:
Fix timedated unable to retrieve & properly set timezone on
read-only /etc (e.g. Ubuntu Core and system-image-based systems)
(LP: #1650688)
[ Lukas Märdian ]
* Support detection for ARM64 Hyper-V guests (LP: #1952599)
-- Lukas Märdian <sl...@ubuntu.com> Fri, 10 Dec 2021 10:15:49 +0100
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952599
Title:
virt: Support detection for ARM64 Hyper-V guests (fixed upstream)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in systemd source package in Hirsute:
New
Status in systemd source package in Impish:
Fix Released
Status in systemd source package in Jammy:
Fix Released
Bug description:
[Impact]
* The detection of Microsoft Hyper-V VMs is done by cpuid currently,
however there is no cpuid on ARM64. And since ARM64 is now a supported
architecture for Microsoft Hyper-V guests[0], then introduce a more
generic way to detect whether a guest is running as a Hyper-V guest: check
if /sys/class/dmi/id/product_version starts with "Hyper-V".
* This bug has already been fixed upstream[1][2]
[Test Plan]
* While changes have been made in the kernel for ARM64 on Hyper-V,
there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we
just want to make sure no regression is introduced.
* start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still
return MSFT (should still rely on cpuid here)
[Where problems could occur]
* The main risk is for the system to detect Hyper-V virt erroneously.
An issue was reported upstream after the first commit was merged[3].
For this reason, systemd is now looking for "Hyper-V" (in
/sys/class/dmi/id/product_version) and not "Microsoft" (in
/sys/class/dmi/id/bios_vendor)
* This change might also break virt detection on hyper-v AMD64.
That's why we need testing. However, AMD64 virt detection should still
rely on cpuid instead of DMI as cpuid takes priority over DMI.
[0]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467
[1] https://github.com/systemd/systemd/pull/20998/files
[2] https://github.com/systemd/systemd/pull/21475/files
[3] https://github.com/systemd/systemd/issues/21468
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952599/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
