With a local reproducer like [1] I could trigger it 3/3 times overall. Then I enabled daemon Debug like: log_outputs="1:file:/tmp/libvirtd.log" And it no more occurred in my test environment.
I disabled the logging, and hit it again - maybe my system just isn't beefy enough to hit the race with logging enablerd. Formerly I also tried to go without uvtool (which uses libvirt-python like Openstack) and switched to virsh only (which is C vs libvirt0.so). That [2] did not trigger the bug, but since I now struggle to get [1] to trigger I'm not sure. But even with a non 100% repro rate, this confirmed that is "can" be hit without Openstack. The resulting livbirtd backtrace [3] looks just like the one I saw from the Openstack team [4]. [1]: http://paste.ubuntu.com/25438499/ [2]: http://paste.ubuntu.com/25438591/ [3]: http://paste.ubuntu.com/25438517/ [4]: http://paste.ubuntu.com/25438609/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714254 Title: libvirtd hangs after # instance creation events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1714254/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
