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].
With a local reproducer like [1] I could trigger it 3/3 times overall.
Then I enabled daemon Debug like: "1:file: /tmp/libvirtd. log"
log_outputs=
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/ paste.ubuntu. com/25438591/ paste.ubuntu. com/25438517/ paste.ubuntu. com/25438609/
[2]: http://
[3]: http://
[4]: http://