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:
These were working dependably on 7.2. After the 7.3 update the VM will start find, shutdown fine, but randomly hang on reboot.

Version-Release number of selected component (if applicable):
libvirt-2.0.0-10.el7.x86_64

How reproducible:
Random, but frequent

Steps to Reproduce:
1. Reboot a VM
2.
3.

Actual results:
VM will randomly hangs during BIOS. It looks like a machine that has an empty boot block, a blinking cursor in the upper left corner.

Expected results:
The VM boots

Additional info:
The kernel doesn't seem to make any difference. We have tried with both the released 7.3 kernel and the 7.2 kernel we had been running.

sbognann has potentially identified seabios-bin as the culprit.

Hi,

could you please provide libvirt debug log and qemu log of the vm? But from the description it does not look like a libvirt issue...

Thanks.

Attached is a log of me replicating the problem with a VM called
examserver-ex300-QA-xxxx-xxxx-xxxx-xxxxxxxxxxx.  While the log was
running, I ran 'init 6' from within the VM and it hung.  I then stopped
it, started it and ran init 6 again and it hung again.  Probably not
shown in the log is that the VM will sometimes hang and sometimes show
in virsh as paused but unresumable:

[root@9610 ~]# virsh list
 Id    Name                           State
----------------------------------------------------
 3     examserver-ex300-QA-xxxx-xxxx-xxxx-xxxxxxxxxxx paused

[root@9610 ~]# virsh resume 3
error: Failed to resume domain 3
error: internal error: unable to execute QEMU command 'cont': Resetting
the Virtual Machine is required

Also, as previously noted, we have found that downgrading seabios-bin
from seabios-bin-1.9.1-5.el7.noarch to seabios-bin-1.7.5-11.el7.noarch
solves the problem.

Thanks,
	Greg

Created attachment 1220678 [details]
Debug of failed reboots

*** This bug has been marked as a duplicate of bug 1394469 ***