This is a feature request. I think.

My target: A monitor wall with 16 Full HD monitors. Each monitor connected to a small computer (Raspi for example). An Linux Host with client Win7 and 16 screens defined via qxl driver. Each Raspi should now connect via remote viewer to one screen on the Win7 Client and display it on its own monitor. 

If this already works, than how? And if not, why?

Greetings

Created attachment 137149 [details]
Graphical view of whish

One guest with 17 monitors? We support only up to 4 monitors in the guest.

But if I got what you mean correctly, you want to split one monitor to 16 areas for the video wall, is that correct?

Somehow. What I tried is, I have defined 4 video qxl sections in the win7.xml file. Than it was possible to do
virsh start win7
remote-viewer spice://localhost:5900
And add than under View / Display the screens and windows expanded it´s desktop over it

But what I want is to open more remote-viewers on different machines which I can than select the virtual monitor inside Win7 what I want to see there.

For Windows each video qxl section is a new monitor and it expands over it. What I need is windows which expands over maybe 16 or even more monitors and that I can get the picture from each monitor in a different remote-viewer.

And yes I want a monitor wall driven by one vm in a host. The vm can than freely move in the cloud and the monitor wall will show what ever we want there.

I hope it's understandable. I am not a native English speaker.

greetings

Pseudocode:

Virsh start win7

On raspi_1
remote-viewer spice://hostmachine:5900 --display1

On raspi_2
remote-viewer spice://hostmachine:5900 --display2

On raspi_3
remote-viewer spice://hostmachine:5900 --display3

On raspi_4
remote-viewer spice://hostmachine:5900 --display4

And so on
.
.
.

With Windows is not that complicated, each display has a different channel, with Linux would be quite hard (you have only a single channel)
From the server prospective you need to accept multiple connections. There's code to allow it but was always a not supported feature, you have to set a SPICE_DEBUG_ALLOW_MC environment (as the DEBUG suggest was never production ready).
From the client you'll have to implement the --display option (which is not that hard, just connect at this/these monitors) and maybe have a master/slave (so only a machine have the control but I think that currently only the first machine connected to server has the control).

You still have the 16 monitors limit problem.

How would you control the VM? Just launch a program that play a video or similar without input?

The VM has only to display a certain software on a dedicated screen. Once setup no interaction needed.

And at the moment we talk about 10 physical displays. But I would like that feature for more than that. Think about a presentation in a hall with thousands of people and a presentation on 100 monitors which is for the director just the same than using his home pc.

I think, what we want here is one connection that splits the display and forwards that to a monitor wall.

So, if we implement the GStreamer Spice source element ( https://bugs.freedesktop.org/show_bug.cgi?id=101830 ) it should be possible to split the streaming in the client to N streams to make the monitor wall (like https://gstreamer.freedesktop.org/apps/videowhale.html)

The monitor wall itself in Spice protocol, I don't see the need for it.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/spice/spice-gtk/issues/60.