Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
The script, XML and such are attached to the bug this was cloned from.
Looking at the debug log, the VM was started in blockdev mode, but the backtrace points to the crash being in 'qemuBlockJobEventProcessLegacy' which is called in non-blockdev mode. The only way I can see that happening is if at the point (due to all of the shutdown shenaningans that happened) something (I presume qemuProcessStop) cleared priv->qemuCaps, in which case we'd end up in the legacy branch despite starting in blockdev mode.
Comment 4Martin Kletzander
2022-02-21 14:37:28 UTC
So, the script calls libvirt APIs from the callback, which is not supported. Even with that I tried reproducing this and with current libvirt the crash does not happen. Other things do, but they are expected when blocking all APIs from a callback. After modifying the script to do the reporting and aborting in another thread all works as expected. There is one case which I am not confident enough to dismiss as expected *yet*, but nevertheless it is unrelated to this bug report).
Please try to reproduce with current libvirt so that we see whether that happened because I have a slower machine or a bug in older version. Please also bear in mind that unless we find something obviously wrong this might still be closed purely because of the API calls from the callback itself.
(In reply to Martin Kletzander from comment #4)
> So, the script calls libvirt APIs from the callback, which is not supported.
Can we throw the unsupported error when calling libvirt APIs from the callback?
> Even with that I tried reproducing this and with current libvirt the crash
> does not happen. Other things do, but they are expected when blocking all
> APIs from a callback. After modifying the script to do the reporting and
> aborting in another thread all works as expected. There is one case which I
> am not confident enough to dismiss as expected *yet*, but nevertheless it is
> unrelated to this bug report).
>
> Please try to reproduce with current libvirt so that we see whether that
> happened because I have a slower machine or a bug in older version. Please
> also bear in mind that unless we find something obviously wrong this might
> still be closed purely because of the API calls from the callback itself.
Now I cannot reproduce it on libvirt-8.0.0-6.el9.x86_64 qemu-kvm-6.2.0-11.el9.x86_64, too
Comment 6Martin Kletzander
2022-03-17 09:57:57 UTC
(In reply to Han Han from comment #5)
I would expect so, thanks for checking that. I would close this BZ in this case, although I'm not sure what the proper resolution should be. Moving to MODIFIED seems weird to me. What do you think Jirka?
Since it cannot be reproduced anymore, I guess CLOSED with CURRENTRELEASE or
WORKSFORME would be appropriate. Or if you can come up with a proper
reproducer, we could turn this into a TestOnly bug.
Comment 8Jaroslav Suchanek
2022-05-10 08:32:52 UTC