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.
Bug 1229073 - [graphical framebuffer]Start guest failed when VNC listen on IPV6 address
Summary: [graphical framebuffer]Start guest failed when VNC listen on IPV6 address
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.2
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Gerd Hoffmann
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 1216984 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-08 01:58 UTC by vivian zhang
Modified: 2015-12-04 16:44 UTC (History)
14 users (show)

Fixed In Version: qemu-kvm-rhev-2.3.0-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-04 16:44:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2546 0 normal SHIPPED_LIVE qemu-kvm-rhev bug fix and enhancement update 2015-12-04 21:11:56 UTC

Description vivian zhang 2015-06-08 01:58:04 UTC 
Description:
When VNC listen on IPV6 address, guest start up failed with qemu-kvm-rhev-2.3.0-1.el7.x86_64

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


How reproducible:
100%

Steps:
1. edit guest with below XML
# virsh edit rh7
...
<graphics type='vnc' port='-1' autoport='yes' listen='::1'>
      <listen type='address' address='::1'/>
    </graphics>
...

2. start guest failed with error

# virsh start rh7
error: Failed to start domain rh7
error: internal error: early end of file from monitor: possible problem:
2015-06-08T01:49:54.905220Z qemu-kvm: -vnc [::1]:0: Failed to start VNC server on `(null)': address resolution failed for [::1]:5900: Name or service not known


3. configure guest with VNC listen on ipv6 network, still failed

# virsh edit rh7
...
<graphics type='vnc' port='-1' autoport='yes'>
      <listen type='network' network='ipv6'/>
    </graphics>
...

# virsh start rh7
error: Failed to start domain rh7
error: internal error: early end of file from monitor: possible problem:
2015-06-08T01:51:35.437876Z qemu-kvm: -vnc [2001:b8:ca2:2::1]:0: Failed to start VNC server on `(null)': address resolution failed for [2001:b8:ca2:2::1]:5900: Name or service not known

# virsh net-dumpxml ipv6
<network>
  <name>ipv6</name>
  <uuid>7ba66277-91b2-45b0-810b-f3620b924790</uuid>
  <forward mode='nat'/>
  <bridge name='virbr6' stp='on' delay='0'/>
  <mac address='52:54:00:46:07:af'/>
  <ip family='ipv6' address='2001:b8:ca2:2::1' prefix='64'>
    <dhcp>
      <range start='2001:b8:ca2:2:1::10' end='2001:b8:ca2:2:1::ff'/>
    </dhcp>
  </ip>
</network>

4.on qemu-kvm-rhev-2.2.0-9.el7.x86_64,  guest start success . check qemu CML. VNC bound to [::1] success

# ps aux |grep rh7
qemu     10014 21.7  4.0 3769480 326780 ?      Sl   09:47   0:23 /usr/libexec/qemu-kvm -name rh7 -S -machine pc-i440fx-rhel7.1.0,accel=kvm,usb=off -cpu Penryn -m 1024 -realtime mlock=off ... -vnc [::1]:0 ...


Excepted results:

Guest should start success when VNC listen on IPV6 address 


Actual results:

Guest start failed when VNC listen on IPV6 address on qemu-kvm-rhev-2.3.0-1.el7.x86_64
Comment 2 Gerd Hoffmann 2015-06-12 10:58:17 UTC 
probably fixed by upstream commit 274c3b52e10466a4771d591f6298ef61e8354ce0
Comment 6 Gerd Hoffmann 2015-06-15 10:57:38 UTC 
Patch posted.
Comment 7 Miroslav Rezanina 2015-06-19 11:09:26 UTC 
Fix included in qemu-kvm-rhev-2.3.0-3.el7
Comment 8 Gerd Hoffmann 2015-06-23 06:07:51 UTC 
*** Bug 1233053 has been marked as a duplicate of this bug. ***
Comment 9 mazhang 2015-06-30 08:15:06 UTC 
Reproduce this bug on qemu-kvm-rhev-2.3.0-2.el7.

Steps:
# /usr/libexec/qemu-kvm -vnc [::]:1 -monitor stdio
QEMU 2.3.0 monitor - type 'help' for more information
(qemu) qemu-kvm: -vnc [::]:1: Failed to start VNC server on `(null)': address resolution failed for [::]:5901: Name or service not known


Verify this bug on qemu-kvm-rhev-10:2.3.0-6.el7.

Result:
# /usr/libexec/qemu-kvm -vnc [::]:1 -monitor stdio
QEMU 2.3.0 monitor - type 'help' for more information
(qemu) info status
VM status: running

So this bug has been fixed.
Comment 11 Gerd Hoffmann 2015-08-31 08:49:25 UTC 
*** Bug 1216984 has been marked as a duplicate of this bug. ***
Comment 13 errata-xmlrpc 2015-12-04 16:44:51 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2546.html
Note You need to log in before you can comment on or make changes to this bug.