Hi all, thanks so far for your time and ideas. Please find the gdb output and also the debug-output of libvirt (as requested by Michal Privoznik and Laine Stump) here: https://paste.xinu.at/m-gPSHl/ On 10/19/2016 01:58 AM, Michal Privoznik wrote: > Those "Network is already in use by interface virbr1" error messages > worry me. Is the bridge active before you start libvirtd? If so we might > be losing netowrk state XML (or fail to parse it) and thus think network > is not started and because of autostart we try to start it again (which > fails). > [...] > Before you start libvirt, are there any files under > /var/run/libvirt/network/ ? If so, what's their content? Laine was already correct about that, this error message only appears when I manually try to restart libvirt after it already hung up. Maybe I should've made that more clear. Additionaly, no, there are no files in that directory, also I am pretty sure that I only got one instance of libvirt running According to the GDB log, the libvirt process is endlessly iterating over [1]. Any ideas what could be wrong?

[1] = https://github.com/libvirt/libvirt/blob/master/src/network/bridge_driver.... _______________________________________________ libvirt-users mailing list libvirt-users(a)redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users

On 10/28/2016 05:59 PM, Laine Stump wrote: > Sigh. I am currently hanging my head in shame :-( > > See: > https://www.redhat.com/archives/libvir-list/2016-October/msg01281.html > > My only excuse is that the task was too simple, and I've come to rely > on reviewers too much so I was lazy and inattentive. > > Again, :-( Just to give short feedback: I just applied your patch to the official 2.3.0 release, built it, installed it and yeah: That fixed my problem! It works like a charm now.

Thank you very much :)