Bug 1370887

Summary: virt-manager not setting usb tablet device
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: berrange, bugzilla, crobinso, dhgutteridge, kparal, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-16 13:57:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screencast
none
virsh dumpxml
none
ps aux grep qemu none

Description Chris Murphy 2016-08-28 00:31:14 UTC 
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:
Comment 1 Chris Murphy 2016-08-28 00:31:57 UTC 
Created attachment 1194951 [details]
screencast
Comment 2 Chris Murphy 2016-08-28 00:32:36 UTC 
Created attachment 1194952 [details]
virsh dumpxml
Comment 3 Chris Murphy 2016-08-28 00:33:10 UTC 
Created attachment 1194953 [details]
ps aux grep qemu
Comment 4 Chris Murphy 2016-08-28 00:42:05 UTC 
Happens on Wayland, does not happen on X.
Comment 5 Chris Murphy 2016-09-02 21:17:39 UTC 
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.
Comment 6 Cole Robinson 2016-09-02 22:39:42 UTC 
Can you attach one of the VM XML configs? I'm curious if somehow <input bus='usb' type='tablet'/> isn't being added
Comment 7 Chris Murphy 2016-09-02 23:05:50 UTC 
It's the 2nd item under attachments.
Comment 8 Chris Murphy 2016-09-02 23:13:22 UTC 
Even a newly created VM lacks <input type='tablet' bus='usb'> - adding it does solve this problem.
Comment 9 Cole Robinson 2016-09-08 20:19:02 UTC 
Yeah this is a virt-manager issue with new libosinfo, fixed upstream. I'll backport
Comment 10 Cole Robinson 2016-09-08 21:30:18 UTC 
commit d725713114b8c521648da3f00c33cd10f0c00fc2
Author: Cole Robinson <crobinso>
Date:   Fri Jul 29 13:17:36 2016 -0400

    osdict: Fix incorrect usage of virtio input
Comment 11 David H. Gutteridge 2016-12-15 20:37:26 UTC 
(Adding myself to the CC list. A VM I created last week was impacted by this.)
Comment 12 Cole Robinson 2017-01-16 13:57:23 UTC 
This was fixed in virt-manager-1.4.0-5.fc24 in mid december