libvirt - vnc port selection regression with newer kernels
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Artful |
Won't Fix
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Artful |
Fix Released
|
Undecided
|
Unassigned |
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-
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-
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.
description: | updated |
Changed in linux (Ubuntu Artful): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Released |
Forgot to add libvirt verison:
ii libvirt-bin 1.3.1-1ubuntu10.13 amd64 programs for the libvirt library 5ubuntu10. 14 amd64 QEMU full system emulation binaries (common files)
ii qemu-system-common 1:2.5+dfsg-