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.
+++ This bug was initially created as a clone of Bug #2118195 +++
Currently, CentOS Stream 8 includes virt-what-1.18 with patches up to 1.22. This version outputs nothing when run inside Illumos/SmartOS LX, so virtual machines are incorrectly identified as bare metal.
virt-what 1.24 includes a patch (https://listman.redhat.com/archives/virt-tools-list/2022-May/017568.html) to support detecting Illumos/SmartOS LX. Could you update the CentOS Stream 8 package to include that patch (or point me to instructions on how to contribute that package update)?
--- Additional comment from Klaus Heinrich Kiwi on 2022-08-16 12:37:51 UTC ---
Not assigning to anyone yet, but maybe Miroslav could give us some pointers here?
--- Additional comment from Richard W.M. Jones on 2022-08-16 13:28:12 UTC ---
We could do this for RHEL 8.7 but it's extremely tight, particularly
for QE to do any testing. Yongkui what do you think?
Otherwise we'd move it to early in RHEL 8.8 cycle, but that would be
in a few months.
--- Additional comment from YongkuiGuo on 2022-08-17 02:10:56 UTC ---
(In reply to Richard W.M. Jones from comment #2)
> We could do this for RHEL 8.7 but it's extremely tight, particularly
> for QE to do any testing. Yongkui what do you think?
>
> Otherwise we'd move it to early in RHEL 8.8 cycle, but that would be
> in a few months.
Hi,rjones
It's ok from the QE side. In that case, the virt-what version (1.24) in RHEL8.7 will be higher than in RHEL9.1.
--- Additional comment from Richard W.M. Jones on 2022-08-17 09:33:22 UTC ---
(In reply to YongkuiGuo from comment #3)
> It's ok from the QE side. In that case, the virt-what version (1.24) in
> RHEL8.7 will be higher than in RHEL9.1.
That will break the upgrade path (LEAPP) so we can't actually do that,
unless we also upgrade virt-what in RHEL 9.1. We don't have a bug for
that (but bug 2114997 is the latest there).
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 (virt-what 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:8282