From a quick look of the libvirtd and liblib coredump / stacktrace, it looks like the following bug. The fix for which was made very recently (early March).
https://bugzilla.redhat.com/show_bug.cgi?id=1931331#c5 https://bugzilla.redhat.com/show_bug.cgi?id=1942010
Upstream libvirt fix for the above is available here:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=2a490ce5a03 glib: Use safe glib event workaround in other event loops
The above commit will be part of libvirt v7.0 which will be released on 01 April (yes, really).
From a quick look of the libvirtd and liblib coredump / stacktrace, it looks like the following bug. The fix for which was made very recently (early March).
https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1931331# c5 /bugzilla. redhat. com/show_ bug.cgi? id=1942010
https:/
Upstream libvirt fix for the above is available here:
https:/ /libvirt. org/git/ ?p=libvirt. git;a=commit; h=2a490ce5a03
glib: Use safe glib event workaround in other event loops
The above commit will be part of libvirt v7.0 which will be released on 01 April (yes, really).