Description of problem: ----------------------- When running EDK2 build using qemu-kvm-7.0.0-8.el9 or newer, ovmf-vars-generator script ends in loop and never ends. This behavior is probably related to changes related to deprecated cpu handling. Version-Release number of selected component (if applicable): ------------------------------------------------------------- qemu-kvm-7.0.0-8.el9 How reproducible: ----------------- Run EDK2 rpm build. Actual results: --------------- Build is stucked and never finishes. Expected results: ----------------- Build successfully finishes.
> This behavior is probably related to changes related to deprecated cpu handling It shouldn't do - those changes didn't have any functional effect on usage of QEMU beyond printing a message on stderr if a deprecated CPU is used.
(In reply to Daniel Berrangé from comment #1) > > This behavior is probably related to changes related to deprecated cpu handling > > It shouldn't do - those changes didn't have any functional effect on usage > of QEMU beyond printing a message on stderr if a deprecated CPU is used. Having said that 'ovmf-vars-generator' appears to be parsing stdout/stderr, so may in fact be impacted. I'd suggest modifying the script to pass '-cpu max' to see if that helps.
'ovmf-vars-generator' runs qemu as a 'subprocess' and uses 'subprocess.stdout.readline()' to look at the output. If the subprocess quits unexpectedly, it can happen that 'readline()' blocks forever. Often, this is handled like this: while proc.poll() is None: data = proc.stdout.readline() ... I would be good if 'ovmf-vars-generator' would detect if qemu stopps early and also report this via its return code.
QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.
Failed to build edk2-ovmf-20220526git16779ede2d36-2.el9 # rpmbuild -bb edk2.spec ...... ...... +SqIs/vdWGA40O3SFdzET14m2k=' --skip-testing Build/Ovmf3264/DEBUG_GCC5/FV/OVMF_VARS.secboot.fd DEBUG:root:Temp output: /tmp/qosb.03nh_3vy.vars INFO:root:Starting enrollment INFO:root:Performing enrollment Never finishes. Build edk2-ovmf-20220526git16779ede2d36-3.el9 successfully. # rpmbuild -bb edk2.spec ...... ...... Wrote: /root/rpmbuild/RPMS/noarch/edk2-tools-doc-20220526git16779ede2d36-3.el9.noarch.rpm Wrote: /root/rpmbuild/RPMS/x86_64/edk2-tools-20220526git16779ede2d36-3.el9.x86_64.rpm Wrote: /root/rpmbuild/RPMS/noarch/edk2-ovmf-20220526git16779ede2d36-3.el9.noarch.rpm Wrote: /root/rpmbuild/RPMS/x86_64/edk2-tools-debuginfo-20220526git16779ede2d36-3.el9.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/edk2-debugsource-20220526git16779ede2d36-3.el9.x86_64.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.PvXUaE + umask 022 + cd /root/rpmbuild/BUILD + cd edk2-16779ede2d36 + /usr/bin/rm -rf /root/rpmbuild/BUILDROOT/edk2-20220526git16779ede2d36-3.el9.x86_64 + RPM_EC=0 ++ jobs -p + exit 0
According to Comment 15 and Comment 16, 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/RHEA-2022:7971