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.

Description of problem:
The CCSP Cloud Certification suite would like a supported, standard way to determine that a RHEL guest is running on a RHEL hypervisor, in order to determine that we are running on a certified host.

This ability has been added to virt-what upstream in commit

http://git.annexia.org/?p=virt-what.git;a=commitdiff;h=b64df398779db07d008781c96685878795bcfd67

We would like this back-ported to RHEL-9.


Version-Release number of selected component (if applicable):
virt-what-1.21-2.el9.2


How reproducible:
100%


Steps to Reproduce:
1. On a RHEL guest on a RHEL hypervisor, run:
   $ sudo virt-what


Actual results:
kvm


Expected results:
redhat
kvm

This is also available as updates to Fedora 35-37 if you want to try it there:

https://bodhi.fedoraproject.org/updates/FEDORA-2022-84347c3e67
https://bodhi.fedoraproject.org/updates/FEDORA-2022-0371db51d4
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a664f389d5

Tested with virt-what-1.22-1.el9.x86_64:

On KVM:
[root@rhel9-1-virt-what home]# virt-what
redhat
kvm

On nested KVM:
[root@localhost ~]# virt-what
redhat
kvm

On TCG:
[root@localhost ~]# virt-what
redhat
qemu

Notes: tier1 gating tests also passed on AWS(including Xen, KVM, Bare Metal), ESXi, Hyper-V(https://dashboard.osci.redhat.com/#/artifact/brew-build/aid/44637584).

Verified this bug per comment 3.

Verified on Nutanix(guest: RHEL-8.7.0-20220614.0, RHEL-9.1.0-20220612.2):

# virt-what
nutanix_ahv
redhat
kvm

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