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? > If you don't need remote connections to my VMs, you can try working around > this issue by using a local socket rather than a port: > > <graphics type='spice'> > <listen type='socket'/> > <image compression='auto_glz'/> > </graphics> I have worked around the issue by setting autoport=no and assigning a fixed port in the XML. Thankfully all my boxes have a dedicated, static machine number so I was able to use this one to avoid collisions. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
