+++ This bug was initially created as a clone of Bug #1038963 +++ +++ This bug was initially created as a clone of Bug #1014422 +++ Description of problem: qemu doesn't listen on IPv6 socket for IPv4 and IPv6 VNC connections. Version-Release number of selected component (if applicable): qemu-1.4.2-10.fc19.x86_64 How reproducible: always Steps to Reproduce: 1. Use virt-manager to create and start a guest with VNC display 2. Check the listening VNC socket: sudo netstat -nlp | grep :59 Actual results: >sudo netstat -nlp | grep :59 tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 3233/qemu-system-x8 Expected results: qemu should listen on an IPv6 socket configured to accept both IPv4 and IPv6 connections. >sudo netstat -nlp | grep :59 tcp6 0 0 ::1:5900 :::* LISTEN 3233/qemu-system-x8 Additional info: --- Additional comment from Cole Robinson on 2013-10-31 22:06:30 CET --- Dan, thoughts on if this is intentional or a defect, and if so is it qemu or libvirt? --- Additional comment from Daniel Berrange on 2013-11-01 09:56:23 CET --- It is a bug - we should listen on ::1 by default, with v6-only=0 so that it also covers 127.0.0.1. At minimum it is a libvirt bug. --- Additional comment from Jan Tomko on 2013-11-01 17:21:42 CET --- ::1 with IPV6_V6ONLY=0 does not cover 127.0.0.1, that only works for :: Since QEMU only supports one listen address, we can't tell it to listen on both. Even if we specify a hostname ('localhost') QEMU will only listen on the first address that works (usually ::1 on dual-stack systems) instead of listening on all of them.
*** Bug 895582 has been marked as a duplicate of this bug. ***
FYI, QEMU 2.9 will have ability to listen on multiple addresses. Libvirt XML has ability to specify multiple addresses already, so we should just need to wire up the QEMU command line generator to handle it. The syntax is described in https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg00590.html
This bug was closed deferred as a result of bug triage. Please reopen if you disagree and provide justification why this bug should get enough priority. Most important would be information about impact on customer or layered product. Please indicate requested target release.