QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.
Tested with edk2-ovmf-20220126gitbb1bba3d77-3.el9_0.1.noarch, both /usr/share/qemu/firmware/50-edk2-ovmf-amdsev.json and /usr/share/qemu/firmware/50-edk2-ovmf-cc.json are updated: [...] "targets": [ { "architecture": "x86_64", "machines": [ "pc-q35-rhel8.5.0", "pc-q35-rhel8.6.0", "pc-q35-rhel9.*" ] } ], [...] The updates are as expected.
Test with edk2-ovmf-20220126gitbb1bba3d77-3.el9_0.1.noarch, sev/sev-es test passed. version: edk2-ovmf-20220126gitbb1bba3d77-3.el9_0.1.noarch kernel-5.14.0-70.17.1.el9_0.x86_64 qemu-kvm-6.2.0-11.el9_0.3.x86_64 Steps: Boot a sev and a sev-es guest, check guests sev/sev-es enabled https://beaker.engineering.redhat.com/recipes/12374241#tasks
According to Comment 4 and Comment 5, set status to VERIFIED. Thanks.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (edk2 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:5965