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
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