On Wed, May 24, 2017 at 07:24:50PM +0200, Guido Günther wrote: > On Wed, May 24, 2017 at 05:24:51PM +0200, Marc Haber wrote: > > I doubt that this issue is actually caused by libvirt itself. The last > > libvirt update was back in March, and I upgrade my sid about twice a > > month, and the breakage is fairly recent. I do create my domains with > > virt-manager's help, but virt-manager also hasn't been updated recently. > > I'm not seeing this problem here but I'm lagging on some sid > updates (though I'm running libvirt 3.0.0-4). Once I have updated I can > try to reproduce but it's unlikely s.th. outside of libvirt.
The issue also happens in stretch :-( so 3.0.0-4 is affected. > Can you check in the domain log that qemu gets broken command line > already (one with colliding ports). Check for -spice port= in > > /var/log/libvirt/qemu/<domain>.log Yes, the qemu process gets called with -spice port=5900. > If so you can try to increase debuggig esp. for qemuProcess and > qemuProcessSPICEAllocatePorts. See log_filters in > /etc/libvirt/libvirtd.log. I guess you mean libvirtd.conf. Do you mean setting something like log_filters="1:qemuProcess 1:qemuProcessSPICEAllocatePorts"? 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
