Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1314880

Summary:	When VM has soundcard enabled console connection via "SPICE HTML5 browser client" doesn't work.
Product:	[oVirt] ovirt-engine	Reporter:	Pawel Slotorsz <pawel>
Component:	Console-Integration	Assignee:	Martin Tessun <mtessun>
Status:	CLOSED WONTFIX	QA Contact:	meital avital <mavital>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.6.2.6	CC:	alexis.hauser, bugs, fdelorey, mtessun, pgrunt
Target Milestone:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-03 06:58:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Spice	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pawel Slotorsz 2016-03-04 18:09:57 UTC

Description of problem:

When VM has soundcard enabled console connection via "SPICE HTML5 browser client" doesn't work.

Toggle message output shows:

Connected to wss://my.host.com:6100/.........................
Channel type 6 unknown.
Channel type 0 unknown.
Channel type 189 unknown.
Channel type 180 unknown.
Channel type 23 unknown.
Channel type 75 unknown.
Channel type undefined unknown.
Channel type undefined unknown.

Another behaviour is that VM goes down (Power off) every time when connection is made via SPICE HTML5 browser.

Version-Release number of selected component (if applicable):

oVirt Engine: Version 3.6.2.6-1.el7.centos
Firefox 38.6.1 on RHEL 6.6 x86_64 Intel

spice-glib.x86_64                       0.26-5.el7               @base          
spice-gtk3.x86_64                       0.26-5.el7               @base          
spice-html5.noarch                      0.1.6-1.el7              @ovirt-3.6-epel
spice-server.x86_64                     0.12.4-15.el7            @base          

How reproducible:


Steps to Reproduce:
1. Enable soundcard on VM
2. Run VM
3. Try to connect to VM console via SPICE HTML5 browser

Actual results:

VM goes down.
Connected to wss:// but channel unknown.
Blank screen.

Expected results:

VM remains up.
Connected to wss:// successfully
SPICE console shows login prompt 

Additional info:

If wrong product/component was chosen please moved it to correct one.
Thank you.

Comment 1 ahauser 2016-04-27 14:25:24 UTC

I can confirm this bug, also affected with oVirt Engine Version: 3.6.3.4-1.el7
Tell me if you need additional informations

Test made on Windows 7 guests, not tested on other guests.

Comment 2 ahauser 2016-05-17 08:18:31 UTC

This bug also affect RHEV-3.6.5.3-0.1.el6
Is it possible to add "Red Hat Enterprise Virtualization Manager" to the affected product or I should open a new bug for it ?

Additional info:
Using spice-html5-0.1.4-1

Comment 3 Yaniv Kaul 2017-01-09 09:40:38 UTC

We do not wish to support spice-html5 - it is not feature complete.

Comment 4 Frank DeLorey 2017-05-12 10:28:59 UTC

We have a customer reporting this issue. They are a University and most users are using MACs to access their VMs. They have not had any issues when running RHEV 3.5 however after upgrading to RHEV 3.6.10 they need to disable the soundcard to access the VMs.

Comment 5 Pavel Grunt 2017-05-12 15:23:12 UTC

The vm destroy was fixed in the bug 1281442, spice-0.12.4-17.el7

Also the spice-html5 is apparently getting some bogus data (from websocket proxy probably) - there is no channel type 189 etc. 

I see that spice-html5 0.1.7 (released almost a year ago) contains some audio related fixes.

Comment 7 Martin Tessun 2017-08-03 06:58:58 UTC

Hi all,

as spice-html5 has always been Tech Preview as of now and we don't see any real benefits within ovirt to use it, as it is not better than a VNC connection, and SPICE client is available for all major platforms besides Mac OS X, we will no longer support spice-html5.

Please use VNC instead, if you need to have access to console.

Thanks!
Martin