Hi, I have seen this issue once but never found a root cause when trying to reproduce. I ended up with one system showing the behavior you mentioned and others not without seeing the difference why.
I thank you a lot to throw in the info that in your case it is the changing kernel version that breaks this - I didn't try to compare those when I looked at it. In my cases I had the issue on multiple versions of libvirt, but it weould be really great if you would have a chance to test newer libvirt stacks e.g. from [1] - that way you can stick to your 16.04.3 set up and switching to your kernels as you had before but bump ther qemu/libvirt versions? I want to avoid starting to work on it - to again end up unreproducible and this cross check would help a lot to start at the right setup. Setting confirmed as I have seen it in the past hoping that this bug and the further tests will help to identify and eventually fix the issues root cause. Since kernel version seems to matter adding a kernel task in case we end up with known issues or a fix there instead of in libvirt. [1]: https://wiki.ubuntu.com/OpenStack/CloudArchive ** Changed in: libvirt (Ubuntu) Status: New => Confirmed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - bind port regression + libvirt - vnc port selection regression with newer kernels -- 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: Confirmed Status in linux package in Ubuntu: New Bug description: 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 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
