Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
mouse not comply user's action in win7 guest with qxl
Version-Release number of selected component (if applicable):
host:
qemu-kvm-1.5.3-19.el7.x86_64
kernel-3.10.0-57.el7.x86_64
guest:
win7-64/32
qxl-win-0.1-19
How reproducible:
100%
Steps to Reproduce:
1.cli:
/usr/libexec/qemu-kvm \
-M pc \
-cpu Opteron_G1,check \
-m 4G \
-smp 4,sockets=2,cores=2,threads=1,maxcpus=16 \
-enable-kvm \
-name win7 \
-uuid 990ea161-6b67-47b2-b803-19fb01d30d12 \
-smbios type=1,manufacturer='Red Hat',product='RHEV Hypervisor',version=el6,serial=koTUXQrb,uuid=feebc8fd-f8b0-4e75-abc3-e63fcdb67170 \
-k en-us \
-rtc base=localtime,clock=host,driftfix=slew \
-nodefaults \
-monitor stdio \
-qmp tcp:0:6666,server,nowait \
-boot menu=on \
-bios /usr/share/seabios/bios.bin \
-vga qxl \
-spice port=5900,disable-ticketing \
-global PIIX4_PM.disable_s3=0 \
-global PIIX4_PM.disable_s4=0 \
-drive file=/home/win7-64.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop,aio=threads \
-device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 \
-netdev tap,id=hostnet0,fd=7 7<>/dev/tap7 \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=4e:5d:ac:10:26:dc \
2.In desktop, Press and hold the left mouse button then draft it from left top to right bottom, like select all icons use mouse in desktop.
3.
Actual results:
Mouse not comply with user's action, like someone drag it from reverse, mouse move with shake while draft it.
Expected results:
Mouse move smoothly.
Additional info:
Change vga to cirru/std this problem gone, Downgrade qxl to qxl-win-0.1-17.
Comment 2Marc-Andre Lureau
2014-03-05 16:13:58 UTC
Which client do you use?
I can't reproduce with virt-manager. Both mouse in client or server mode works fine.
Just found use virt-viewer-0.5.7-7.el7.x86_64 on rhel7 desktop, works well.
if connect rhel7 by ""ssh -X hostname" from fc18, got problem.
Comment 8Marc-Andre Lureau
2014-03-07 11:44:54 UTC
(In reply to mazhang from comment #7)
> Just found use virt-viewer-0.5.7-7.el7.x86_64 on rhel7 desktop, works well.
> if connect rhel7 by ""ssh -X hostname" from fc18, got problem.
Ok, changing bug title.
That makes sense. The client uses gdk_display_warp_pointer(), which isn't working over remote protocols. If your guest is configured correctly, you have mouse in client mode. For that to work, you need a working usb-tablet and/or a spice-vdagent.
I am tempted to close this bug as WONTFIX, since this is more a configuration issue and technical limitation.
Could you try with a guest using usb tabler & running vdagent?
thanks