RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
IPv6 address in brackets fails with -vnc

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.3.0-1.el7.x86_64

How reproducible:
128 %

Steps to Reproduce:
1. /usr/libexec/qemu-kvm -vnc [::1]:0

Actual results:
qemu-kvm: -vnc [::1]:0: Failed to start VNC server on `(null)': address resolution failed for [::1]:5900: Name or service not known

Expected results:
qemu starts and listens on IPv6 localhost

Additional info:
Upstream patch (now in the vnc queue):
https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg03462.html

http://patchwork.ozlabs.org/patch/465075/

Commit 274c3b52e10466a4771d591f6298ef61e8354ce0 (2.4.0).

Need that one in 7.2 ...

Oops, already in (via bug 1229073).

*** This bug has been marked as a duplicate of bug 1229073 ***