[Spice-devel] Announcing spice 0.9.1 & spice-protocol 0.9.0
alevy at redhat.com
Fri Sep 2 12:38:14 PDT 2011
On Fri, Sep 02, 2011 at 05:12:21PM +0200, Hans de Goede wrote:
> On 09/02/2011 03:41 PM, John A. Sullivan III wrote:
> >On Fri, 2011-09-02 at 13:49 +0300, Alon Levy wrote:
> >>On Thu, Sep 01, 2011 at 01:30:41PM -0400, John A. Sullivan III wrote:
> >>>On Thu, 2011-09-01 at 11:52 +0300, Alon Levy wrote:
> >>>>On Thu, Sep 01, 2011 at 09:59:14AM +0200, Christophe Fergeau wrote:
> >>>>>On Thu, Aug 25, 2011 at 03:44:58PM +0200, Hans de Goede wrote:
> >>>>>>* Multi-client support, disabled by default (experimental!) set the
> >>>>>> environment variable SPICE_DEBUG_ALLOW_MC before starting qemu to enable
> >>>>>Do we have documentation explaining what multiclient is, and how to use it?
> >>>>>I think there's a page on the wiki, but I'm not 100% sure about this :-/
> >>>>Updated http://spice-space.org/page/Features/MultipleClients
> >>>Thank you for implementing this feature. Are there any plans to add
> >>>multi-user or multi-tenant (trying to find some new label) where each
> >>>connection has their own channels, that is they have their own desktop
> >>>rather than sharing the same desktop? - John
> >>You mean you want to have a single vm with a single spice server, but two clients,
> >>one talking to windows session A and another to windows session B, or in linux
> >>case one talking to X server A and another to X server B?
> >>I'd say that requires quite a lot of changes:
> >> For windows: update driver to work with terminal services? no idea really how to
> >> implement this in windows, but definitely a driver issue. Currently there is just
> >> a single working PDev in windows.
> >> For linux: probably easier. Would have to have different X servers, so actually easier
> >> then having multiple cards for a single X server. But otoh how do you add devices on the
> >> fly? not sure linux would handle this right. Never tried.
> >>So in summary I don't have any plans for this, and it doesn't seem to be too easy either.
> >Yes, that is it exactly. Alas :(
> Don't we have the Linux case covered for like 99% with Xspice? All that is required
> is for the VM and the guests to have some way to do a socket connection between the
> 2 (iow they cannot be on completely isolated networks).
> You don't even need to do it in a VM then.
Well, yeah, we can do that with Xspice, wish I thought of that. But it isn't exactly the
same thing - it means all networking is done from within the guest (so guest has to have
networking implemented for one, and I guess performance can be impacted too). But Xspice
is not feature complete - it does only display+cursor+inputs. So no agent (copy-paste,
guest mouse), no sound, no usb, no smartcard.
And yeah, you wouldn't actually need to run a VM. But I assume you do want some form of
isolation? (I mean more then just running it as the user - that works right now).
> As for the windows case, I agree we don't have a solution for that and won't likely
> have it in the future either. The windows case sounds to me like you just want windows
> terminal server. You likely would need a license for that anyways even if you were to
> use spice as the display protocol, because of how windows licensing works.
> Spice-devel mailing list
> Spice-devel at lists.freedesktop.org
More information about the Spice-devel