Description of problem: Upstream qemu 4.2 uses seabios 1.13. Well, to be exact, it uses a git snapshot one commit away from 1.13-final because the actual release was a bit late for 4.2. Lets rebase downstream too.
(In reply to Gerd Hoffmann from comment #0) > Description of problem: > > Upstream qemu 4.2 uses seabios 1.13. Well, to be exact, it uses a git > snapshot one commit away from 1.13-final because the actual release was a > bit late for 4.2. > > Lets rebase downstream too. If we do so, we should probably move to seabios 1.13 GA.
> If we do so, we should probably move to seabios 1.13 GA. Sure. That one commit from snapshot to final is just updating the version number, no actual code changes.
Run the RHEL test plan for seabios as usual after rebases. Do sanity checking on qemu-kvm-4.2.0-7.module+el8.2.0+5520+4e5817f3 with seabios 1.13. Not hit any issue, the core functions work as expected. So set status to VERIFIED. Host: kernel-4.18.0-175.el8.x86_64 qemu-kvm-4.2.0-7.module+el8.2.0+5520+4e5817f3 seabios-1.13.0-1.module+el8.2.0+5520+4e5817f3.x86_64 seabios-bin-1.13.0-1.module+el8.2.0+5520+4e5817f3.noarch Guest: rhel820 and windows10 Job link: http://10.66.86.2/kvm_autotest_job_log/?jobid=4052686
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, 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-2020:2017