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.
Bug 1984630 - Nutanix AHV is detected as hyperv [rhel-7.9.0.z]
Summary: Nutanix AHV is detected as hyperv [rhel-7.9.0.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-what
Version: 7.9
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: YongkuiGuo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-21 19:29 UTC by Rick Barry
Modified: 2021-08-31 11:00 UTC (History)
15 users (show)

Fixed In Version: virt-what-1.18-4.el7_9.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-31 09:10:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:3331 0 None None None 2021-08-31 09:10:58 UTC

Description Rick Barry 2021-07-21 19:29:06 UTC
This is the RHEL 7.9 version of the RHEL 8.5 bug 1756381.

Description of problem:
virt-what shows Nutanix AHV platform as "hyperv"

Version-Release number of selected component (if applicable):
virt-what-1.18-6.el8.x86_64 tested on CentOS Linux release 8.0.1905

How reproducible:
always

Steps to Reproduce:
1. use RHEL on Nutanix AHV platform (tested with Nutanix 20170830.301)
2. run virt-what


Actual results:
output is "hyperv"

Expected results:
output "ahv" and documentation updated to include Nutanix AHV platform

Comment 5 Richard W.M. Jones 2021-07-22 07:45:48 UTC
Not sure why, but we don't have all the required flags yet:

remote: *** Resolves:
remote: ***   Unapproved:
remote: ***     rhbz#1984630 (qa_ack+, internal_target_release=7.9.z, devel_ack+, mirror+, release?, stale-, zstream+, Triaged)
...
remote: *** Current checkin policy requires:
remote:     ((rhel-7.9.0 == + and blocker == +) or rhel-7.9.z == +)

Comment 6 Rick Barry 2021-07-22 10:47:50 UTC
(In reply to Richard W.M. Jones from comment #5)
> Not sure why, but we don't have all the required flags yet:
> 
> remote: *** Resolves:
> remote: ***   Unapproved:
> remote: ***     rhbz#1984630 (qa_ack+, internal_target_release=7.9.z,
> devel_ack+, mirror+, release?, stale-, zstream+, Triaged)
> ...
> remote: *** Current checkin policy requires:
> remote:     ((rhel-7.9.0 == + and blocker == +) or rhel-7.9.z == +)

The RHEL 7.9 z-stream approval process is a little different than RHEL 8.x and requires manually setting release+.

Jaroslav, can we get release+ approval for this 7.9.z BZ? This is one of a set of three ( 7.9.z, 8.2.z and 8.4.z) that we are trying to get out in the next scheduled batch update series.

Comment 9 YongkuiGuo 2021-07-23 08:06:14 UTC
rjones, please help put the virt-what-1.18-4.el7_9.1 package on http://oirase.annexia.org/tmp/bz..., thanks.

Comment 10 Richard W.M. Jones 2021-07-23 08:10:04 UTC
http://oirase.annexia.org/tmp/bz1984630-vw/

Comment 11 YongkuiGuo 2021-07-23 08:15:49 UTC
Cristian, could you have a try with virt-what-1.18-4.el7_9.1 package (comment 10) on Nutanix AHV?

Comment 12 Cristian Seres 2021-07-23 10:59:09 UTC
(In reply to YongkuiGuo from comment #11)
> Cristian, could you have a try with virt-what-1.18-4.el7_9.1 package
> (comment 10) on Nutanix AHV?

Hi,

it works on Nutanix AHV:

[cristian@s21 ~]$ sudo virt-what
nutanix_ahv
[cristian@s21 ~]$ cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)
[cristian@s21 ~]$ uname -r
3.10.0-1160.31.1.el7.x86_64
[cristian@s21 ~]$ rpm -q virt-what
virt-what-1.18-4.el7_9.1.x86_64
[cristian@s21 ~]$

Comment 13 Richard W.M. Jones 2021-07-23 11:24:19 UTC
Thanks for testing this.

Comment 14 YongkuiGuo 2021-07-23 11:32:57 UTC
Thanks, Cristian.

It also works fine on KVM, ESXi, Hyper-V and AWS platforms.

On ESXi:
[root@bootp-73-199-170 ~]# rpm -q virt-what
virt-what-1.18-4.el7_9.1.x86_64
[root@bootp-73-199-170 ~]# virt-what
vmware


On KVM:
[root@localhost ~]# rpm -Uvh virt-what-1.18-4.el7_9.1.x86_64.rpm 
Preparing...                          ################################# [100%]
Updating / installing...
   1:virt-what-1.18-4.el7_9.1         ################################# [ 50%]
Cleaning up / removing...
   2:virt-what-1.18-4.el7             ################################# [100%]
[root@localhost ~]# virt-what
kvm


On AWS and Hyper-V:
Please check the results: https://dashboard.osci.redhat.com/#/artifact/brew-build/aid/38299831

Comment 18 errata-xmlrpc 2021-08-31 09:10:56 UTC
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-2021:3331


Note You need to log in before you can comment on or make changes to this bug.