[SOLVED] Spice Connections unresponsive to input after a few minutes idle

R

rpm5099

New Member
Jan 16, 2024
11
2
3
I'm using virt-viewer to access VM's on proxmox via spice from Windows 11. It works great for about 2 minutes, but as soon as it is left idle for a few minutes the vm becomes completely unresponsive to input via spice - however the output still appears to be getting refreshed. The vm is otherwise functioning normally and the gui works fine via the proxmox web interface console. I've looked at the output of running virt-viewer using:



`"C:\Program Files\VirtViewer v11.0-256\bin\remote-viewer.exe" -v --debug --spice-debug pve-spice.vv`



as well as looking at the output of spiceproxy on proxmox by stopping the service and running:



`spiceproxy start --debug`



I've also extensively grepped /var/log on all of the vm's which include Rocky 9 and Ubuntu 22. I'm not seeing anything at all that jumps out at me as being related, by timestamp or content, to the vm's becoming unresponsive. I don't usually run into brick walls where I have no idea what additional steps to take to troubleshoot, but I'm totally lost on this. I appreciate advice, I can provide whatever info necessary.


> root@proxmox:/var/log#kvm --version
QEMU emulator version 8.1.5 (pve-qemu-kvm_8.1.5-3)
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers

> root@proxmox:/var/log#pveversion
pve-manager/8.1.4/ec5affc9e41f1d79 (running kernel: 6.5.13-1-pve)


remote-viewer.exe version 11.0-256
 
Hi,

Does the issue only occurs on Windows 11? or other VMs?

Have you checked the network traffic of SPICE when you start the `remote-viewer` until the SPICE is unresponsive?
 
Moayad said:
Hi,

Does the issue only occurs on Windows 11? or other VMs?

Have you checked the network traffic of SPICE when you start the `remote-viewer` until the SPICE is unresponsive?
Click to expand...
Hi there - I'm actually remoting into Linux vm's from a bare metal Windows 11. I have not tried remoting in from a Linux machine but I can do that. I have not captured pcap and looked through it, although I can do that, but I'm certain the connection is active because if I do things through the proxmox web ui console the spice client shows everything real time, it just doesn't accept any input at all. Does that provide the information you need? Thanks for replying.
 
I tested from a Ubuntu 23 Vmware vm and it did the exact same thing on multiple proxmox vm's. This makes me 100% certain that the problem is on the Proxmox itself. I would really appreciate any input anyone can provide.
 
Hi,

Could you please run `journalctl -f` and check the message error you see when the SPICE does not respond?
 
Sure - I don't see in here an entry that corresponds exactly to when the VM stops responding but it's hard to tell because it doesn't seem to stop responding while you are using it, but as soon as you leave it idle for several minutes all input from mouse and keyboard is ignored entirely. This output spans from before connecting via spice to after the spice session freezes input.

Code: 
(py3115)user@[hostname]:~$sudo journalctl -f
Mar 11 10:53:44 [hostname] spice-vdagent[3288]: vdagent-audio: (capture-right) 65535 (100.00%)
Mar 11 10:53:49 [hostname] dbus-daemon[1322]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.91' (uid=1000 pid=3115 comm="/usr/bin/gnome-shell " label="unconfined")
Mar 11 10:53:49 [hostname] systemd[1]: Starting Fingerprint Authentication Daemon...
Mar 11 10:53:49 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:53:49 [hostname] dbus-daemon[1322]: [system] Successfully activated service 'net.reactivated.Fprint'
Mar 11 10:53:49 [hostname] systemd[1]: Started Fingerprint Authentication Daemon.
Mar 11 10:53:49 [hostname] gnome-shell[3115]: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
                                                       asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
Mar 11 10:54:00 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:54:02 [hostname] sudo[323784]:      user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/journalctl -f
Mar 11 10:54:02 [hostname] sudo[323784]: pam_unix(sudo:session): session opened for user root(uid=0) by user(uid=1000)
Mar 11 10:54:10 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Received Graphics Device Info:
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Mapping connector Virtual-1 to display #0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found matching X Output: name=Virtual-1 id=66
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Adding graphics device info: channel_id: 0 monitor_id: 0 device_address: pci/0000/01.0, device_display_id: 0 xrandr output ID: 66
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Mapping connector Virtual-2 to display #1
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found matching X Output: name=Virtual-2 id=67
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Adding graphics device info: channel_id: 0 monitor_id: 1 device_address: pci/0000/01.0, device_display_id: 1 xrandr output ID: 67
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Mapping connector Virtual-3 to display #2
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found matching X Output: name=Virtual-3 id=68
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Adding graphics device info: channel_id: 0 monitor_id: 2 device_address: pci/0000/01.0, device_display_id: 2 xrandr output ID: 68
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Mapping connector Virtual-4 to display #3
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found matching X Output: name=Virtual-4 id=69
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Adding graphics device info: channel_id: 0 monitor_id: 3 device_address: pci/0000/01.0, device_display_id: 3 xrandr output ID: 69
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found monitor Virtual-1 with geometry 1488x1072+0-0 - associating it to SPICE display #0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: 1/4 displays found - completing with disabled displays.
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Received Graphics Device Info:
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Mapping connector Virtual-1 to display #0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found matching X Output: name=Virtual-1 id=66
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Adding graphics device info: channel_id: 0 monitor_id: 0 device_address: pci/0000/01.0, device_display_id: 0 xrandr output ID: 66
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Mapping connector Virtual-2 to display #1
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found matching X Output: name=Virtual-2 id=67
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Adding graphics device info: channel_id: 0 monitor_id: 1 device_address: pci/0000/01.0, device_display_id: 1 xrandr output ID: 67
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Mapping connector Virtual-3 to display #2
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found matching X Output: name=Virtual-3 id=68
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Adding graphics device info: channel_id: 0 monitor_id: 2 device_address: pci/0000/01.0, device_display_id: 2 xrandr output ID: 68
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Mapping connector Virtual-4 to display #3
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Device /dev/dri/card0 is at /sys/devices/pci0000:00/0000:00:01.0/drm/card0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found card '/sys/devices/pci0000:00/0000:00:01.0/drm/card0' with Vendor ID 0x100, Device ID 0x1b36
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found matching X Output: name=Virtual-4 id=69
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Adding graphics device info: channel_id: 0 monitor_id: 3 device_address: pci/0000/01.0, device_display_id: 3 xrandr output ID: 69
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: Found monitor Virtual-1 with geometry 1488x1072+0-0 - associating it to SPICE display #0
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: 1/4 displays found - completing with disabled displays.
Mar 11 10:54:18 [hostname] spice-vdagentd[2568]: Set max clipboard: 104857600
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: vdagent_audio_playback_sync mute=no nchannels=2
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: vdagent-audio: (playback-left) 65535 (100.00%)
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: vdagent-audio: (playback-right) 65535 (100.00%)
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: vdagent_audio_record_sync mute=no nchannels=2
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: vdagent-audio: (capture-left) 65535 (100.00%)
Mar 11 10:54:18 [hostname] spice-vdagent[3288]: vdagent-audio: (capture-right) 65535 (100.00%)
Mar 11 10:54:19 [hostname] systemd[1]: fprintd.service: Deactivated successfully.
Mar 11 10:54:21 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:54:22 [hostname] dbus-daemon[1322]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.91' (uid=1000 pid=3115 comm="/usr/bin/gnome-shell " label="unconfined")
Mar 11 10:54:22 [hostname] systemd[1]: Starting Fingerprint Authentication Daemon...
Mar 11 10:54:22 [hostname] dbus-daemon[1322]: [system] Successfully activated service 'net.reactivated.Fprint'
Mar 11 10:54:22 [hostname] systemd[1]: Started Fingerprint Authentication Daemon.
Mar 11 10:54:22 [hostname] kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Mar 11 10:54:22 [hostname] kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Mar 11 10:54:22 [hostname] kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Mar 11 10:54:22 [hostname] kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Mar 11 10:54:31 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:54:33 [hostname] gdm-password][324026]: gkr-pam: unlocked login keyring
Mar 11 10:54:33 [hostname] dbus-daemon[2846]: [session uid=1000 pid=2846] Activating service name='org.freedesktop.FileManager1' requested by ':1.38' (uid=1000 pid=3115 comm="/usr/bin/gnome-shell " label="unconfined")
Mar 11 10:54:33 [hostname] NetworkManager[1324]: <info>  [1710168873.4875] agent-manager: agent[bd06cd86a7628928,:1.91/org.gnome.Shell.NetworkAgent/1000]: agent registered
Mar 11 10:54:33 [hostname] ubuntu-appindicators@ubuntu.com[3115]: unable to update icon for software-update-available
Mar 11 10:54:33 [hostname] ubuntu-appindicators@ubuntu.com[3115]: unable to update icon for livepatch
Mar 11 10:54:33 [hostname] dbus-daemon[2846]: [session uid=1000 pid=2846] Successfully activated service 'org.freedesktop.FileManager1'
Mar 11 10:54:33 [hostname] dbus-daemon[2846]: [session uid=1000 pid=2846] Activating service name='org.gnome.ArchiveManager1' requested by ':1.138' (uid=1000 pid=324149 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" label="unconfined")
Mar 11 10:54:33 [hostname] gnome-shell[3115]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x6022cf056300] is on because it needs an allocation.
Mar 11 10:54:33 [hostname] gnome-shell[3115]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x6022d1011700] is on because it needs an allocation.
Mar 11 10:54:33 [hostname] gnome-shell[3115]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x6022d1015ba0] is on because it needs an allocation.
Mar 11 10:54:33 [hostname] dbus-daemon[2846]: [session uid=1000 pid=2846] Successfully activated service 'org.gnome.ArchiveManager1'
Mar 11 10:54:33 [hostname] gnome-shell[3115]: DING: Detected async api for thumbnails
Mar 11 10:54:33 [hostname] gnome-shell[3115]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Mar 11 10:54:33 [hostname] gnome-shell[3115]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Mar 11 10:54:33 [hostname] gnome-shell[3115]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Mar 11 10:54:33 [hostname] gnome-shell[3115]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Mar 11 10:54:33 [hostname] gnome-shell[3115]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Mar 11 10:54:33 [hostname] gnome-shell[3115]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Mar 11 10:54:33 [hostname] gnome-shell[3115]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Mar 11 10:54:33 [hostname] gnome-shell[3115]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Mar 11 10:54:33 [hostname] gnome-shell[3115]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Mar 11 10:54:33 [hostname] gnome-shell[3115]: DING: GNOME nautilus 42.6
Mar 11 10:54:34 [hostname] kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Mar 11 10:54:34 [hostname] kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Mar 11 10:54:34 [hostname] kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Mar 11 10:54:34 [hostname] kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Mar 11 10:54:41 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:54:43 [hostname] nautilus[324142]: Could not delete '.meta.isrunning': No such file or directory
Mar 11 10:54:52 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:54:52 [hostname] systemd[1]: fprintd.service: Deactivated successfully.
Mar 11 10:55:02 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:55:13 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:55:23 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:55:34 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:55:44 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:55:55 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:56:05 [hostname] qemu-ga[1335]: info: guest-ping called
Mar 11 10:56:16 [hostname] qemu-ga[1335]: info: guest-ping called
 
