Public bug reported:
Since yesterdays upgrade to qemu packages version 1:2.5+dfsg-
5ubuntu10.37, new VMs have networking issues. Their network interfaces
stop working after a short time, are not even able to PXE boot but when,
they will LOSE connectivity after a few seconds (longest was around a
I just noticed you released a new version already. Testing 1:2.5+dfsg-
5ubuntu10.38.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829245
Title:
Networking issues after upgrade to
This is a OpenNebula cluster. AFAICS all hosts are effected as soon as
they run with the new versions. Hosts have different hardware but
similar network configuration: 2 bonded NICs and a bridged interface to
be used by VMs.
Network setup on VH host
auto lo
iface lo inet loopback
#eth0 is
> I'm wondering as 1:2.5+dfsg-5ubuntu10.37 never existed in the wild.
> The archive should have went from .36 to .38 I'd think.
@christian: We mirror Ubuntu repositories in a way that keeps versions
in our repo even when they have been removed from the original one. I
guess this means version .37
@dan It works! I cannot reproduce the bug on the patched host (version
1:2.5+dfsg-5ubuntu10.38+bug1829245v20190516b1 from your ppa).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829245
Title:
@dan Ok, will try and report back soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829245
Title:
Networking issues after upgrade to 1:2.5+dfsg-5ubuntu10.37
To manage notifications about this
Version 1:2.5+dfsg-5ubuntu10.38 doesn't fix it entirely but works better
than ...10.37. It seem to lose network connectivity only on reboots of a
VM. Poweroff/resume (killing and restarting the kvm process) fixes it
again.
Still no error messages or something. Willing to provide more
information
