[GH-ISSUE #542] SPICE Documentation #405

New issue

Closed

opened 2026-02-27 16:39:10 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 16:39:10 +03:00

Owner

Originally created by @catborise on GitHub (Apr 21, 2015).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/542

Hi,
it is specified that with version 4.8.9 spice support was added. Nice upgrade.. thanks
But there is not any configuration example.
when i try to use spice protocol, it says "Unexpected protocol mismatch."

is there any change to work it in supervisord.conf ? or anywhere else...

please help,
thanks

Originally created by @catborise on GitHub (Apr 21, 2015). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/542 Hi, it is specified that with version 4.8.9 spice support was added. Nice upgrade.. thanks But there is not any configuration example. when i try to use spice protocol, it says "Unexpected protocol mismatch." is there any change to work it in supervisord.conf ? or anywhere else... please help, thanks

kerem closed this issue

2026-02-27 16:39:10 +03:00

kerem commented

2026-02-27 16:39:10 +03:00

Author

Owner

@brenard commented on GitHub (Apr 22, 2015):

Hello,

No, you have nothing to configure or to change in supervisord.conf. On the instance page, in Access / Console type, you have to choice spice. The resulting configuration in XML view is something like that :

<graphics type='spice' autoport='yes' listen='0.0.0.0'>
  <listen type='address' address='0.0.0.0'/>
</graphics>

After that, when you open the console page of this instance, webvirtmgr auto-detect that is a SPICE console, and not a VNC console, and display the good one HTML5 client. This client will connect to your instance console throught the websocket of webvirtmgr-console script that will act as a proxy to your instance console SPICE TCP socket.

I mean you have a problem in proxying of webvirtmgr-console script. I recommend to look in supervisord logs, you could see precious details to understand your problem.

@brenard commented on GitHub (Apr 22, 2015): Hello, No, you have nothing to configure or to change in _supervisord.conf_. On the instance page, in _Access / Console type_, you have to choice _spice_. The resulting configuration in XML view is something like that : ``` <graphics type='spice' autoport='yes' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> ``` After that, when you open the console page of this instance, webvirtmgr auto-detect that is a SPICE console, and not a VNC console, and display the good one HTML5 client. This client will connect to your instance console throught the websocket of _webvirtmgr-console_ script that will act as a proxy to your instance console SPICE TCP socket. I mean you have a problem in proxying of _webvirtmgr-console_ script. I recommend to look in supervisord logs, you could see precious details to understand your problem.

kerem commented

2026-02-27 16:39:10 +03:00

Author

Owner

@catborise commented on GitHub (Apr 22, 2015):

thank you very much. the problem is solved.

When i look to the vm config xml file the entry was like below which is default virt-manager vm creation config.
<graphics type='spice' autoport='yes'/>

then i change it like you said it worked flawlessly.

@catborise commented on GitHub (Apr 22, 2015): thank you very much. the problem is solved. When i look to the vm config xml file the entry was like below which is default virt-manager vm creation config. `<graphics type='spice' autoport='yes'/>` then i change it like you said it worked flawlessly.

kerem commented

2026-02-27 16:39:10 +03:00

Author

Owner

@lahdekorpi commented on GitHub (Jun 15, 2015):

Sorry for the stupid question, but is the SPICE port then binded to the public IP and accessible by anyone, anywhere?

@lahdekorpi commented on GitHub (Jun 15, 2015): Sorry for the stupid question, but is the SPICE port then binded to the public IP and accessible by anyone, anywhere?

kerem referenced this issue

2026-02-27 16:40:00 +03:00

[PR #405] [MERGED] Fixes "TypeError: tostring() got an unexpected keyword argument 'method'" #645