This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-artful

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1722702

Title:
  libvirt - vnc port selection regression with newer kernels

Status in libvirt package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed
Status in libvirt source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: Bug appears in linux-image-4.11.x kernels on 16.04.3.
  4.8.x and 4.10.x are okay.

  When libvirtd is restarted on Kernel 4.11.0-x-generic or above , it
  loses all information regarding existing port bindings and is unable
  to correctly re-identify vnc ports that currently in use. libvirt
  attempts to bind to an existing port and fails.

  instance-000a6096.log:2017-10-09T01:42:16.017220Z
  qemu-system-x86_64: -vnc 0.0.0.0:0: Failed to start VNC server: Failed to 
listen on socket: Address already in use

  Fairly certain this is the same bug reported, and patched in
  kernel-4.13.4-200.fc26 for Fedora
  https://bugzilla.redhat.com/show_bug.cgi?id=1432684

  Fix: Cherry picking a set of 3 patches (merged as the same set by
  David Miller) from upstream Linux.

  Testcase: Restart of libvirt.

  Risk for Regressions: Looking at the changes those 3 patches
  introduce, the delta is minimal and makes sense with respect to the
  explanations given in the commit message. Overall risk should be low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1722702/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to