[Users] concurrent SPICE access [was: Re: oVirt 3.5 planning]

[Markus Stockhausen]

> Von: users-bounces at ovirt.org [users-bounces at ovirt.org]" im Auftrag von "Itamar Heim [iheim at redhat.com]
> Gesendet: Donnerstag, 27. Februar 2014 09:53
> An: Sven Kieske; users at ovirt.org
> Betreff: Re: [Users] concurrent SPICE access [was: Re:  oVirt 3.5 planning]
> 
> On 02/27/2014 10:52 AM, Itamar Heim wrote:
> > On 02/27/2014 10:51 AM, Sven Kieske wrote:
> >> Well, you generate a separate ticket to the same vm.
> >> resulting in another vnc-session to the server, but the input/output
> >> is shared, you can see in real time when the other user types etc.
> >
> > iirc, the ticketing mechanism works in a way that a new ticket
> > disconnects the previous session?
> 
> (on connection with the new ticket)

In the VNC case this does not work. I do not know if its by design or
just a bug/feature. Either Ovirt does not instruct libvirt to create a new
VNC ticket with option "disconnect all connected clients" or this 
information is not correctly interpreted by qemu.

If you launch a client that initiates a shared connection to the console 
then existing connections will stay open. This magically works if you
use the novnc client (as Sven explained).

The only thing that prevents a concurrent access to the console with
virt-viewer is the fact that it enforces a single VNC connection.

So state is as follows:

SPICE: disconnect happens during ticket creation
VNC: disconnect may happen during client connection

You can check that behaviour if you associate a .VV file with a text editor. 
With SPICE the existing console connection is terminated just before the
.VV file opens in the editor. With VNC the existing session stays open.

Markus
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140227/7042c6f1/attachment-0001.txt>