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.

Created attachment 915882 [details]
Comment

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).

Unfortunately the logs are pretty useless at figuring out what's wrong. I don't see anything suspect in this log. I don't suppose that abrt recorded a core dump somewhere ?  Unless there's a way to reproduce, an abrt coredump is our only hope

Yeh as discussed on pkrempa/jdenemar on irc earlier, abrt wasn't started unfortunately.

Just prior to this my qemu seg'd and that was logged in dmesg but the seg of libvirt wasn't.

and yes, I'm sympathetic it's probably hard to get anything useful out of it, just thought I'd better report it anyway.

Dave

Since we don't have the core dump or backtrace and reproducer is unknown, I'm afraid I have to close this bug as there's nothing we can do about it (although we'd love to). Please, keep abrt running and reopen this bug or file a new one in case you see it again.