[Users] Spice Issue

[Sven Knohsalla]

Hi Oved,

many thanks for the fast response!

Have to say it here:
You guys delivers an incredible support (regarding response time and technical answers),
in comparison with Dell and other distributors!

Keep myself on testing.

Best, Sven.



-----Ursprüngliche Nachricht-----
Von: Oved Ourfalli [mailto:ovedo at redhat.com] 
Gesendet: Mittwoch, 21. November 2012 07:15
An: Itamar Heim
Cc: users at ovirt.org; Sven Knohsalla; spice-devel 
Betreff: Re: [Users] Spice Issue



----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Sven Knohsalla" <s.knohsalla at netbiscuits.com>
> Cc: users at ovirt.org, "Oved Ourfalli" <oourfali at redhat.com>
> Sent: Tuesday, November 20, 2012 11:35:31 PM
> Subject: Re: [Users] Spice Issue
> 
> On 11/20/2012 08:28 PM, Sven Knohsalla wrote:
> > Hi,
> >
> > just in progress to test
> >
> > oVirt Engine Version: 3.1.0-2.fc17
> > +
> >
> > oVirt-node-iso-2.5.5-0.1.fc17
> >
> >    OS Version: oVirt Node - 17 - 1
> >
> >    Kernel Version: 3.6.1 - 1.fc17.x86_64
> >
> >    KVM Version: 1.0.1 - 2.fc17
> >
> >    VDSM Version: 4.10.0.10
> >
> > *_SPICE Version: 0.10.1 - 5.fc17_
> >
> > *Running in some kind of spice issue (using win7 + iexplorer9
> > +Spice
> > ActiveX Plugin 5.0.0.10021)
> > when opening a VM console.
> >
> > Console output of …\ SpiceClient\spicec.exe:
> >
> > Controller: bad channel name “scursor” in secure-channels
> >
> > Spice window doesn’t show anything
> >
> > àThe strange thing is, this client configuration is currently 
> > working with oVirt 3.0 engine?!
> >
> > Does anybody knows this behavior/issue?
> >
> 
> oved, iirc you handled the spice channel configs around this?
> 
Adding spice-devel.
We pass spice the list of secure channels, each one prefixed with "s", denoting a secured channel (no real reason for it... just historical ones I guess).
spice should remove the "s", and use the "cursor" channel in this case.
Looks like it isn't done in this case.
Adding spice-devel, as they should know if it is supposed to work.

Anyway, in the engine side, as a workaround you can use the engine-config utility, and set the SpiceSecureChannels to a list of channels without that one, just to see if it works.
First query the configuration to see the list of current secured channels (in latest ovirt 3.1, we put all channels there by default).