• virt-what-1.25-4.el9
    • None
    • Low
    • rhel-sst-virt-tools
    • ssg_virtualization
    • 5
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • ---
    • None

      Description of problem:

      Detection of nutanix_ahv erroneously includes bare metal systems including Nutanix hardware. This is because the current test only looks for a 'Manufacturer: Nutanix' match in the DMI info.

      For example, a system based on Nutanix NX-T00-4NL3-G5 hardware includes this in the DMI output:

      Manufacturer: Nutanix
      Product Name: NX-T00-4NL3-G5

      This could be resolved by also matching the product name for AHV:

      Manufacturer: Nutanix
      Product Name: AHV

      Version-Release number of selected component (if applicable):

      1.25

            [RHEL-7533] virt-what detects Nutanix hardware as VM

            Yongkui Guo added a comment -

            Closing this bug per rjones's comment.

            Yongkui Guo added a comment - Closing this bug per rjones's comment.

            Richard Jones added a comment - - edited

            This is a TestOnly bug so I think there's nothing for me to do. The fix was included in virt-what 1.25-4.el9 which was already shipping in RHEL 9.3.

            Richard Jones added a comment - - edited This is a TestOnly bug so I think there's nothing for me to do. The fix was included in virt-what 1.25-4.el9 which was already shipping in RHEL 9.3.

            Yongkui Guo added a comment -

            yeagersm@gmail.com Thanks for the verification.

            Yongkui Guo added a comment - yeagersm@gmail.com Thanks for the verification.

            Hi rhn-eng-rjones,

            The owner of the Nutanix hardware was finally able to test the preview version. It works correctly and virt-what exits with code 0 rather than reporting AHV detected.

            Scott Yeager (Inactive) added a comment - Hi rhn-eng-rjones , The owner of the Nutanix hardware was finally able to test the preview version. It works correctly and virt-what exits with code 0 rather than reporting AHV detected.

            Yash Mankad added a comment -

            Moving to In Progress as the BZ that this issue was migrated from was in POST status.

            Yash Mankad added a comment - Moving to In Progress as the BZ that this issue was migrated from was in POST status.

            pm-rhel added a comment -

            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.

            pm-rhel added a comment - 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.

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

            Richard Jones added a comment - I moved this to 9.4 since I'm going on holiday for most of the rest of the month.

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

            Richard Jones added a comment - The last possible date to test this is 28th Aug, otherwise it'll get moved to RHEL 9.4.

            yeagersm@gmail.com added a comment -

            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.

            yeagersm@gmail.com added a comment - 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.

            Yongkui Guo added a comment -

            Hi Scott,

            Is there any progress on the verification?

            Yongkui Guo added a comment - Hi Scott, Is there any progress on the verification?

              virt-maint virt-maint
              jira-bugzilla-migration RH Bugzilla Integration
              Yongkui Guo Yongkui Guo
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: