You are not logged in.
Pages: 1
From yesterday to today, all of a sudden, the mouse in one of my windows guests is no longer working. On other guests it still works fine.
I'm really puzzled by this as didn't make any changes to neither guest nor host. The guest had its last windows update a week ago, and according to the pacman log, my last activities on the host were also from a week ago.
The error logs are clean, too. No error messages in the windows event viewer, no error or warning messages in the libvirt log for the specific VM, journalctl not showing any suspicious entries either.
I tried the following so far without success.
- Reboot of the VM
- Reboot of the host
- Running Windows update on the guest and pacman -Syu on the host
It's not just the mouse, though, either. I noticed that the resolution gets no longer adapted to the size of the remote viewer screen - it just gets scaled down instead. Which is why I'm quite sure there's something wrong with SPICE here but again, I have no indication as to where that could come from and I don't know how to resolve it. I tried the following steps with no success so far:
- Reinstalling Windows SPICE guest tools as a whole and later, several components separately (guest-agent, qxldod, vioinput)
- Removing the tablet device from libvirt and then put it back
- Since I have 2 screens, I tried removing one "Video QXL" card using virt-manager. Oddly enough, that didn't work, virt-manager didn't give me a choice to remove the second card even though I used virt-manager to put it there in the first place. So I edited the XML using virsh edit. I could now remove the second card but otherwise no improvements.
If I use RDP to connect to the VM, everything works properly, including mouse. I have this problem only if I access the host directly through SPICE. The keyboard works fine, but the mouse doesn't at all, and dynamic screen resolution isn't working either.
Any advice what next to try?
Last edited by vic-t (2018-11-13 14:27:44)
Offline
Another step I just tried is to recreate the VM by taking the XML from a working VM just to exclude any mistakes in the virsh config. The issue remains the same as described above.
Offline
Could you try starting the VM directly from terminal (see qemu page in wiki) and post the output ?
That would help to determine if virt-manager is the problem cause or not.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Ok, so it looks like this is solved. By removing the guest tools and video drivers in Windows, then reinstalling the latter, I was able to use the mouse again. Dynamic resolution changes started working again after I reinstalled the guest tools (latest version).
I still don't understand what caused this but I'm glad it works again. Hopefully this will be helpful to someone else.
Offline
@Lone_Wolf: Saw your message only just now, sorry. But it looks like virt-manager was not to blame.
Offline
Pages: 1