This bug was fixed in the package systemd - 245.4-4ubuntu3.14
---------------
systemd (245.4-4ubuntu3.14) focal; urgency=medium
[ Lukas Märdian ]
* Allow target units to fail (LP: #1948476)
File: d/p/lp1948476-pid1-target-units-can-fail-through-dependencies.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fe0cb0bd66baea89d8bbe47cb47d88540f46d470
* Fix whitespace in
lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch to match
upstream
File:
debian/patches/lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=80fef80a1b018556939011707c4ce00cebc58806
* Support detection for ARM64 Hyper-V guests (LP: #1952599)
Files:
-
debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch
- debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=caf3aff933cc7bf21565faba05f78ce78b3196cd
[ Andy Chi ]
* Add privacy micmute hotkey for Dell machine. (LP: #1952733)
File:
debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ff8dc41f55baa418076e42509ddbf3212a8c1353
* Add microphone mute key for Dell machine. (LP: #1952735)
File:
debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=175fb4e209fba889b4bcd81cb2ed262923943a3f
[ Yao Wei ]
* Add ACCEL_LOCATION=base property for 6 Dell clamshell models (LP: #1943561)
File:
debian/patches/lp1943561-dell-clamshell-accel-location-base-with-sku.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=246195d68b2bb0473f4a3f1c2ebe54dfd37f068b
[ Dan Streetman ]
* d/p/lp1944711-login-filenames-in-run-systemd-users-are-uids.patch:
Fix systemd-logind restart loading of existing sessions
(LP: #1944711)
[ 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 <sl...@ubuntu.com> Fri, 10 Dec 2021 10:04:02 +0100
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
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
