Discussion:
[Spice-devel] Spice just for a remote desktop to a virtual machine?
Marc Dunivan
2018-01-26 22:11:08 UTC
Permalink
Is SPICE for the use case of providing a remote virtual desktop only to a virtual machine’s graphical/desktop environment? Additionally, the virtual machine host must be a Linux OS, correct...SPICE server only runs on Linux?

SPICE can’t be used to obtain a remote desktop from a Fedora GNOME PC to a Windows 10 PC, or visa versa?
Uri Lublin
2018-01-29 09:33:13 UTC
Permalink
Post by Marc Dunivan
Is SPICE for the use case of providing a remote virtual desktop only to a virtual machine’s graphical/desktop environment?
Hi,

There are 2 projects that allow remoting a "non-virtual" desktop:
Xspice and x11spice
Post by Marc Dunivan
Additionally, the virtual machine host must be a Linux OS, correct...SPICE server only runs on Linux?
Currently, AFAIK, there is only a Linux implementation.
Theoretically, there can be implementations for other operating systems.
Post by Marc Dunivan
SPICE can’t be used to obtain a remote desktop from a Fedora GNOME PC to a Windows 10 PC, or visa versa?
One can, for example, install x11spice on a Fedora Gnome PC and access
it from a Windows 10 PC running remote-viewer.

Uri.
Christophe de Dinechin
2018-01-29 10:09:27 UTC
Permalink
Post by Marc Dunivan
Is SPICE for the use case of providing a remote virtual desktop only to a virtual machine’s graphical/desktop environment? Additionally, the virtual machine host must be a Linux OS, correct...SPICE server only runs on Linux?
SPICE can’t be used to obtain a remote desktop from a Fedora GNOME PC to a Windows 10 PC, or visa versa?
At the moment, that’s correct. But a question asked at DevConf reminded me
that with the shift to Wayland, SPICE may have an opportunity to provide
a better Wayland remote desktop experience. Any volunteer for that?

By the way, if that happens, we might want to consider this a fourth possible
location for the spice streaming agent and attached plugins, the first three
being the current “in-guest”, the proposed “in spice server”, and Marc André’s
suggestion to put that in host outside of QEMU process.
Post by Marc Dunivan
_______________________________________________
Spice-devel mailing list
https://lists.freedesktop.org/mailman/listinfo/spice-devel
Christophe de Dinechin
2018-01-29 10:10:58 UTC
Permalink
Post by Christophe de Dinechin
Post by Marc Dunivan
Is SPICE for the use case of providing a remote virtual desktop only to a virtual machine’s graphical/desktop environment? Additionally, the virtual machine host must be a Linux OS, correct...SPICE server only runs on Linux?
SPICE can’t be used to obtain a remote desktop from a Fedora GNOME PC to a Windows 10 PC, or visa versa?
At the moment, that’s correct. But a question asked at DevConf reminded me
that with the shift to Wayland, SPICE may have an opportunity to provide
a better Wayland remote desktop experience. Any volunteer for that?
By the way, if that happens, we might want to consider this a fourth possible
location for the spice streaming agent and attached plugins, the first three
being the current “in-guest”, the proposed “in spice server”, and Marc André’s
suggestion to put that in host outside of QEMU process.
Also relevant to this discussion: work to use pipewire for remoting wayland:
https://www.ctrl.blog/entry/wayland-gnome-remote-desktop
Post by Christophe de Dinechin
Post by Marc Dunivan
_______________________________________________
Spice-devel mailing list
https://lists.freedesktop.org/mailman/listinfo/spice-devel
Snir Sheriber
2018-01-29 11:01:13 UTC
Permalink
Post by Christophe de Dinechin
Post by Christophe de Dinechin
Post by Marc Dunivan
Is SPICE for the use case of providing a remote virtual desktop only to a virtual machine’s graphical/desktop environment? Additionally, the virtual machine host must be a Linux OS, correct...SPICE server only runs on Linux?
SPICE can’t be used to obtain a remote desktop from a Fedora GNOME PC to a Windows 10 PC, or visa versa?
At the moment, that’s correct. But a question asked at DevConf reminded me
that with the shift to Wayland, SPICE may have an opportunity to provide
a better Wayland remote desktop experience. Any volunteer for that?
By the way, if that happens, we might want to consider this a fourth possible
location for the spice streaming agent and attached plugins, the first three
being the current “in-guest”, the proposed “in spice server”, and Marc André’s
suggestion to put that in host outside of QEMU process.
https://www.ctrl.blog/entry/wayland-gnome-remote-desktop
Cool!

