Bug 2083884

Summary: qemu reboot problem with seabios 1.16.0 [rhel.8.7]
Product: Red Hat Enterprise Linux 8 Reporter: Juro Bystricky <juro.bystricky>
Component: seabiosAssignee: Gerd Hoffmann <kraxel>
Status: CLOSED ERRATA QA Contact: Xueqiang Wei <xuwei>
Severity: low Docs Contact:
Priority: low    
Version: CentOS StreamCC: bstinson, chayang, coli, jmaloy, jwboyer, kkiwi, kraxel, lersek, mrezanin, ppolawsk, rjones, virt-maint, xuwei
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: seabios-1.16.0-2.module+el8.7.0+15506+033991b0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-08 09:19:55 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:

Description Juro Bystricky 2022-05-10 22:31:57 UTC
Description of problem:

QEMU fails to reboot with seabios 1.16.0


Version-Release number of selected component (if applicable):
CentOS Stream 8 seabios 1.16.0-1.module_el8.7.0+1140+ff0772f9 

How reproducible:
100%

Steps to Reproduce:
Please see more details here: https://gitlab.com/qemu-project/qemu/-/issues/766 

Actual results:
Reboot is not possible


Expected results:
Reboot possible


Additional info:
There is already a fix for this problem:  https://github.com/coreboot/seabios/commit/01774004c7f7fdc9c1e8f1715f70d3b913f8d491

Comment 6 Laszlo Ersek 2022-05-16 08:55:23 UTC
It's pretty annoying that PAM emulation continues to differ between KVM and TCG.

Comment 10 Klaus Heinrich Kiwi 2022-05-25 15:29:02 UTC
Mirek, can we try to spin this to DTM13 so that we can still try to hit CTC1?

Comment 14 Yanan Fu 2022-06-01 01:12:05 UTC
QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.

Comment 15 Xueqiang Wei 2022-06-01 16:25:12 UTC
Tested with seabios-1.16.0-2.module+el8.7.0+15506+033991b0, not hit this issue.

Versions:
kernel-4.18.0-384.el8.x86_64
qemu-kvm-6.2.0-14.module+el8.7.0+15289+26b4351e
seabios-1.16.0-2.module+el8.7.0+15506+033991b0.x86_64
seabios-bin-1.16.0-2.module+el8.7.0+15506+033991b0.noarch
seavgabios-bin-1.16.0-2.module+el8.7.0+15506+033991b0.noarch


1. boot a guest without enable-kvm
/usr/libexec/qemu-kvm \
     -S  \
     -name 'avocado-vt-vm1'  \
     -sandbox on  \
     -machine q35,memory-backend=mem-machine_mem \
     -device pcie-root-port,id=pcie-root-port-0,multifunction=on,bus=pcie.0,addr=0x1,chassis=1 \
     -device pcie-pci-bridge,id=pcie-pci-bridge-0,addr=0x0,bus=pcie-root-port-0  \
     -nodefaults \
     -device VGA,bus=pcie.0,addr=0x2 \
     -m 12288 \
     -object memory-backend-ram,size=12288M,id=mem-machine_mem  \
     -smp 8,maxcpus=8,cores=4,threads=1,dies=1,sockets=2  \
     -cpu 'Cascadelake-Server-noTSX',+kvm_pv_unhalt \
     -chardev socket,server=on,path=/var/tmp/avocado_d5y2n0ic/monitor-qmpmonitor1-20220526-211317-vXJhHwYe,id=qmp_id_qmpmonitor1,wait=off  \
     -mon chardev=qmp_id_qmpmonitor1,mode=control \
     -chardev socket,server=on,path=/var/tmp/avocado_d5y2n0ic/monitor-catch_monitor-20220526-211317-vXJhHwYe,id=qmp_id_catch_monitor,wait=off  \
     -mon chardev=qmp_id_catch_monitor,mode=control \
     -device pvpanic,ioport=0x505,id=idOBPOcB \
     -chardev socket,server=on,path=/var/tmp/avocado_d5y2n0ic/serial-serial0-20220526-211317-vXJhHwYe,id=chardev_serial0,wait=off \
     -device isa-serial,id=serial0,chardev=chardev_serial0  \
     -chardev socket,id=seabioslog_id_20220526-211317-vXJhHwYe,path=/var/tmp/avocado_d5y2n0ic/seabios-20220526-211317-vXJhHwYe,server=on,wait=off \
     -device isa-debugcon,chardev=seabioslog_id_20220526-211317-vXJhHwYe,iobase=0x402 \
     -device pcie-root-port,id=pcie-root-port-1,port=0x1,addr=0x1.0x1,bus=pcie.0,chassis=2 \
     -device qemu-xhci,id=usb1,bus=pcie-root-port-1,addr=0x0 \
     -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
     -device pcie-root-port,id=pcie-root-port-2,port=0x2,addr=0x1.0x2,bus=pcie.0,chassis=3 \
     -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie-root-port-2,addr=0x0 \
     -blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/home/kvm_autotest_root/images/rhel870-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \
     -blockdev node-name=drive_image1,driver=qcow2,read-only=off,cache.direct=on,cache.no-flush=off,file=file_image1 \
     -device scsi-hd,id=image1,drive=drive_image1,write-cache=on \
     -device pcie-root-port,id=pcie-root-port-3,port=0x3,addr=0x1.0x3,bus=pcie.0,chassis=4 \
     -device virtio-net-pci,mac=9a:4f:30:b4:e3:27,id=idMrOEfm,netdev=id8rEnSa,bus=pcie-root-port-3,addr=0x0  \
     -netdev tap,id=id8rEnSa,vhost=on  \
     -vnc :0  \
     -rtc base=utc,clock=host,driftfix=slew  \
     -boot menu=off,order=cdn,once=c,strict=off \
     -monitor stdio \
     -accel tcg \
     #-enable-kvm \


2. reset the guest

(qemu) system_reset


After step 2, guest reset successfully.

Comment 18 Xueqiang Wei 2022-06-08 19:49:26 UTC
According to Comment 15, set status to VERIFIED.

Comment 22 errata-xmlrpc 2022-11-08 09:19:55 UTC
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 (Low: virt:rhel and virt-devel:rhel security, 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/RHSA-2022:7472