Bug 981540
Summary: | can not see mouse in guest when lanch the guest with virt-viewer | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | EricLee <bili> |
Component: | virt-viewer | Assignee: | Virt Viewer Maint <virt-viewer-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | acathrow, bili, cfergeau, codong, dblechte, dyuan, lcui, mzhan, tzheng |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-19 09:17:40 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: | |
Embargoed: |
Description
EricLee
2013-07-05 05:45:29 UTC
Sorry for wrong judgement of exsiting bug 980714, they should be the same root reason causeed: This only reproduced in the guest with spice+qxl as graphic type, not reproduced in a vnc guest. And the error in qemu/guest.log is the same as the bug https://bugzilla.redhat.com/show_bug.cgi?id=980714, so I think it is the same issue displaying in different kinds of component. Most likely the same as https://bugzilla.redhat.com/show_bug.cgi?id=981094 The proper fix belongs to qemu, but I don't know if RHEL7 qemu has the needed patch. However, libvirt 1.1.1 has a workaround for this, so this bug should no longer occur. Eric, are you still seeing this? I did not hit this when using remote-viewer on RHEL7. (In reply to Christophe Fergeau from comment #4) > Eric, are you still seeing this? I did not hit this when using remote-viewer > on RHEL7. No, I can not reproduce it both in virt-viewer and remote-viewer with package: libvirt-1.1.1-15.el7.x86_64 qemu-kvm-rhev-1.5.3-21.el7.x86_64 Ok, thanks for confrming! It was probably the same bug as bug #981094 Closing this bug now. |