Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionRazvan Corneliu C.R. VILT
2021-05-10 19:18:32 UTC
Systemd doesn't recognize ESXi as a hypervisor. The v244-rc1 2-line patch applies cleanly to both the EL7 v219 tree and the EL8 v235 tree and solves this issue. It is not required for
It is a blocker for open-vm-tools AARCH64 support.
The patch can be located at: https://github.com/systemd/systemd/commit/4d4ac92c928fcbc60b85fcbf8370af3883ee63db.patch
As soon as I create all the bugs (open-vm-tools, virt-what) I will update the dependency tree.
Hi Jan,
From the Descirption, systemd-detec-virt shouldn't print 'vmware' when VM(systemd < 239-53.el8) was built in ESXi ARM host, right?
We have isntalled a RHEL-8.6.0-20211216.2-aarch64 (systemd-239-53.el8) and a RHEL-8.6.0-20211121.1-aarch64 (systemd-239-51.el8), both can print 'vmware' or recognize ESXi, so do we understand this issue wrong?
Thanks.
(In reply to Bo Yang from comment #5)
> Hi Jan,
>
> From the Descirption, systemd-detec-virt shouldn't print 'vmware' when
> VM(systemd < 239-53.el8) was built in ESXi ARM host, right?
> We have isntalled a RHEL-8.6.0-20211216.2-aarch64 (systemd-239-53.el8) and a
> RHEL-8.6.0-20211121.1-aarch64 (systemd-239-51.el8), both can print 'vmware'
> or recognize ESXi, so do we understand this issue wrong?
Yes, you do understand this wrong. The patch adds an *additional* way to detect VMware virtualization in case DMI detection doesn't work. That's because there is no simple/standardized way to get this info and the whole thing is just guesswork based on various bits of data gleaned from the system.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:2069