On Fri, May 04, 2018 at 03:18:39PM +0700, unsigned_nerd wrote: > Package: libvirt-daemon > Version: 1.2.9-9+deb8u5 > Followup-For: Bug #897634 > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > > I run multiple VMs. I upgraded software on my Debian 8.10 which > included the kernel (3.16.0-6-amd64) on May 3, 2018 GMT+7. After > the reboot, I could run only 1 VM at a time. Note that if I remove > the network interface from the second VM, then I can still run the > send instance but that is not a workaround as I need network access > for my VMs. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > I googled hard and the most relevance issue I found is: > https://bugzilla.redhat.com/show_bug.cgi?id=1506822 . That's when I > decide to upgrade my system from Debian 8 to Debian 9 so that I could > get the newer version of libvirt-daemon. After that, the problem is > gone. I can run multiple VMs once again. > > * What was the outcome of this action? > > The problem is gone. > > * What outcome did you expect instead? > > That's what I expected.
[NB: I'm not running Jessie currently] Since this is triggered by a kernel upgrade could you guys take that up with the kernel maintainers please? It's a regression caused by the kernel update after all. There's also a newer version in Jessie backports (but the bug should be fixed in Jessie nevertheless). Cheers, -- Guido
