Mouse clicking but not moving in some Distros with evDev

Nov 8, 2025
1
0
1
Hello everybody,
brief description of my Problem:
I use Proxmox with GPU-Passthrough and two GPUs. To switch mouse and keyboard between host and guest I use evDev. In most Distributions like WIndows 11, PopOS and so on everything works, just with CachyOS (and at least the live version of Ubuntu) the keyboard works fine, mouse also clicks (both right and left) but it just isn't moving. Evtest doesn't pick up any movement. A USB mouse though works.

Additional Infos:
I use Xfce4 on my proxmox host, I know, I'm not supposed to do that, but for the last 2 years everything worked just fine. The problem came a few days ago and I can't think of anything that might have triggered it. For test purposes I used a installation of windows, ubuntu and cachyos in the VM (ID 105). In the windows installer the mosue moves. In a different VM (106) I have PopOs installed, the mouse is moving and in a live version of Ubuntu and CachyOS it isn't.

journalctl -r after the start of the VM shows the following:
Code:
Nov 08 19:13:10 malte sudo[132617]: pam_unix(sudo:session): session opened for user root(uid=0) by malte(uid=1000)
Nov 08 19:13:10 malte sudo[132617]:    malte : TTY=pts/2 ; PWD=/home/malte ; USER=root ; COMMAND=/usr/bin/journalctl -r
Nov 08 19:12:51 malte dnsmasq-dhcp[1638]: DHCPACK(subnet) 10.10.100.100 bc:24:11:7d:86:e3 malte-gameos
Nov 08 19:12:51 malte dnsmasq-dhcp[1638]: DHCPREQUEST(subnet) 10.10.100.100 bc:24:11:7d:86:e3
Nov 08 19:12:41 malte kernel: kvm: kvm [131996]: ignored rdmsr: 0xc001029a data 0x0
Nov 08 19:12:41 malte kernel: kvm: kvm [131996]: ignored rdmsr: 0xc001029b data 0x0
Nov 08 19:12:41 malte kernel: kvm_do_msr_access: 2 callbacks suppressed
Nov 08 19:12:35 malte sudo[132199]: pam_unix(sudo:session): session closed for user root
Nov 08 19:12:26 malte sudo[132199]: pam_unix(sudo:session): session opened for user root(uid=0) by malte(uid=1000)
Nov 08 19:12:26 malte sudo[132199]:    malte : TTY=pts/2 ; PWD=/home/malte ; USER=root ; COMMAND=/usr/bin/journalctl -r
Nov 08 19:12:23 malte sudo[131620]: pam_unix(sudo:session): session closed for user root
Nov 08 19:12:17 malte kernel: usb 1-14.2: reset full-speed USB device number 6 using xhci_hcd
Nov 08 19:12:15 malte kernel: kvm: kvm [131996]: ignored wrmsr: 0xc0000410 data 0x22
Nov 08 19:12:15 malte kernel: kvm: kvm [131996]: ignored rdmsr: 0xc0000410 data 0x0
Nov 08 19:12:15 malte kernel: kvm: kvm [131996]: ignored wrmsr: 0xc0000410 data 0x22
Nov 08 19:12:15 malte kernel: kvm: kvm [131996]: ignored rdmsr: 0xc0000410 data 0x0
Nov 08 19:12:15 malte kernel: kvm: kvm [131996]: ignored wrmsr: 0xc0000410 data 0x22
Nov 08 19:12:15 malte kernel: kvm: kvm [131996]: ignored rdmsr: 0xc0000410 data 0x0
Nov 08 19:12:15 malte kernel: kvm: kvm [131996]: ignored wrmsr: 0xc0000410 data 0x22
Nov 08 19:12:15 malte kernel: kvm: kvm [131996]: ignored rdmsr: 0xc0000410 data 0x0
Nov 08 19:12:15 malte kernel: kvm: kvm [131996]: ignored wrmsr: 0xc0000410 data 0x22
Nov 08 19:12:15 malte kernel: kvm: kvm [131996]: ignored rdmsr: 0xc0000410 data 0x0
Nov 08 19:12:05 malte systemd[1]: systemd-rfkill.service: Deactivated successfully.
Nov 08 19:12:00 malte pvedaemon[122179]: <root@pam> end task UPID:malte:00020390:001E05F1:690F87EB:qmstart:105:root@pam: OK
Nov 08 19:12:00 malte pvedaemon[131984]: VM 105 started with PID 131996.
Nov 08 19:12:00 malte systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
Nov 08 19:12:00 malte systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status...
Nov 08 19:12:00 malte kernel: vfio-pci 0000:0b:00.0: reset done
Nov 08 19:12:00 malte kernel: vfio-pci 0000:0b:00.0: resetting
Nov 08 19:12:00 malte kernel: vfio-pci 0000:0b:00.3: reset done
Nov 08 19:12:00 malte kernel: vfio-pci 0000:0b:00.2: reset done
Nov 08 19:12:00 malte kernel: vfio-pci 0000:0b:00.1: reset done
Nov 08 19:12:00 malte kernel: vfio-pci 0000:0b:00.0: reset done
Nov 08 19:12:00 malte kernel: vfio-pci 0000:0b:00.3: resetting
Nov 08 19:12:00 malte kernel: vfio-pci 0000:0b:00.2: resetting
Nov 08 19:12:00 malte kernel: vfio-pci 0000:0b:00.1: resetting
Nov 08 19:12:00 malte kernel: vfio-pci 0000:0b:00.0: resetting
Nov 08 19:12:00 malte kernel: vfio-pci 0000:0b:00.0: reset done
Nov 08 19:12:00 malte kernel: vfio-pci 0000:0b:00.0: resetting
Nov 08 19:11:56 malte kernel: subnet: port 1(tap105i0) entered forwarding state
Nov 08 19:11:56 malte kernel: subnet: port 1(tap105i0) entered blocking state
Nov 08 19:11:56 malte kernel: tap105i0: entered allmulticast mode
Nov 08 19:11:56 malte kernel: subnet: port 1(tap105i0) entered disabled state
Nov 08 19:11:56 malte kernel: subnet: port 1(tap105i0) entered blocking state
Nov 08 19:11:56 malte kernel: tap105i0: entered promiscuous mode
Nov 08 19:11:56 malte systemd[1]: Started 105.scope.
Nov 08 19:11:56 malte kernel: vfio-pci 0000:0b:00.0: reset done
Nov 08 19:11:56 malte kernel: vfio-pci 0000:0b:00.0: resetting
Nov 08 19:11:55 malte pvedaemon[131984]: start VM 105: UPID:malte:00020390:001E05F1:690F87EB:qmstart:105:root@pam:

