Checked this on our DELL hardware, didn't observed it:

# dmidecode | grep -A 10 "System Information" | grep -E "Manufacturer|Product Name"
        Manufacturer: Nutanix
        Product Name: AHV

(In reply to Shaoyu Shang from comment #1)
> Checked this on our DELL hardware, didn't observed it:
> 
> # dmidecode | grep -A 10 "System Information" | grep -E
> "Manufacturer|Product Name"
>         Manufacturer: Nutanix
>         Product Name: AHV

This is on baremetal or in a VM?

(In reply to Richard W.M. Jones from comment #2)
> (In reply to Shaoyu Shang from comment #1)
> > Checked this on our DELL hardware, didn't observed it:
> > 
> > # dmidecode | grep -A 10 "System Information" | grep -E
> > "Manufacturer|Product Name"
> >         Manufacturer: Nutanix
> >         Product Name: AHV
> 
> This is on baremetal or in a VM?

This is from RHEL9 guest VM. This RHEL9 VM in running on Nutanix AHV, and the Nutanix AHV is running on DELL servers.

To be more clearly, this is the outputs from AHV which is running on my DELL hardware:
  # dmidecode | grep -A 10 "System Information" | grep -E "Manufacturer|Product Name"
          Manufacturer: Dell Inc.
          Product Name: PowerEdge R740xd

And this is the outputs in the RHEL9 guest VM which is running on AHV:
  # dmidecode | grep -A 10 "System Information" | grep -E "Manufacturer|Product Name"
          Manufacturer: Nutanix
          Product Name: AHV
  
  # virt-what 
  nutanix_ahv
  redhat
  kvm

@yeagersm, are you able to provide these outputs in your test bed?

My understanding of this bug is that Nutanix make hardware (news to me):

https://www.nutanix.com/products/hardware-platforms/specsheet
https://portal.nutanix.com/page/documents/details/?targetId=System-Specs-G4-Multinode%3ASystem-Specs-G4-Multinode

When virt-what is run on baremetal it sees "Manufacturer: Nutanix" and
thinks this is the Nutanix AHV hypervisor (which it is not).

There are still some things I'm confused over.  Does this Nutanix
hardware run AHV on top and then guests in that?  Does the Nutanix
hardware run anything directly without a hypervisor (containers? partitioned VMs?)

Hi Richard,

> When virt-what is run on baremetal it sees "Manufacturer: Nutanix" and
> thinks this is the Nutanix AHV hypervisor (which it is not).
In my DELL hardware, run "virt-what" in the AHV didn't return any value.


> There are still some things I'm confused over.  Does this Nutanix
> hardware run AHV on top and then guests in that?  
Yes, we can install Nutanix AHV on any qualified hardware include the Nutanix hardware, and then we can install RHEL guest VMs on the AHV.

AHV is a el7 based KVM hypervisor.


> Does the Nutanix hardware run anything directly without a hypervisor (containers? partitioned
> VMs?)
I'm not quiet sure, but the Nutanix hardware is still x86 based servers.

> @yeagersm, are you able to provide these outputs in your test bed?

Yes, the only output seen is:

nutanix_ahv

> When virt-what is run on baremetal it sees "Manufacturer: Nutanix" and thinks this is the Nutanix AHV hypervisor (which it is not).

That is correct.

> Does this Nutanix hardware run AHV on top and then guests in that?

Not necessarily. As Shaoyu mentioned, it is x86 based server hardware. In the case I'm working with, there is no mention of AHV in the DMI data, but there are plenty of references to physical hardware components (SuperMicro mainboard and PSU, Intel ethernet and Xeon CPU). It does seem that these systems ship with some "factory installed software" which might include AHV. Otherwise, they appear to be standard systems that can run any OS on the bare metal.

Fixed upstream in:
http://git.annexia.org/?p=virt-what.git;a=commitdiff;h=eeb7d8a1e7c73fc9c5b4e987d92a04136d61b07d

Note this needs QA ACK from someone before it can be added to RHEL.  If you
(Scott) are able to QA a preview package that we will build then that
could help.

Scott, could you please try the proposed version here and report back
if this fixes the problem on the baremetal Nutanix hardware.  These
RPMs should be installable on either RHEL or CentOS 9:

https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=2305466

Sorry wrong link, it should be:
https://kojihub.stream.centos.org/koji/buildinfo?buildID=33583

Thanks Richard. I'll arrange to test the preview version on the Nutanix hardware and report back with the result.

Scott, were you able to test the new package?  If you have problems downloading it,
or are unable to test it, please let us know.

Hi Richard,

I'm working with the owner of the affected hardware to test the new version, since it's not under my control. Hoping to have that completed in the next day or two. Thanks.

If we can't test it this week I'll move the bug to RHEL 9.4.

Hi Scott,

Is there any progress on the verification?

Hi, I am following up with the hardware owner about completing the test. Will post an update here if they confirm it can be done this week.

The last possible date to test this is 28th Aug, otherwise it'll get moved
to RHEL 9.4.

I moved this to 9.4 since I'm going on holiday for most of the rest of the month.

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.