I think you are looking for the conf file in /etc/pve/nodes/proxmox/qemu-server/. If so, here's an example of one that is not working:

agent: 1
balloon: 4096
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
ide2: none,media=cdrom
machine: q35
memory: 16384
meta: creation-qemu=8.1.2,ctime=1706847305
name: Ubuntu22
net0: virtio=BC:24:11:E8:90:4E,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
parent: before_watchdog
protection: 1
scsi0: local-zfs:vm-103-disk-0,iothread=1,size=150G
scsihw: virtio-scsi-single
smbios1: uuid=eb50c164-c2e2-4f1e-bc33-ea5904342dc6
sockets: 1
vmgenid: 0e3ea960-ebbd-4616-98d7-a2eb28e3b1d9
watchdog: model=i6300esb,action=reset
 
Hi,

Thank you for the VM config!

rpm5099 said:
Mar 11 10:54:22 [hostname] kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Mar 11 10:54:22 [hostname] kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Mar 11 10:54:22 [hostname] kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Mar 11 10:54:22 [hostname] kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Click to expand...

Errors related to `nvidia-drm` indicate that there may be issues with the GPU drivers, I would check if the Nvidia driver has an update available.

Does the other VM have a GPU passedthrough?
 
It probably does but that's not what's causing the spice problem. That's something I added 3 days ago. Spice froze input before the hardware was even installed in the machine.
 
Here is the entire list of snapshot configs, none of which have worked with spice. I appreciate your help, but are we getting any closer to finding the problem?


Code: 
agent: 1
balloon: 4096
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
ide2: none,media=cdrom
machine: q35
memory: 16384
meta: creation-qemu=8.1.2,ctime=1706847305
name: Ubuntu22
net0: virtio=*********bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
parent: *********
protection: 1
scsi0: local-zfs:vm-103-disk-0,iothread=1,size=150G
scsihw: virtio-scsi-single
smbios1: uuid=eb50c164-c2e2-4f1e-bc33-ea5904342dc6
sockets: 1
vmgenid: 0e3ea960-ebbd-4616-98d7-a2eb28e3b1d9
watchdog: model=i6300esb,action=reset

