Bug 1143907 - Cannot open spice with virt-viewer when addess/listen=0
Summary: Cannot open spice with virt-viewer when addess/listen=0
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glib2
Version: 7.2
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Colin Walters
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-18 08:45 UTC by Yang Yang
Modified: 2020-12-15 07:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:31:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
spice log for virt-viewer (2.72 KB, text/plain)
2014-09-18 08:46 UTC, Yang Yang
no flags Details

Description Yang Yang 2014-09-18 08:45:19 UTC
Description of problem:
Define/start a domain with a spice graphic and set listen/address to 0. Connected to spice graphic by virt-viewer failed since solving address 0 failed.

Version-Release number of selected component (if applicable):
kernel-3.10.0-155.el7.x86_64
libvirt-1.2.8-2.el7.x86_64
glib2-2.40.0-2.el7.x86_64
glib-networking-2.40.0-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Define/start a domain with a spice graphic and set listen/address to 0. 
# virsh dumpxml test1 | grep graphic
<graphics type='spice' port='5900' autoport='yes' listen='0'>
      <listen type='address' address='0'/>
    </graphics>
2.open the spice graphic by virt-viewer
#virt-viewer test1


Actual results:
in step 2: failed to connect to spice graphic
           GSpice-WARNING **:Error resolving '0': Name or service not known

Expected results:
in step 2: should connect to spice graphic without error

Additional info:
After downgrade glib2 and glib-networking to 2.36.3-5.el7, the error disappared.

Comment 1 Yang Yang 2014-09-18 08:46:58 UTC
Created attachment 938797 [details]
spice log for virt-viewer

Comment 4 Vitezslav Humpa 2015-05-11 13:45:54 UTC
This is still happening with glib/glib-networking-2.42.0-2.el7.

Comment 6 RHEL Program Management 2020-12-15 07:31:19 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.