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.
Description of problem:
virt-what failed to detect the right hypervisor on RHEV4.2.
Version-Release number of selected component (if applicable):
virt-what-1.18-4.el7.x86_64
rhvh-4.2.0.6-0.20180104.0+1
rhvm-4.2.0.2-0.1.el7
vm: RHEL-7.5-20180116.0-Server-x86_64
How reproducible:
100%
Steps:
1. Prepare a RHEV env with:
rhvh-4.2.0.6-0.20180104.0+1
rhvm-4.2.0.2-0.1.el7
2. Create a RHEL7.5 vm on it using:
RHEL-7.5-20180116.0-Server-x86_64-dvd1.iso
3. Start the vm, and test:
# virt-what
ovirt
rhev
kvm
I see in the /sbin/virt-what, it used dmidecode to detect the hypervisor, so I tried in the vm:
# dmidecode | grep -i manufacturer
Manufacturer: oVirt
Manufacturer: Red Hat
Manufacturer: Red Hat
Manufacturer: Red Hat
# dmidecode | grep -i "Product Name"
Product Name: RHEV Hypervisor
I'm not sure whether rhv team should correct this problem or virt-what can work around that, please help to take a look.
Actual results:
ovirt
rhev
kvm
Expected results:
rhev
kvm
or:
rhv
kvm
Additional info:
Comment 1Richard W.M. Jones
2018-01-18 09:31:48 UTC
Yes this looks like we should tighten up one of those tests.
However moving to RHEL 7.6 since this is mostly cosmetic.
AFAIK, there is no RHEL8 guest image testing on RHEV4.2.
Comment 4Richard W.M. Jones
2019-12-13 08:41:07 UTC
This isn't a customer issue and is a largely cosmetic bug. I think we
should if anything move it to RHEL 8.3 because we're unlikely to fix it
in RHEL 7. There's another RHEL 8.3 / virt-what bug and both could
be looked at at the same time (bug 1782435).
Comment 8RHEL Program Management
2021-01-08 07:26:39 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 9Richard W.M. Jones
2021-01-08 10:55:54 UTC
I apologise for the actions of the "stale" bug process above. This bug
is not stale, and I am reopening it. All bugs are important.
Start up a rhel8.3 vm on RHEVH 4.4 and run virt-what(1.18-6.el8) inside the guest.
# virt-what
kvm
# dmidecode | grep Manufacturer
Manufacturer: Red Hat
Manufacturer: Red Hat
Manufacturer: Red Hat
Manufacturer: Red Hat
Manufacturer: Red Hat
Manufacturer: Red Hat
Manufacturer: Red Hat
Manufacturer: Red Hat
# dmidecode | grep 'Product Name'
Product Name: RHEL
Product Name: RHEL-AV
Comment 12Richard W.M. Jones
2021-06-18 10:43:25 UTC
Yes this is still not fixed in RHEL 8 (or upstream).
Moving to RHEL 9.
Comment 14RHEL Program Management
2022-01-05 07:27:03 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 15Richard W.M. Jones
2022-01-05 10:12:30 UTC
I apologise for the actions of the "stale" bug process above. This bug
is not stale, and I am reopening it. All bugs are important.
Since RHV won't be supported on RHEL9 anyway and this has not been deemed important enough to fix, let's just officially close this as wontfix. Even if this moved to RHEL8/RHEL-AV, it's unlikely to matter that much.
Description of problem: virt-what failed to detect the right hypervisor on RHEV4.2. Version-Release number of selected component (if applicable): virt-what-1.18-4.el7.x86_64 rhvh-4.2.0.6-0.20180104.0+1 rhvm-4.2.0.2-0.1.el7 vm: RHEL-7.5-20180116.0-Server-x86_64 How reproducible: 100% Steps: 1. Prepare a RHEV env with: rhvh-4.2.0.6-0.20180104.0+1 rhvm-4.2.0.2-0.1.el7 2. Create a RHEL7.5 vm on it using: RHEL-7.5-20180116.0-Server-x86_64-dvd1.iso 3. Start the vm, and test: # virt-what ovirt rhev kvm I see in the /sbin/virt-what, it used dmidecode to detect the hypervisor, so I tried in the vm: # dmidecode | grep -i manufacturer Manufacturer: oVirt Manufacturer: Red Hat Manufacturer: Red Hat Manufacturer: Red Hat # dmidecode | grep -i "Product Name" Product Name: RHEV Hypervisor I'm not sure whether rhv team should correct this problem or virt-what can work around that, please help to take a look. Actual results: ovirt rhev kvm Expected results: rhev kvm or: rhv kvm Additional info: