On Fri, Sep 08, 2017 at 03:39:56PM +0200, Guido Günther wrote:
> On Sun, Aug 13, 2017 at 10:51:25AM +0200, Marc Haber wrote:
> > found #863266 3.6.0-1
> > thanks
> >
> > On Thu, Aug 03, 2017 at 11:32:37AM -0300, Guido Günther wrote:
> > > Thanks for checking. I'll close the bug for sid then at
Hi Marc,
On Sun, Aug 13, 2017 at 10:51:25AM +0200, Marc Haber wrote:
> found #863266 3.6.0-1
> thanks
>
> On Thu, Aug 03, 2017 at 11:32:37AM -0300, Guido Günther wrote:
> > Thanks for checking. I'll close the bug for sid then at least. I have no
> > idea yet how the kernel enters the game on
found #863266 3.6.0-1
thanks
On Thu, Aug 03, 2017 at 11:32:37AM -0300, Guido Günther wrote:
> Thanks for checking. I'll close the bug for sid then at least. I have no
> idea yet how the kernel enters the game on stretch though.
I still have the issue on current sid. I am, however, also running a
I forgot to update libvirt while testing earlier. Updated libvirt-daemon-system
(libvirt-daemon) from 3.0.0-4 to 3.5.0-1 from Buster and can no longer
reproduce the issue.
--
Bob
This appears to be related to kernel changes? At least on my end.
I have no issues starting multiple VMs while running 4.9.0-3 on Stretch.
However, I get the Spice error on 4.11.0-1, installed from Buster on top of a
mostly-Stretch system.
It works again after downgrading the kernel, and
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
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
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
I'm having the same problem in Debian Stretch.
This might be related to the following bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1397440
https://bugzilla.redhat.com/show_bug.cgi?id=1432684
If you don't need remote connections to my VMs, you can try working
around this issue by using a
On Wed, May 24, 2017 at 05:24:51PM +0200, Marc Haber wrote:
> Package: libvirt-daemon
> Version: 3.0.0-4
> Severity: normal
>
> Dear Maintainer,
>
> somewhere in mid-may, libvirt broke in regard to autoport and SPICE in
> sid. On my systems, I cannot start more than a single VM any more;
>
Package: libvirt-daemon
Version: 3.0.0-4
Severity: normal
Dear Maintainer,
somewhere in mid-may, libvirt broke in regard to autoport and SPICE in
sid. On my systems, I cannot start more than a single VM any more;
libvirt complains that Port 5900 is already in use:
[3/6034]mh@swivel:~ $ virsh
11 matches
Mail list logo
