noVNC erratic mouse cursor in Win VM when display=spice

[andreisrr]

Hi,

I've had problems with Windows VMs (Win10 guests for testing) in the following context:
- display = default (initial install)
- install full virtio drivers
- change display to spice

At this stage I can access the VM very well using spice client, but if for any reason I have to access it using noVNC, the mouse is totally erratic and I can't do anything useful.

What did I do wrong?
Than kyou.

 

[driley]

Hi,

how did you setup the VM? Did you enable the Qemu Guest Agent flag?
If yes it could be because you are missing the Qemu Guest Agent on the guest machine (windows)

To remedy this install the "Qemu Guest Agent". You can find instructions on how to do this here:
https://pve.proxmox.com/wiki/Qemu-guest-agent

Additionally this is how I would setup my Windows Guest Machines:
System:
Machine: q35
Qemu Agent: true

BIOS: OVMF (UEFI)
Add EFI Disk: true

Disks:
Cache: Write Back
Discard: true
IO Thread: true

CPU:
Cores (min): 3

Memory:
RAM: 8192

Finish but don't boot it yet.
Attach the virtio drivers (can be found in the wiki guide above)
as a CD/DVD Drive with BUS set to IDE

In the installer when reaching the setup select the load drivers option
and search through the drivers you added using the CD/DVD Drive

The most important drivers would be the following:

• Hard disk
• Network:
• Memory Ballooning

Hope this helps.

 

[andreisrr]

So far I have this:
machine: 440fx
qemu agent was disabled, I enabled it
BIOS is SeaBIOS, replicating an environment with non-UEFI BIOS physical stations
Virtio single
disk with no cache, ssd emulation, io thread, io_uring (roughly defaults from new vm wizard)

The installer got the drivers for disk. (the only virtio device).
After first proper boot, installed from virtio drivers disk the entire set of virtio drivers. Also installed virtio-guest-tools.
power off, change network to virtio,
change display, usb, audio to spice.

now boot to usage.

I presumed at first that the guest agent = virtio-guest-tools. Apparently I was wrong.
Installed from ISO, from guest-agent subdir, the appropriate guest agent.

In Windows, under Settings -> Apps, I see virtio-guest-tools, but I don't see guest-agent.
I don't see guest-agent anywhere (when installing I was only asked to allow it to install, nothing else).
I see it installed under c:\program files, with guest-ga.exe having a distinctive icon. I see nothing in tray, but I see the process in Task Manager.

Powershell -> Get-Service QEMU-GA returns "running".

shell on the host with "qm agent VM_id ping" returns:
No QEMU guest agent configured

Apparently changing this setting for the VM needs complete poweroff of VM, not just restart.

Interesting that now "qm agent VM_id ping" returns nothing...

Anyway, after all this, mouse is still unusable in noVNC.

 

[driley]

Thanks for the input.
I'm not really sure what is causing these issues, but one last idea would be to change the Hardware -> Display from "default" / "spice" to "Standard VGA" when you are connecting using noVNC.

 

[andreisrr]

Thanks for the input.
I'm not really sure what is causing these issues, but one last idea would be to change the Hardware -> Display from "default" / "spice" to "Standard VGA" when you are connecting using noVNC.

I already know of that option. It requires a guest reboot though, which in some cases might be more then just an inconvenience.