| 2018-04-30 18:08:21 |
dana |
bug |
|
|
added bug |
| 2018-05-18 15:39:30 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-05-18 15:39:30 |
Dimitri John Ledkov |
bug task added |
|
systemd (Ubuntu Bionic) |
|
| 2018-05-18 15:39:30 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Cosmic |
|
| 2018-05-18 15:39:30 |
Dimitri John Ledkov |
bug task added |
|
systemd (Ubuntu Cosmic) |
|
| 2018-05-18 15:39:47 |
Dimitri John Ledkov |
description |
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 |
Cherrypick https://github.com/systemd/systemd/commit/3776f9cf00b163eedeb0325691d23df11385cbc5
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 |
|
| 2018-05-18 19:04:36 |
Dimitri John Ledkov |
description |
Cherrypick https://github.com/systemd/systemd/commit/3776f9cf00b163eedeb0325691d23df11385cbc5
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 |
Cherrypick https://github.com/systemd/systemd/commit/f2fe2865cd19cd4318b82d01b9b62d22b1697b3a
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 |
|
| 2018-05-18 19:06:15 |
Dimitri John Ledkov |
systemd (Ubuntu Cosmic): status |
New |
Fix Committed |
|
| 2018-05-21 15:44:32 |
Dimitri John Ledkov |
description |
Cherrypick https://github.com/systemd/systemd/commit/f2fe2865cd19cd4318b82d01b9b62d22b1697b3a
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 |
[Impact]
* XEN virtualization missidentified as hyperv
* This may cause units limited to a virtualisation not to be started; or redundant units for the other type of virtualisation to be started instead.
* Previously xen & hyper-v were detected correctly separately, even when xen emulates/suggests that it is hyper-v.
[Test Case]
* Execute systemd-detect-virt and check that it detects Xen & Hyperv
[Regression Potential]
* Things that "fake" xen might not work as the detection code branches are changed, but it would affect previous releases and future releases of systemd-detect-virt. So far such things are not known to exist, and if such things appear in the future support for them would need to land upstream first.
[Other Info]
* Original bug report
Cherrypick https://github.com/systemd/systemd/commit/f2fe2865cd19cd4318b82d01b9b62d22b1697b3a
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 |
|
| 2018-05-24 10:08:09 |
Łukasz Zemczak |
systemd (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2018-05-24 10:08:11 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-05-24 10:08:13 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2018-05-24 10:08:17 |
Łukasz Zemczak |
tags |
|
verification-needed verification-needed-bionic |
|
| 2018-05-24 16:07:03 |
dana |
tags |
verification-needed verification-needed-bionic |
verification-done verification-done-bionic |
|
| 2018-05-24 16:09:19 |
dana |
tags |
verification-done verification-done-bionic |
verification-done-bionic verification-needed |
|
| 2018-05-25 10:53:35 |
Dimitri John Ledkov |
tags |
verification-done-bionic verification-needed |
verification-done verification-done-bionic |
|
| 2018-07-03 06:58:06 |
Steve Langasek |
tags |
verification-done verification-done-bionic |
verification-needed verification-needed-bionic |
|
| 2018-07-03 21:49:58 |
dana |
tags |
verification-needed verification-needed-bionic |
verification-done-bionic verification-needed |
|
| 2018-07-17 15:49:47 |
Dimitri John Ledkov |
tags |
verification-done-bionic verification-needed |
verification-done verification-done-bionic |
|
| 2018-07-19 12:13:45 |
Launchpad Janitor |
systemd (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-07-19 12:14:13 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-08-28 00:32:43 |
Launchpad Janitor |
systemd (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
