Well, I DO see display, problem is with mouse cursor or mouse movement at all.
Let me tell you about our config.
Host is running Debian 10, QEMU 4.2, libspice-server 0.14.3, libvirt 5.0 with ramfb support patches. Nvidia drivers are 440.43 (actually, we tried different versions, problem stays here). Nvidia hardware consists of M10 and P100 cards.
We try to run Win 10, Ubuntu 20.04 and Ubuntu 18.04 guests.
With Win 10, situation is like I told earlier, no cursor in Nvidia window. It does not depend of is Nvidia VGPU adapter is the only one or is QXL video attached to VM too.
Windows problems are not so critical for us since we have tried RDP and are satisfied with it for that moment. But situation with Linux guests is worse. We try to use spice-streaming-agent with hardware-accelerated H264 encoding to achieve smooth video and 3D playback. At the moment, we have two different versions of plugin to spice-streaming-agent:
1) gst-plugin from git. It requires such configuration to work: video QXL + Nvidia MDEV with display="off". So, when VM is started, and remote-viewer is connected to VM, we have one QXL display with console boot messages. It becomes blank when X server starts. When spice-streaming-agent is run, second window with Nvidia display appears and first window remains black. That config is selected because no way existed to disable Spice display channel when spice-streaming-agent is run and its window opened, along with h264-compressed data stream original spice data was sent consuming network and CPU.
With this plugin, Ubuntu 20.04 with vd-agent 0.19 is working flawlessly with a visible mouse cursor.
When Ubuntu 18.04 (that is required urgently):
If vd-agent (0.18) is not running, after some VM power cycles (not reboots!) mouse appears but cursor position is not in sync with mouse events coordinates. After next VM power cycle mouse disappears again. Input devices configurations inside VM when mouse working and not working are equal.
If vd-agent 0.18 is running, no mouse events are seen on display, and lots of messages like "mouse event on unknown display 0>=0 (or 1>=1, I don't remember now)" are in syslog.
I tried to build vd-agent 0.20 here to check if this will fix situation but it can't open a channel :(
This plugin has drawbacks: it consumes lots of CPU; it depends on GStreamer with nvenc plugin that is not built by default, it depends on CUDA, so in case with Nvidia only Nvidia Quadro vGPU configurations are supported (more expensive licenses than Virtual PC license type), and with Nvidia M10 only 8Gbyte-vGPU configurations are supported that is definitely more than needed and only 4 guests per 32-Gbytes card.
2) a plugin that is currently in development. It uses Nvidia framebuffer capturing subsystem (FBC) so it requires vGPU attached with display="on" (else FBC is not working) and video set to "none". The plugin itself works better. But no mouse (movements or clicks) is seen even on Ubuntu 20.04 with vd-agent 0.19.
With ubuntu 18.04 I can get mouse in 2nd window (that is produced by spice-streaming-agent) when actually mouse is over 1st window (that has main spice data). In 1st window there is no visible cursor, and movements are not in sync with actual mouse position in my physical display. When mouse is over 2nd window (spice-streaming-agent generated), a lot of "mouse event on unknown display (1>=1)" messages are printed to VM syslog. So, if it's possible to somehow fix that behaviour, that would be great!
As a short summary: for me currently is very important to have working mouse in second configuration (with vGPU with display="on" and video set to "none").
Thank you in advance for any help!
03.06.2020, 11:59, "Frediano Ziglio" <fziglio@xxxxxxxxxx>:
,Hi,I think the mouse issue are similar to https://gitlab.freedesktop.org/spice/win32/vd_agent/-/issues/13 andIn other word for some combination of displays the agent is not able to handle mouse eventscausing the events to get discarded. The solution would be for the agent to either handle allcases or being able to tell the server that is not capable to handle the mouse allowingthe server to fall back to server mouse.I think you can see the display using the "console vnc" feature that allows Qemuto use spice to send "frames".Ole, what's your configuration for the guest/host or the mediated device?Software installed on the host?Type of Nvidia card/setup?Thanks,FredianoWell, I just create a VM with a mediated device, run it, set up Nvidia drivers, and after VM reboot its window can be shown with remote-viewer. When display is set to "none", just nvidia window appears, when QXL display is set, two windows appear.02.06.2020, 17:30, "Uri Lublin" <uril@xxxxxxxxxx>:On 6/2/20 4:50 PM, ole-krutov@xxxxxxxxx wrote:
Hi,
No, I do not use spice-streaming-agent with windows VM at all.
How do you see the NVIDIA window on the client ?01.06.2020, 22:24, "Uri Lublin" <uril@xxxxxxxxxx>:On 6/1/20 6:59 PM, ole-krutov@xxxxxxxxx
<mailto:ole-krutov@xxxxxxxxx> wrote:Now I have tried different combinations of vd-agent state and
mouse
cursor type. In no case mouse cursor was visible on nvidia display
window. With dual display, qxl+nvidia, stopping vd-agent made
cursor
visible on qxl window. Reaction to mouse events was seen on nvidia
window too, but with invisible mouse cursor.Hi,I assume you have your own spice-streaming-agent plugin.Does it support the display_info interface ?Uri01.06.2020, 17:27, "Frediano Ziglio" <fziglio@xxxxxxxxxx
<mailto:fziglio@xxxxxxxxxx>>:Hi all,
when just qxl adapter is attached to VM all works
well. But
when Nvidia GRID
instance is attached and its drivers are running,
mouse cursor
is never
shown on its display window. Sometimes it's just
invisible but
active and
reacting to mouse movements, clicks and wheel scrolling,
sometimes it's
totally missing. This behaviour is a bit dependent of is
Nvidia adapter
alone or together with qxl. Just sometimes mouse
cursor is
visible on qxl
display but it's very unstable and totally unusable.
Similar
behaviour is
under linux VM too. Is it normal "won't fix" state,
or can I
provide some
additional info? Windows has latest vd-agent and
spice-agent
installed.
Hi,
recently we got similar reports. Can you try to see
what's happen if
you disable the agent?It seems that in these conditions the agent is not able to
handle
the mouse
so mouse events are "lost".Another test would you could do is to use the "spicy"
utility. This
utility
has an option to switch manually the mouse mode
(server/client). It
would be
helpful to understand different behaviour using the 2 modes.Frediano
_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
<mailto:Spice-devel@xxxxxxxxxxxxxxxxxxxxx>
https://lists.freedesktop.org/mailman/listinfo/spice-devel
_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/spice-devel
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel