I'd ask the kernel Team to integrate the following changes into our 4.13 kernel release to avoid any sort of update-regressions related to SO_REUSEPORT [1] - Reproducer [2] without libvirt, how to use in [3] - Fixes are submitted as [3] - [6] - If I tracked them correctly they went upstream without [5]+[6] but with [7] instead - Overall the upstream change that I'd ask to pull in as a fix into any 4.13 release is in the merge [8] as part of 4.14-rc2
[1]: https://lwn.net/Articles/542629/ [2]: https://bugzilla.redhat.com/attachment.cgi?id=1314915 [3]: http://www.spinics.net/lists/netdev/msg454647.html [4]: http://www.spinics.net/lists/netdev/msg454769.html [5]: http://www.spinics.net/lists/netdev/msg454786.html [6]: http://www.spinics.net/lists/netdev/msg454933.html [7]: https://github.com/torvalds/linux/commit/fbed24bcc69d3e48c5402c371f19f5c7688871e5 [8]: https://github.com/torvalds/linux/commit/4e683f499a15cd777d3cb51aaebe48d72334c852 ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722702 Title: libvirt - vnc port selection regression with newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1722702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
