Bug 1535762
| Summary: | virt-what failed to detect the right hypervisor on RHEV4.2 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Xianghua Chen <xchen> |
| Component: | virt-what | Assignee: | Virtualization Maintenance <virt-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | YongkuiGuo <yoguo> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9.0 | CC: | dougsland, linl, rjones, virt-maint, yoguo |
| Target Milestone: | beta | Keywords: | Reopened, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-10-21 13:49:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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. 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). 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. 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 Yes this is still not fixed in RHEL 8 (or upstream). Moving to RHEL 9. 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. 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: