Bug 641980
Summary: | mouse does not work in virt guests | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Poelstra <poelstra> |
Component: | qemu | Assignee: | Justin M. Forbes <jforbes> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 14 | CC: | amit.shah, berrange, crobinso, dwmw2, ehabkost, gcosta, hbrock, itamar, jaswinder, jforbes, knoel, kraxel, markmc, ondrejj, scottt.tw, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-10-19 19:25:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John Poelstra
2010-10-11 17:17:20 UTC
FWIW, keyboard does work. I think this is a qemu issue. Latest QEMU has broken non-tablet mouse according to Gerd's patch series upstream: http://lists.nongnu.org/archive/html/qemu-devel/2010-10/msg00410.html We should really make sure that series is applied for F14. Smells like a dup of bug 636887 Checking the Xorg.0.log from the guest to see if it activated 'vmmouse' will confirm whether its the same issue. After discussing more on #fedora-qa we determined this was a result of me NOT specifying the OS and Version in the virt-manager GUI. I created a new guest by correctly specifying OS=Linux and Version=Fedora 14 and mouse works fine. I created a new guest and specified OS=Linux and Version=Ubuntu 10.4 and ran Ubuntu 10.10 install and mouse does NOT work. Removing F14Blocker. If you didn't select an OS type, then instead of getting a USB tablet, you would have got the default QEMU mouse which is PS/2 + vmmouse extensions. So I still reckon you were hitting the QEMU bug i mention. Xorg.0.log can confirm. *** This bug has been marked as a duplicate of bug 636887 *** |