Bug 97575 - Creating more than one spiceport channel makes one of them unusable
Summary: Creating more than one spiceport channel makes one of them unusable
Status: RESOLVED FIXED
Alias: None
Product: Spice
Classification: Unclassified
Component: html5-client (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Pavel Grunt
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-02 13:40 UTC by Oliver Gutierrez
Modified: 2016-09-06 16:14 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
libvirt log (3.96 KB, text/plain)
2016-09-02 13:40 UTC, Oliver Gutierrez
Details
virsh dumpxml of running machine (6.36 KB, text/xml)
2016-09-02 13:40 UTC, Oliver Gutierrez
Details

Description Oliver Gutierrez 2016-09-02 13:40:13 UTC
Created attachment 126173 [details]
libvirt log

When I try to create more than one port, the port devices got created but I can not use them. Only one of the ports is working (in my case, always the last one).
Comment 1 Oliver Gutierrez 2016-09-02 13:40:39 UTC
Created attachment 126174 [details]
virsh dumpxml of running machine
Comment 2 Pavel Grunt 2016-09-02 14:26:52 UTC
Hi Oliver,

I know that you are using spice-html5 -> there is an issue when you have more than one channel of a type - channel id is not set,
see https://cgit.freedesktop.org/spice/spice-html5/tree/spiceconn.js#n122


so spice-html5 is requesting to open the channel twice (because it doesn't set the id), causing:
 spicevmc_connect: channel client 10:0 (0x558c773cf000) already connected, refusing second connection
Comment 3 Pavel Grunt 2016-09-02 14:39:29 UTC
Posted https://patchwork.freedesktop.org/patch/108551/

Oliver, please check, if it changes anything
Comment 4 Oliver Gutierrez 2016-09-05 07:48:14 UTC
Path works marvels. I've tested and now I receive initialization for both channels and both ports in VM are working as expected.

Thank you guys!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.