The config file of my VM looks as follow:
Code:
agent: 1
args: -object input-linux,id=kbd1,evdev=/dev/input/by-id/usb-Logitech_G815_RGB_MECHANICAL_GAMING_KEYBOARD_046E303E3836-event-kbd,grab_all=true,grab-toggle=scrolllock -object input-linux,id=kbd2,evdev=/dev/input/by-id/usb-Logitech_G815_RGB_MECHANICAL_GAMING_KEYBOARD_046E303E3836-if01-event-kbd -object input-linux,id=mouse1,evdev=/dev/input/by-id/usb-Logitech_G502_HERO_Gaming_Mouse_0D74387A3538-event-mouse -object input-linux,id=kbd3,evdev=/dev/input/by-id/usb-Logitech_G502_HERO_Gaming_Mouse_0D74387A3538-if01-event-kbd -device ich9-intel-hda,id=sound1,bus=pci.0,addr=0x18 -device hda-micro,audiodev=hda -audiodev pa,id=hda,server=/run/user/1000/pulse/native
balloon: 0
bios: ovmf
boot: order=virtio0;ide2
cores: 6
cpu: host
efidisk0: speicher:105/vm-105-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
hostpci0: 0000:0b:00,pcie=1
ide2: speicher:iso/ubuntu-24.04.iso,media=cdrom,size=6197156K
kvm: 1
machine: q35
memory: 16384
meta: creation-qemu=9.0.2,ctime=1737365433
name: Game-OS
net0: rtl8139=BC:24:11:7D:86:E3,bridge=subnet
numa: 0
ostype: l26
scsihw: virtio-scsi-single
smbios1: uuid=3b450438-2415-48df-9efb-49ccfa598596
sockets: 1
tablet: 0
tags: lin
usb0: host=1-14.2
usb1: host=1-11
vga: none
virtio0: speicher:105/vm-105-disk-3.qcow2,iothread=1,size=1000G
vmgenid: a6034cc4-2060-4ebc-87e7-926ca42482c7

I am a bit of a noob, so I am already very sorry for the tones of mistakes I have probably already done and I am very grateful for any help!
Thank you already!

Update: Also tried switching back to xserver-xorg-input-evdev, also didn't work, still trying around with no clue
 
Last edited:
Since the issue seems to be affecting only some of the VMs and not others, it might be related to how input devices are being passed through or handled in certain VM configurations. A few things you could try:
Check VM Configuration: Ensure the problematic VMs are using the correct input device settings. You might need to adjust the USB tablet or PS/2 settings in the VM's hardware options.
Update Guest Additions/Tools: If the VM relies on particular drivers, such as QEMU guest tools or VMware/VirtualBox guest additions, ensure they are updated. These can affect input device functionality.
Examine Proxmox Logs: Check Proxmox's syslog and VM-specific logs for any errors or warnings when starting the affected VMs. Sometimes the logs give a crucial hint about what's missing or failing.
Compare Software Versions: Since you mentioned everything worked fine for two years, consider whether a recent Proxmox or guest OS update could correlate with this issue. Reverting or reconfiguring after an update may help.
Test Different Display Protocols: If you're using SPICE or VNC for your VM display, try switching to another protocol and see if the issue persists.