That reminds me there is also an experimental spice backend for Weston
(Wayland compositor). iirc it worked nice but still needed some more love.
(maybe it worth a link on spice-spice.org? ;) )

https://github.com/ein-shved/compositor-spice
Post by Christophe de Dinechin
Post by Christophe de Dinechin
Post by Marc Dunivan
_______________________________________________
Spice-devel mailing list
https://lists.freedesktop.org/mailman/listinfo/spice-devel
_______________________________________________
Spice-devel mailing list
https://lists.freedesktop.org/mailman/listinfo/spice-devel
Christophe de Dinechin
2018-01-29 12:48:17 UTC
Permalink
Post by Christophe de Dinechin
Post by Christophe de Dinechin
Post by Marc Dunivan
Is SPICE for the use case of providing a remote virtual desktop only to a virtual machine’s graphical/desktop environment? Additionally, the virtual machine host must be a Linux OS, correct...SPICE server only runs on Linux?
SPICE can’t be used to obtain a remote desktop from a Fedora GNOME PC to a Windows 10 PC, or visa versa?
At the moment, that’s correct. But a question asked at DevConf reminded me
that with the shift to Wayland, SPICE may have an opportunity to provide
a better Wayland remote desktop experience. Any volunteer for that?
By the way, if that happens, we might want to consider this a fourth possible
location for the spice streaming agent and attached plugins, the first three
being the current “in-guest”, the proposed “in spice server”, and Marc André’s
suggestion to put that in host outside of QEMU process.
https://www.ctrl.blog/entry/wayland-gnome-remote-desktop
Cool!
That reminds me there is also an experimental spice backend for Weston (Wayland compositor). iirc it worked nice but still needed some more love.
(maybe it worth a link on spice-spice.org? ;) )
https://github.com/ein-shved/compositor-spice
Yes. Also worth adding to the SPICE top-level project I started working on. Will do.

I’m a bit fuzzy, was there any decision regarding spice-space.org?
I’d like to be able to update things like the mac build instructions
or, when it’s in, instructions on how to use the flight recorder data
to tune performance.


Christophe
Post by Christophe de Dinechin
Post by Christophe de Dinechin
Post by Marc Dunivan
_______________________________________________
Spice-devel mailing list
https://lists.freedesktop.org/mailman/listinfo/spice-devel
_______________________________________________
Spice-devel mailing list
https://lists.freedesktop.org/mailman/listinfo/spice-devel
_______________________________________________
Spice-devel mailing list
https://lists.freedesktop.org/mailman/listinfo/spice-devel
Victor Toso
2018-01-29 13:17:03 UTC
Permalink
Hi,
Post by Christophe de Dinechin
Post by Snir Sheriber
Post by Christophe de Dinechin
Post by Marc Dunivan
Is SPICE for the use case of providing a remote virtual
desktop only to a virtual machine’s graphical/desktop
environment? Additionally, the virtual machine host must
be a Linux OS, correct...SPICE server only runs on Linux?
SPICE can’t be used to obtain a remote desktop from a
Fedora GNOME PC to a Windows 10 PC, or visa versa?
At the moment, that’s correct. But a question asked at
DevConf reminded me that with the shift to Wayland, SPICE
may have an opportunity to provide a better Wayland remote
desktop experience. Any volunteer for that?
By the way, if that happens, we might want to consider this
a fourth possible location for the spice streaming agent
and attached plugins, the first three being the current
“in-guest”, the proposed “in spice server”, and Marc
André’s suggestion to put that in host outside of QEMU
process.
Also relevant to this discussion: work to use pipewire for
https://www.ctrl.blog/entry/wayland-gnome-remote-desktop
Cool!
That reminds me there is also an experimental spice backend
for Weston (Wayland compositor). iirc it worked nice but
still needed some more love. (maybe it worth a link on
spice-spice.org? ;) )
https://github.com/ein-shved/compositor-spice
Yes. Also worth adding to the SPICE top-level project I started working on. Will do.
I’m a bit fuzzy, was there any decision regarding
spice-space.org?
Decision about what?
Post by Christophe de Dinechin
I’d like to be able to update things like the mac build
instructions or, when it’s in, instructions on how to use the
flight recorder data to tune performance.
AFAIR, you can submit changes to spice-space-pages [0] and some
VM is going to regenerate the spice-space.org page.

