Description of problem: CentOS 7 installer image booted in Fedora 24 virt-manager shows two mouse arrows, with the VM one not properly tracking my mouse movements, making it essentially impossible (without a lot of effort) to use the VM. The problem doesn't happen with Fedora 24 or 25 images. Version-Release number of selected component (if applicable): virt-manager-1.4.0-3.fc24.noarch libvirt-daemon-driver-qemu-1.3.3.2-1.fc24.x86_64 libvirt-client-1.3.3.2-1.fc24.x86_64 libvirt-daemon-driver-nwfilter-1.3.3.2-1.fc24.x86_64 libvirt-daemon-driver-secret-1.3.3.2-1.fc24.x86_64 libvirt-daemon-driver-network-1.3.3.2-1.fc24.x86_64 libvirt-daemon-driver-interface-1.3.3.2-1.fc24.x86_64 libvirt-glib-0.2.3-2.fc24.x86_64 libvirt-daemon-1.3.3.2-1.fc24.x86_64 libvirt-daemon-config-network-1.3.3.2-1.fc24.x86_64 libvirt-python-1.3.3-3.fc24.x86_64 libvirt-gconfig-0.2.3-2.fc24.x86_64 libvirt-daemon-driver-nodedev-1.3.3.2-1.fc24.x86_64 libvirt-daemon-driver-storage-1.3.3.2-1.fc24.x86_64 libvirt-daemon-kvm-1.3.3.2-1.fc24.x86_64 libvirt-gobject-0.2.3-2.fc24.x86_64 xorg-x11-drv-qxl-0.1.4-7.fc24.x86_64 xorg-x11-drv-libinput-0.19.0-2.fc24.x86_64 libinput-1.4.1-1.fc24.x86_64 ibus-wayland-1.5.13-3.fc24.x86_64 libwayland-server-1.10.0-1.fc24.x86_64 xorg-x11-server-Xwayland-1.18.4-1.fc24.x86_64 libwayland-client-1.10.0-1.fc24.x86_64 gnome-shell-3.20.4-1.fc24.x86_64 How reproducible: c Always Fedora-Server-netinst-x86_64-25-20160819.n.1.iso Never Fedora-Workstation-Live-x86_64-25_Alpha-2.iso Never Steps to Reproduce: 1. Boot virt-manager-1.4.0-3.fc24.noarch 2. 3. Actual results: See video screencast. Expected results: One mouse arrow in the VM that properly tracks physical mouse movements. Additional info:
Created attachment 1194951 [details] screencast
Created attachment 1194952 [details] virsh dumpxml
Created attachment 1194953 [details] ps aux grep qemu
Happens on Wayland, does not happen on X.
Happens with openSUSE-Leap-42.2-DVD-x86_64-Build0164-Media.iso which as of today is the most recent beta for the next version of Leap.
Can you attach one of the VM XML configs? I'm curious if somehow <input bus='usb' type='tablet'/> isn't being added
It's the 2nd item under attachments.
Even a newly created VM lacks <input type='tablet' bus='usb'> - adding it does solve this problem.
Yeah this is a virt-manager issue with new libosinfo, fixed upstream. I'll backport
commit d725713114b8c521648da3f00c33cd10f0c00fc2 Author: Cole Robinson <crobinso> Date: Fri Jul 29 13:17:36 2016 -0400 osdict: Fix incorrect usage of virtio input
(Adding myself to the CC list. A VM I created last week was impacted by this.)
This was fixed in virt-manager-1.4.0-5.fc24 in mid december