On Mon, Jul 03, 2017 at 10:43:22AM +0200, Marc Haber wrote: > On Tue, Jun 27, 2017 at 10:03:55AM +0100, Thomas Pircher wrote: > > This might be related to the following bugs: > > https://bugzilla.redhat.com/show_bug.cgi?id=1397440 > > That one looks like a race condition in port allocation. I don't think > this is the issue here, on my systems, the issue happens even when one > hasn't done anything for minutes. > > > https://bugzilla.redhat.com/show_bug.cgi?id=1432684 > > That one seems more like it, but I cannot currently check the backtrace. > Will do as soon as I get the issue on a less important system. What > bothers me with this bugzilla issue is that the bug seems to be > presentin libvirt 3.0, not in libvirt 3.1, and then again in libvirt > 3.2, judging from comment #3. > > Guido, will we get libvirt 3.1 or 3.2 in unstable soon?
…at debconf latest. Cheers, -- Guido
