Mauricio, Wow! Such an awesome reproducer. Very detailed and easy to follow. Thanks for providing it.
I was able to verify the problem here, and looked at the upstream patch[1] that fixes it. The rationale makes sense to me, although that cleanup function is pretty involved and it's hard to say if there can be any fallout from moving the worker thread pool freeing action earlier. I looked at the upstream repository and could not find any amends/fixes to the commit in question. It's present in Mantic and Noble, which is a good sign. Do you have a PPA build that I can try with the reproducer to check the fix, please? Otherwise, this LGTM and I'm +1 on proceeding with the SRU. Thanks! [1]: For reference: https://gitlab.com/libvirt/libvirt/-/commit/152770333449cd3b78b4f5a9f1148fc1f482d842 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059272 Title: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2059272/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
