Problem solved! I did not need any additional drivers for this to work! I usually install the virtio-win-guest-tools.exe from the virtio ISO but even that is not necessary to get SPICE video with mouse sync to work. Instead of toggling the tablet support of and on in Options you can simply add: Then you re-enable tablet support but proxmox does not delete this line, it changes it to:Īnd when proxmox sees tablet: 1 in the config, it starts the VM with the tablet support even if the display is set to spice. When you turn the tablet support off in options, proxmox modifies the config file for the VM and inserts this: Proxmox DOES NOT start it with the -device usb-tablet,id=tablet,bus=ehci.0,port=1 option!!! Even though it claims that it's on under Options! NOW! Change the display from Default to SPICE and start the VM. It's omitted but proxmox is launching the VM with it because it is the default option. If you look at the config file for the VM under /etc/pve/qemu-server/.conf you see no mention of tablet: 1 in that config file. device usb-tablet,id=tablet,bus=ehci.0,port=1 If you inspect the kvm process that proxmox started and the parameters it pased this is confirmed: When you create a new Win VM with default display and start it, it by default starts with tablet support (for mouse sync). Here's what's going on and why it seemed to work for some and not others. Mouse is synced and survives reboots, etc. Under options, Use tablet for pointer is set to yes. Now the resolution can be changed but mouse is not synced. I switch the video to SPICE and power off/on the machine. It also explains why it doesn't work for a lot of people.īrand new windows VM, with default video.I connect to the console via usual proxmox novnc way and. I think a found a solution for this and it works consistently in my environment. Thanks in advance for any help the community is able to provide. (I have not had these issues with Linux VM desktops + Spice.) I'd be using Linux VMs for this if the VPN clients were Linux-compatible. Other than this Windows 10 mouse business, I really do like Proxmox and Spice. Has anyone else run into mouse issues like this with Windows 10 and Spice? Any tips or workarounds? If I RDP into the "bad" VM, the mouse works. Plain Windows 10, followed the best practices guide, and it works as expected. I have another VM with pretty much the same setup. I've reinstalled Windows 10 numerous times, trying different drivers.changed power settings, updated Proxmox, updated virt-viewer, etc. Spice connects, and the keyboard works, but the mouse will not work at all in one of my VMs. I basically followed the directions in the Windows 10 best practices guide, using the latest Virtio drivers, QEMU agent, etc. It's gotten somewhat better, but I am having issues with my mouse working in one VM over Spice. With Windows 7 being out of mainline support, I decided to try Windows 10 again. I fell back to Windows 7, which worked great. I tried using Windows 8 and Windows 10 with Spice several years ago, and it was a total mess at the time. I have been using Proxmox for several years, mostly to host VMs that I use to connect to various VPNs without breaking my local desktop networking.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |