NoVNC console mouse way off from local mouse

[Guy]

Since upgrading to 7.2-5 the console of the VMs seems to have developed an issue where the mouse cursor inside the VM is way off from the local mouse and make it impossible to navigate a graphical UI.

I've restarted the VM and browser, I've also tried rebooting the proxmox server.

Sometimes the cursor lines up but after a while it's gone again.

This is happening for windows 7, 10, and linux such as Ubuntu and Kali.

I have a short video which shows this very clearly.. the screenshot is taken from this.

Really stuck at the moment as many of my users can't use their VM systems.

Any help or suggestions would be most welcome.

Cheers,
--Guy

 

[Moayad]

Hello,

Did you installed/enabled Spice on your VMs?

Have you tried a different OS to manage your noVNC (since some software such as Drawing on Desktop makes an issue with noVNC/SPICE)?

 

[Guy]

No I've not enabled Spice.. We need to use NoVNC because we are proxying the access over HTML5. All access is only via HTML.

I've tried connecting via windows, Mac, and Linux (Debian). All show the same behavour.

 

[dcsapak]

can you post the vm config? (qm config ID) ? and the output of 'pveversion -v' ?

 

[Guy]

Details requested attached.

Let me know if you need anything more.

#SJC-Agent-20220614
#
#Windows 10 with SJC HX Agent
agent: 1
boot: order=virtio0;net0
cores: 2
cpu: kvm64
kvm: 1
machine: pc-i440fx-6.2
memory: 4096
meta: creation-qemu=6.2.0,ctime=1655233799
name: Copy-of-VM-SJC-Agent-20220614
net0: virtio=26:A0:3D:EC:12:76,bridge=vmbr0,tag=200
numa: 0
onboot: 0
ostype: win10
scsihw: lsi
smbios1: uuid=c0ab0ec4-0195-4edc-aadd-378d72ffde7d
sockets: 1
tablet: 0
vga: std,memory=32
virtio0: LabImages:138/base-138-disk-0.raw/20045/vm-20045-disk-0.qcow2,iothread=0,size=50G
vmgenid: 8026fe09-22c3-4ab3-8483-df8286fb2c40




# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.35-2-pve)
pve-manager: 7.2-5 (running version: 7.2-5/12f1e639)
pve-kernel-5.15: 7.2-5
pve-kernel-helper: 7.2-5
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.4: 6.4-4
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-5
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

 

[dcsapak]

tablet: 0

can you try to enable the tablet as pointer device again? (that should be the default)

 

[Guy]

Excellent, that seems to have fixed it.

What's interesting is that the tablet setting is not something we change. In our env users create VMs from templates and those templates are created using packer, which does not make this setting. So I'm not sure how these got changed.

Thanks for the assistance here.

--Guy

 

[optical]

How do you do that?

I am also having this issue with latest Proxmox and latest Win11. My pointer is totally out of sync, even after enabling spice. How do I change that tablet option that fixes it?

 

[netwebdave]

@optical
Click the VM in Proxmox --> Options (in same column as Summary, Console, etc.). Look for Use Tablet for Pointer

 

[jdesousa]

I am also facing this issue on a Solaris 10 VM, I have tried setting the tablet to 0 and 1 but the pointer onscreen does not map to the pointer in the VM, any help much appreciated

 

[RayRayNoob]

I have to same issue, but in windows 10. The mouse cusor is way off, thus making it unusable

 

[dooferorg]

I have this too just trying to install Windows 10 on a VM on a new Proxmox 8.2.2 host. 'Use tablet for pointer' IS enabled already in the Options for the VM.

 

[Kingneutron]

If the virtio drivers are already installed, and spice instead of novnc has been tried, your best bet may be to use remote desktop such as nomachine instead of trying to console from the browser.

 

[SInisterPisces]

Sometimes when this happens and nothing else works, I check the resolution setting inside the VM. If it's set to something much too large, like over 5K, I experience this issue.

Some versions of Linux get confused with certain hardware and mis-select the resolution, I guess. If your Windows is set to a strange resolution in NoVNC and you can't change it, enter the BIOS inside the VM (when it starts) and do it from there.

 

[dbadge]

I had something similar happen to me. To fix it, on the affected VM I unchecked the 'Use tablet for pointer', then re-checked it. This seems to have fixed the issue for me.

 

[nightowl]

This happens to me on the latest PVE as of today while connecting to a nested PVE 8.2.7 system (so Debian 12 with KDE installed running Plasma X11). PVE on the host, and the nested VM, is at 8.2.7 with updates from the no-subscription repo on test machines. The spice-vdagent service is running in the VM.

The problem occurs with spice only, however. NoVNC works fine in every resolution I have tried. Some resolutions seem to work, regardless of being 4:3 or not - for example 2048x1152 (16:9) and 2560x1600 (16:10). But others result in vertical mouse position issues where the mouse is offset by a pretty significant number of pixels (the virtual mouse pointer is closer to the top of the window than the real mouse pointer). This can be easily seen when moving the mouse over a button - since the button doesn't highlight until the real mouse pointer is moved down far enough.

It seems like a math problem somewhere in virt-viewer. Note that the "Use tablet for pointer" option made no difference for me.