RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Found when testing the fix for bug 1411105. If the guest OS has 4GB of memory or more and uses buffers above the 4GB boundary for AHCI DMA, the upper 32-bit registers LST_ADDR_HI and FIS_ADDR_HI may contain non-zero values after reboot. Seabios does not correctly reset them back to 0, which manifests as a crash or hang.

Version-Release number of selected component (if applicable):
seabios-1.10.1-1.el7

How reproducible:
10/10 for me

Steps to Reproduce:
1. Start a Windows Server 2008 VM configured per bug 1411105 comment 0. Use qemu-kvm-rhev where bug 1411105 is fixed.
2. Reboot the guest.

Actual results:
The VM hangs or crashes in seabios and the OS does not boot up again.

Expected results:
The guest OS reboots successfully.

Fix included in seabios-1.10.1-2.el7

According to comment0.

Reproduce this bug with seabios-1.10.1-1.el7 & seabios-1.9.1-5.el7 

result:
guest can not reboot successfully.

Verified this bug with seabios-1.10.2-1 & qemu-kvm-rhev-2.8.0-6.el7.x86_64.

result:
Guest reboot sucessfully.

qemu command line:

/usr/libexec/qemu-kvm -drive file=/home/win2008-r2-64-virtio.qcow2,cache=unsafe -M q35 -nodefaults -nodefconfig -vga qxl -device ioh3420,bus=pcie.0,id=root1.0,slot=1 -netdev tap,id=hostnet11,vhost=on,ifname=nw1 -device e1000,netdev=hostnet11,mac=00:54:45:56:12:10,id=poc1,bus=pcie.0 -netdev tap,id=hostnet12,vhost=on,ifname=nw2 -device virtio-net-pci,netdev=hostnet12,mac=00:54:45:56:11:10,bus=root1.0,id=poc2 -m 4G -smp 4,cores=4 -cpu qemu64,+x2apic,+fsgsbase,model=13 -enable-kvm -usbdevice tablet -vnc :1 -monitor stdio

So,set this bug as verified.

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-2017:1855