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 1007936

Summary: Error message fail - GSpice-WARNING **: invalid SPICE_MAGIC!
Product: Red Hat Enterprise Linux 6 Reporter: Bill Sanford <bsanford>
Component: virt-viewerAssignee: Virt Viewer Maint <virt-viewer-maint>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.5CC: acathrow, cfergeau, dblechte, marcandre.lureau, mkrcmari, pvine, vipatel
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-15 01:07:11 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:

Description Bill Sanford 2013-09-13 15:16:50 UTC
Description of problem:
Using virt-viewer and specifying ports 22 or 25 end up with a different error logging message than "GSpice-WARNING **: Connection refused."

[root@kaitain ~]# remote-viewer spice://localhost:22
(remote-viewer:19821): GSpice-WARNING **: invalid SPICE_MAGIC!

Version-Release number of selected component (if applicable):
RHEL6.5-20130911.n.1

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Christophe Fergeau 2013-09-13 16:05:07 UTC
You probably have some daemons listening on port 22 and 25 (ssh and smtp), which would send some data to remote-viewer when it attempts to connect. The client tells you this data does not match what it expects. I'm not exactly sure what you'd expect in this situation? No GSpice-Warning at all? Or something else?

Comment 2 Bill Sanford 2013-09-13 16:20:30 UTC
Every other port replies with "GSpice-WARNING **: Connection refused."

I kind of expect that instead of the "GSpice-WARNING **: invalid SPICE_MAGIC!" where I made reference to in the initial description.

Comment 3 Bill Sanford 2013-09-13 16:22:11 UTC
Oh, BTW, this is on a single RHEL 6.5 instance where the remote-viewer is being launched by the command-line.

Comment 4 Christophe Fergeau 2013-09-16 07:54:05 UTC
(In reply to Bill Sanford from comment #2)
> Every other port replies with "GSpice-WARNING **: Connection refused."
> 
> I kind of expect that instead of the "GSpice-WARNING **: invalid
> SPICE_MAGIC!" where I made reference to in the initial description.

Imo 'invalid SPICE_MAGIC' is more correct than 'connection refused' in this case. We could reword the warning message if you think that's useful, but I don't think it's that important. If you install more services on your box, you'll get this message for more ports.

Comment 5 Marc-Andre Lureau 2013-10-15 01:07:11 UTC
I agree with Christophe, closing for now