[0] https://gitlab.com/spice/spice-space-pages

We use Pelican [1] and if you want to generate the website in
your end, you can with spice-space repo [2]

[1] http://docs.getpelican.com/en/stable/
[2] https://gitlab.com/spice/spice-space

Cheers,
toso
Christophe de Dinechin
2018-01-29 13:56:19 UTC
Permalink
Post by Victor Toso
Hi,
Post by Christophe de Dinechin
Post by Snir Sheriber
Post by Christophe de Dinechin
Post by Christophe de Dinechin
Post by Marc Dunivan
Is SPICE for the use case of providing a remote virtual
desktop only to a virtual machine’s graphical/desktop
environment? Additionally, the virtual machine host must
be a Linux OS, correct...SPICE server only runs on Linux?
SPICE can’t be used to obtain a remote desktop from a
Fedora GNOME PC to a Windows 10 PC, or visa versa?
At the moment, that’s correct. But a question asked at
DevConf reminded me that with the shift to Wayland, SPICE
may have an opportunity to provide a better Wayland remote
desktop experience. Any volunteer for that?
By the way, if that happens, we might want to consider this
a fourth possible location for the spice streaming agent
and attached plugins, the first three being the current
“in-guest”, the proposed “in spice server”, and Marc
André’s suggestion to put that in host outside of QEMU
process.
Also relevant to this discussion: work to use pipewire for
https://www.ctrl.blog/entry/wayland-gnome-remote-desktop
Cool!
That reminds me there is also an experimental spice backend
for Weston (Wayland compositor). iirc it worked nice but
still needed some more love. (maybe it worth a link on
spice-spice.org? ;) )
https://github.com/ein-shved/compositor-spice
Yes. Also worth adding to the SPICE top-level project I started working on. Will do.
I’m a bit fuzzy, was there any decision regarding
spice-space.org?
Decision about what?
Weren’t we discussing about where it’s hosted just yesterday in Brno?
Or is that now completely solved and stable? I was under the impression
that we were still looking for the optimal hosting solution.

Thanks
Christophe
Post by Victor Toso
Post by Christophe de Dinechin
I’d like to be able to update things like the mac build
instructions or, when it’s in, instructions on how to use the
flight recorder data to tune performance.
AFAIR, you can submit changes to spice-space-pages [0] and some
VM is going to regenerate the spice-space.org page.
[0] https://gitlab.com/spice/spice-space-pages
We use Pelican [1] and if you want to generate the website in
your end, you can with spice-space repo [2]
[1] http://docs.getpelican.com/en/stable/
[2] https://gitlab.com/spice/spice-space
Cheers,
toso
Victor Toso
2018-01-29 14:07:39 UTC
Permalink
Hi,
Post by Victor Toso
Post by Christophe de Dinechin
Post by Snir Sheriber
Post by Christophe de Dinechin
Post by Marc Dunivan
Is SPICE for the use case of providing a remote virtual
desktop only to a virtual machine’s graphical/desktop
environment? Additionally, the virtual machine host must
be a Linux OS, correct...SPICE server only runs on Linux?
SPICE can’t be used to obtain a remote desktop from a
Fedora GNOME PC to a Windows 10 PC, or visa versa?
At the moment, that’s correct. But a question asked at
DevConf reminded me that with the shift to Wayland, SPICE
may have an opportunity to provide a better Wayland remote
desktop experience. Any volunteer for that?
By the way, if that happens, we might want to consider this
a fourth possible location for the spice streaming agent
and attached plugins, the first three being the current
“in-guest”, the proposed “in spice server”, and Marc
André’s suggestion to put that in host outside of QEMU
process.
https://www.ctrl.blog/entry/wayland-gnome-remote-desktop
Cool!
That reminds me there is also an experimental spice backend
for Weston (Wayland compositor). iirc it worked nice but
still needed some more love. (maybe it worth a link on
spice-spice.org? ;) )
https://github.com/ein-shved/compositor-spice
Yes. Also worth adding to the SPICE top-level project I started working on. Will do.
I’m a bit fuzzy, was there any decision regarding
spice-space.org?
Decision about what?
Weren’t we discussing about where it’s hosted just yesterday in
Brno? Or is that now completely solved and stable? I was under
the impression that we were still looking for the optimal
hosting solution.
Ah, hosting... But the subject was about changing the
spice-space.org itself, that got me confused.

We have static pages with some static generator that works
although we can also improve design, content, etc. We just need a
place to display those html files and AFAIR, teuf was looking for
a new home to the spice-space.. not sure the status of that.
Thanks
Christophe
Post by Victor Toso
Post by Christophe de Dinechin
I’d like to be able to update things like the mac build
instructions or, when it’s in, instructions on how to use the
flight recorder data to tune performance.
AFAIR, you can submit changes to spice-space-pages [0] and some
VM is going to regenerate the spice-space.org page.
[0] https://gitlab.com/spice/spice-space-pages
We use Pelican [1] and if you want to generate the website in
your end, you can with spice-space repo [2]
[1] http://docs.getpelican.com/en/stable/
[2] https://gitlab.com/spice/spice-space
Cheers,
toso
Snir Sheriber
2018-01-29 14:25:29 UTC
Permalink
Hi

True, the process is still as toso mentioned.

Currently we are running for some time now in the new instance
(which is not openshift) seems stable so far.

Snir.
Post by Victor Toso
Hi,
Post by Christophe de Dinechin
Post by Victor Toso
Post by Christophe de Dinechin
Post by Snir Sheriber
Post by Christophe de Dinechin
Post by Christophe de Dinechin
Post by Marc Dunivan
Is SPICE for the use case of providing a remote virtual
desktop only to a virtual machine’s graphical/desktop
environment? Additionally, the virtual machine host must
be a Linux OS, correct...SPICE server only runs on Linux?
SPICE can’t be used to obtain a remote desktop from a
Fedora GNOME PC to a Windows 10 PC, or visa versa?
At the moment, that’s correct. But a question asked at
DevConf reminded me that with the shift to Wayland, SPICE
may have an opportunity to provide a better Wayland remote
desktop experience. Any volunteer for that?
By the way, if that happens, we might want to consider this
a fourth possible location for the spice streaming agent
and attached plugins, the first three being the current
“in-guest”, the proposed “in spice server”, and Marc
André’s suggestion to put that in host outside of QEMU
process.
https://www.ctrl.blog/entry/wayland-gnome-remote-desktop
Cool!
That reminds me there is also an experimental spice backend
for Weston (Wayland compositor). iirc it worked nice but
still needed some more love. (maybe it worth a link on
spice-spice.org? ;) )
https://github.com/ein-shved/compositor-spice
Yes. Also worth adding to the SPICE top-level project I started working on. Will do.
I’m a bit fuzzy, was there any decision regarding
spice-space.org?
Decision about what?
Weren’t we discussing about where it’s hosted just yesterday in
Brno? Or is that now completely solved and stable? I was under
the impression that we were still looking for the optimal
hosting solution.
Ah, hosting... But the subject was about changing the
spice-space.org itself, that got me confused.
We have static pages with some static generator that works
although we can also improve design, content, etc. We just need a
place to display those html files and AFAIR, teuf was looking for
a new home to the spice-space.. not sure the status of that.
Post by Christophe de Dinechin
Thanks
Christophe
Post by Victor Toso
Post by Christophe de Dinechin
I’d like to be able to update things like the mac build
instructions or, when it’s in, instructions on how to use the
flight recorder data to tune performance.
AFAIR, you can submit changes to spice-space-pages [0] and some
VM is going to regenerate the spice-space.org page.
[0] https://gitlab.com/spice/spice-space-pages
We use Pelican [1] and if you want to generate the website in
your end, you can with spice-space repo [2]
[1] http://docs.getpelican.com/en/stable/
[2] https://gitlab.com/spice/spice-space
Cheers,
toso
Loading...