[snapshot]
agent: 1
balloon: 4096
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
ide2: none,media=cdrom
machine: q35
memory: 16384
meta: creation-qemu=8.1.2,ctime=1706847305
name: Ubuntu22
net0: virtio=*********bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
parent: **************
protection: 1
runningcpu: host,+kvm_pv_eoi,+kvm_pv_unhalt
runningmachine: pc-q35-8.1+pve0
scsi0: local-zfs:vm-103-disk-0,iothread=1,size=150G
scsihw: virtio-scsi-single
smbios1: uuid=eb50c164-c2e2-4f1e-bc33-ea5904342dc6
snaptime: 1707450552
sockets: 1
vmgenid: 0e3ea960-ebbd-4616-98d7-a2eb28e3b1d9
vmstate: local-zfs:vm-103-******

[Snapshot]
agent: 1
balloon: 4096
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
ide2: none,media=cdrom
machine: q35
memory: 16384
meta: creation-qemu=8.1.2,ctime=1706847305
name: Ubuntu22
net0: virtio=*********bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
parent: *******
protection: 1
runningcpu: host,+kvm_pv_eoi,+kvm_pv_unhalt
runningmachine: pc-q35-8.1+pve0
scsi0: local-zfs:vm-103-disk-0,iothread=1,size=150G
scsihw: virtio-scsi-single
smbios1: uuid=eb50c164-c2e2-4f1e-bc33-ea5904342dc6
snaptime: 1709071137
sockets: 1
vmgenid: 0e3ea960-ebbd-4616-98d7-a2eb28e3b1d9
vmstate: local-zfs:vm-103-**********

[snapshot]
agent: 1
balloon: 4096
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
ide2: none,media=cdrom
machine: q35
memory: 16384
meta: creation-qemu=8.1.2,ctime=1706847305
name: Ubuntu22
net0: virtio=*********bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
parent: ********
scsi0: local-zfs:vm-103-disk-0,iothread=1,size=150G
scsihw: virtio-scsi-single
smbios1: uuid=eb50c164-c2e2-4f1e-bc33-ea5904342dc6
snaptime: 1706856506
sockets: 1
vmgenid: 0e3ea960-ebbd-4616-98d7-a2eb28e3b1d9

[snapshot]
agent: 1
balloon: 4096
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
ide2: none,media=cdrom
machine: q35
memory: 16384
meta: creation-qemu=8.1.2,ctime=1706847305
name: Ubuntu22
net0: virtio=*********bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
scsi0: local-zfs:vm-103-disk-0,iothread=1,size=150G
scsihw: virtio-scsi-single
smbios1: uuid=eb50c164-c2e2-4f1e-bc33-ea5904342dc6
snaptime: 1706851121
sockets: 1
vmgenid: 0e3ea960-ebbd-4616-98d7-a2eb28e3b1d9

[snapshot]
agent: 1
balloon: 4096
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
ide2: none,media=cdrom
machine: q35
memory: 16384
meta: creation-qemu=8.1.2,ctime=1706847305
name: Ubuntu22
net0: virtio=*********bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
parent: clean_ubuntu22_install
scsi0: local-zfs:vm-103-disk-0,iothread=1,size=150G
scsihw: virtio-scsi-single
smbios1: uuid=eb50c164-c2e2-4f1e-bc33-ea5904342dc6
snaptime: 1706854709
sockets: 1
 
Last edited:
To narrow down the issue, I would test the `remote-viewer` on a different workstation/box and see if it has the same behavior.
 
Moayad, I think I found the problem and it was my fault, it was a timeout on haproxy. I screwed up and didn't realize the local connections were going through the proxy because I didn't have an explicit DNS rule set. If the connection was being killed completely or never went through networking would have been the first thing I checked, but somehow it was only killing traffic on the connection going from client to server. Sorry to waste your time, in case it helps anyone these settings in the backend passthrough of the haproxy backend for your spice proxy will fix the problem:

Code: 
timeout tunnel 7200s
timeout queue 30s
 
  • Like
Reactions: moisapto and Heinrich Pechtold
Hi,

Glad to hear that you solved the issue yourself! I will go ahead and set your thread as [SOLVED] to help the other people who have similar issue.

Have a nice day :)
 
I solved the same problem by using this information in haproxy (pfsense)
It worked fine.
Thanks for posting this!
Your hint is a great working solution.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom