Bug 1017860 - Cannot connect to VMs on RHEL5 host
Summary: Cannot connect to VMs on RHEL5 host
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-gtk
Version: 6.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Christophe Fergeau
QA Contact: Desktop QE
: 813889 (view as bug list)
Depends On:
Blocks: 960054 1017862 1017864
TreeView+ depends on / blocked
Reported: 2013-10-10 15:57 UTC by Christophe Fergeau
Modified: 2014-10-14 06:46 UTC (History)
6 users (show)

Cause: Protocol version fallback was broken

Consequence: Could not connect to spice guests on RHEL5 servers

Fix: Fix old protocol fallback.

Result: Can connect to spice guests on RHEL5 servers again.
Clone Of:
: 1017862 1017864 (view as bug list)
Last Closed: 2014-10-14 06:46:28 UTC

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1487 normal SHIPPED_LIVE spice-gtk bug fix and enhancement update 2014-10-14 01:28:31 UTC

Description Christophe Fergeau 2013-10-10 15:57:14 UTC
Trying to connect to a RHEL5 VM causes a warning in the console '(remote-viewer:9644): GSpice-WARNING **: major mismatch (got 1, expected 2)' and an error message that it couldn't connect to the remote VM.
Tested with spice-gtk.x86_64 0:0.20-9.el6

This is fixed by http://lists.freedesktop.org/archives/spice-devel/2013-October/014897.html, scratch build with these 2 patches available from http://brewweb.devel.redhat.com/brew/taskinfo?taskID=6398063

Comment 1 Marc-Andre Lureau 2014-02-19 19:34:03 UTC
*** Bug 813889 has been marked as a duplicate of this bug. ***

Comment 2 David Jaša 2014-02-20 12:51:28 UTC
We have access to one VM running on RHEV2.2/RHEL5.y host --> qa_ack+

FWIW, connection works fine with F20 client (spice-gtk-0.23-1.fc20.x86_64) so the fix should work fine in RHEL6/7 as well once it makes its way to the builds...

Comment 5 errata-xmlrpc 2014-10-14 06:46:28 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.


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