Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1241860

Summary: Fail to launch spice guest console via virt-viewer or virt-manager
Product: Red Hat Enterprise Linux 7 Reporter: tingting zheng <tzheng>
Component: spiceAssignee: Christophe Fergeau <cfergeau>
Status: CLOSED ERRATA QA Contact: SPICE QE bug list <spice-qe-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.2CC: astepano, cfergeau, dblechte, djasa, fidencio, juzhou, mzhan, tpelka, xiaodwan
Target Milestone: rcKeywords: Regression
Target Release: 7.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
No docs needed (regression introduced in very first 7.2 development build, and fixed long before beta)
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 14:35:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Debug info from virt-viewer
none
Fix 0040-Don-t-set-SpiceLinkReply-pub_key-if-client-advertise.patch none

Description tingting zheng 2015-07-10 09:14:45 UTC 
Created attachment 1050633 [details]
Debug info from virt-viewer

Description:
Fail to launch spice guest console via virt-viewer or virt-manager

Version:
virt-manager-1.2.1-2.el7.noarch
virt-viewer-2.0-4.el7.x86_64
spice-gtk-python-0.26-4.el7.x86_64
spice-gtk-0.26-4.el7.x86_64
spice-vdagent-0.14.0-10.el7.x86_64
spice-gtk3-0.26-4.el7.x86_64
spice-glib-0.26-4.el7.x86_64
spice-server-0.12.4-11.el7.x86_64
spice-protocol-0.12.6-2.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1.Launch virt-manager,new a guest or start an existing guest with spice graphics.
# virsh dumpxml $guest
    <channel type='spicevmc'>
      <target type='virtio' name='com.redhat.spice.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='spice' port='5900' autoport='yes' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
      <image compression='off'/>
    </graphics>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>

2.From virt-manager,you will see the error as:Error:viewer connection to hypervisor host got refused or disconnected!
Debug info from virt-manager:
[Fri, 10 Jul 2015 15:52:54 virt-manager 5391] DEBUG (engine:357) window counter incremented to 2
[Fri, 10 Jul 2015 15:52:54 virt-manager 5391] DEBUG (console:650) Starting connect process for proto=spice trans= connhost=127.0.0.1 connuser= connport= gaddr=127.0.0.1 gport=5900 gtlsport=None gsocket=None

(virt-manager:5391): GSpice-WARNING **: incomplete link header (0/16)

(virt-manager:5391): GSpice-WARNING **: major mismatch (got 2, expected 1)
[Fri, 10 Jul 2015 15:52:54 virt-manager 5391] DEBUG (viewers:538) Spice channel event error: <enum SPICE_CHANNEL_ERROR_LINK of type SpiceChannelEvent>
[Fri, 10 Jul 2015 15:52:54 virt-manager 5391] DEBUG (console:749) Viewer disconnected

3.Launch guest from virt-viewer:
# virt-viewer $ guest
Error shows as below:
Unable to connect to the graphic server 127.0.0.1:5900

Actual results：
As description.

Expected results:
Spice guest can be launched from virt-manager or virt-viewer.

Additional info:
1.When I download spice pkg to spice-server-0.12.4-9.el7.x86_64,can not reproduce this issue.
2.Can not reproduce this bug with vnc guest.
3.Attached spice debug info from virt-viewer.
Comment 4 Christophe Fergeau 2015-07-10 13:00:16 UTC 
The patch to fix bug #1071176 seems to have had an issue during the backport (ie the regression occurred between spice-server-0.12.4-9.el7.x86_64 and spice-server-0.12.4-10.el7.x86_64 )
Comment 5 Christophe Fergeau 2015-07-10 13:17:40 UTC 
Created attachment 1050678 [details]
Fix 0040-Don-t-set-SpiceLinkReply-pub_key-if-client-advertise.patch

This patch (scratch build at https://brewweb.devel.redhat.com/taskinfo?taskID=9500151 ) fixes the issue (caused by typos in the backport of 0040-Don-t-set-SpiceLinkReply-pub_key-if-client-advertise.patch)
Comment 7 Andrei Stepanov 2015-07-10 14:23:42 UTC 
As I understand:
QE test should consist in general connection to SpiceServer, without specific setup.
The bug is in spice-server.
Give qa_ack +
Comment 11 errata-xmlrpc 2015-11-19 14:35:16 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-2429.html