Windows 10 VM input becomes unresponsive

[lukeeexd]

I have a windows 10 VM, sometimes input like mouse clicks dont work or moving the mouse in the VNC doesnt move it in the VM. I can press the windows key and move around with the arrow keys just mouse input stops working. The VM isnt frozen because what was running beforehand still runs and the time updates etc. The only way to fix is to stop the VM and after booting back up the mouse is out of sync https://i.imgur.com/OPAuF7G.gif. Theres 2 other Windows VMs that dont have this issue. Any advice?

 

[Moayad]

hi,

Are you using SPICE on the Windows VM?


Please post:
pveversion -v
qm config <VMID>

 

[lukeeexd]

hi,

Are you using SPICE on the Windows VM?


Please post:
pveversion -v
qm config <VMID>

Hi,

I am using NoVNC. I've tried SPICE but just couldnt get it to work.

pveversion -v:

proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-helper: 6.2-2
pve-kernel-5.4: 6.2-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-8
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-6
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1

qm config:

bootdisk: ide0
cores: 4
ide0: local-zfs:vm-995-disk-0,size=32G
ide2: none,media=cdrom
memory: 4096
name: Newfie
net0: e1000=6E:4B:AA:D9:81:3D,bridge=vmbr1,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=d01bcebb-d467-4ed4-af4e-4fb56763c25e
sockets: 1
vmgenid: 69769885-7d83-42ab-8a86-a017179fdc16

 

[Moayad]

If you need to use SPICE just following our Wiki [1], however you could to start SPICE by click on Console -> SPICE like the image below.

if you don't need use SPICE, just disable SPICE by going to Datacenter -> Windows VM -> Hardware -> Display. Edit it and select as Default.

hope this helps

[1] https://pve.proxmox.com/wiki/SPICE

 

[lukeeexd]

If you need to use SPICE just following our Wiki [1], however you could to start SPICE by click on Console -> SPICE like the image below.

if you don't need use SPICE, just disable SPICE by going to Datacenter -> Windows VM -> Hardware -> Display. Edit it and select as Default.

hope this helps

[1] https://pve.proxmox.com/wiki/SPICE

Yes I've tried all that. It doesnt fix my root issue though..

 

[lukeeexd]

It just happened on a separte VM now

 

[Moayad]

hi,

Please update your node to the current version then reboot PVE and try again please

 

[lukeeexd]

Okay updated I will reply here if it happens again

 

[lukeeexd]

hi,

Please update your node to the current version then reboot PVE and try again please

Happened just now

 

[Moayad]

on my workstation works normally, ok try to uninstall SPICE on Windows VM and make sure to disable on settings as well.

 

[lukeeexd]

on my workstation works normally, ok try to uninstall SPICE on Windows VM and make sure to disable on settings as well.

I am not using SPICE and never was. I am using NoVNC. The issue doesnt happen on boot, its random. It could go days without happening then just randomly happens

 

[Moayad]

when it happen again try on the different browser, or browser without plugins

 

[lukeeexd]

when it happen again try on the different browser, or browser without plugins

Tried different browers, ipad, mobile phone etc it happens to anyone trying to use the VM even in a different country