Bug 1880774
| Summary: | [DOC][POWER] Firmware requirements for running VMs with pseries-rhel8* machine type on RHV 4.4 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Vinícius Ferrão <vinicius> |
| Component: | Documentation | Assignee: | Richard Hoch <rhoch> |
| Status: | CLOSED WONTFIX | QA Contact: | rhev-docs <rhev-docs> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.4.1 | CC: | ahadas, ctomasko, gveitmic, lsurette, mhicks, mkalinin, mtessun, mzamazal, pagranat, pelauter, rhoch, sgoodman, srevivo |
| Target Milestone: | --- | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | ppc64le | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-20 12:15:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1886803 | ||
| Bug Blocks: | |||
|
Description
Vinícius Ferrão
2020-09-19 21:25:06 UTC
Polina, can you please check what we get in our PPC environment? The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again. I can reproduce the problem also on POWER8. When I add <features><ccf-assist state='off'/></features> to the domain XML, the VM starts. Well, it works for me after upgrading the firmware. However, the machine in Comment 0 has an up-to-date firmware. Unless nested (or generally non-hvm) virtualization is used, which is apparently not the case, it should work. So it looks like a platform bug; we may want to check whether it could be something that has been fixed in RHEL/AV 8.3. I'm going to file a QEMU bug. Vinícius, what's the qemu-kvm version on your host? And can you confirm that you run your VMs on bare metal (no nested virtualization)? Hi all. I'm not running nested virtualisation, it's bare metal, and here is anything with qemu on the machine: [root@rhvpower ~]# rpm -qa | grep -i qemu qemu-kvm-common-4.2.0-29.module+el8.2.1+7712+3c3fe332.2.ppc64le qemu-kvm-block-ssh-4.2.0-29.module+el8.2.1+7712+3c3fe332.2.ppc64le qemu-kvm-4.2.0-29.module+el8.2.1+7712+3c3fe332.2.ppc64le ipxe-roms-qemu-20181214-5.git133f4c47.el8.noarch qemu-img-4.2.0-29.module+el8.2.1+7712+3c3fe332.2.ppc64le qemu-kvm-block-iscsi-4.2.0-29.module+el8.2.1+7712+3c3fe332.2.ppc64le libvirt-daemon-driver-qemu-6.0.0-25.2.module+el8.2.1+7722+a9e38cf3.ppc64le qemu-kvm-block-curl-4.2.0-29.module+el8.2.1+7712+3c3fe332.2.ppc64le qemu-kvm-core-4.2.0-29.module+el8.2.1+7712+3c3fe332.2.ppc64le qemu-kvm-block-rbd-4.2.0-29.module+el8.2.1+7712+3c3fe332.2.ppc64le Just for completeness the engine runs on x86_64, and it is self-hosted if this means anything to help out. If there's need for sosreport or something like this please let me know. Thank you for the information, QEMU bug created: https://bugzilla.redhat.com/1886803 Hi Vinícius, could you please check Risk Level setting of your firmware, as described by David in https://bugzilla.redhat.com/show_bug.cgi?id=1886803#c1 ? (You can respond to that comment directly.) Hi Milan, I've answered there already. There's other questions, I'll respond now. For whatever reasons, I'm not receiving messages from Bugzilla anymore. Since it went down a couple days ago. Hi Milan, I've answered there already. There's other questions, I'll respond now. For whatever reasons, I'm not receiving messages from Bugzilla anymore. Since it went down a couple days ago. Hi Vinícius, yes, thank you. I watch both the bugs and receive e-mail notifications from Bugzilla normally, no idea why they don't work for you. As discussed in BZ 1886803, the reported problem disappeared after switching to Risk Level 0 in the firmware. It's probably worth to have it documented some way, so moving this bug to documentation. In summary, to be able to run a VM with pseries-rhel8* emulated machine on POWER 9, the host firmware must be up to date and the firmware risk level (Spectre mitigations etc.) must be set to 0. See BZ 1886803 for details. Didn't get in to 4.4.4, moving to 4.4.5 What exactly is the request for documentation? Hi Steve, please get in touch with David Gibson who should know what would be good to document regarding firmware configuration on POWER to avoid user confusion -- see https://bugzilla.redhat.com/show_bug.cgi?id=1886803#c9 . Closing documentation bug. This content is best suited for a KCS article. What is a KCS article? (In reply to Vinícius Ferrão from comment #20) > What is a KCS article? It was documented here: https://access.redhat.com/solutions/6042541 |