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.
The vnc protocol doesn't support that. Fundamental problem is there is no message to notify the client about the cursor position. So using a hardware cursor (let vnc client render the cursor via rich cursor extension) works with absolute mouse mode (aka tablet) only where this notification is not needed in the first place.
Workaround #1: use spice instead of vnc.
Workaround #2: use usb-tablet instead of a mouse.
Description of problem:Guest's screen can't capture mouse events correctly when VNC remote connection guest . Version-Release number of selected component (if applicable):qemu-kvm-rhev-2.12.0-7.el7,3.10.0-919.el7.x86_64(guest & host) How reproducible:100% Steps to Reproduce: 1.Boot rhel 7 guest with a mouse and VNC display with commands below /usr/libexec/qemu-kvm -name virtio-vga -m 2G -machine vmport=off,accel=kvm \ -cpu Skylake-Client,enforce \ -smp 4 \ -serial unix:/tmp/console1,server,nowait \ -monitor stdio \ -device virtio-vga,id=vga1,yres=1080,xres=1920 \ -drive file=/home/SnB.qcow2,if=none,id=drive-scsi-disk0,format=qcow2,cache=none,werror=stop,rerror=stop -device virtio-scsi-pci,id=scsi0,addr=04 -device scsi-hd,drive=drive-scsi-disk0,bus=scsi0.0,scsi-id=0,lun=0,id=scsi-disk0,bootindex=1 \ -netdev tap,id=idinWyYp,vhost=on -device virtio-net-pci,mac=70:5a:0f:38:cd:99,id=idlbq7eA,netdev=idinWyYp \ -device ich9-usb-uhci6 \ -vnc :0 \ 2.Use remote-viewer to connect to guest and check mouse function inside guest. Actual results:Guest can't capture mouse events correctly. Expected results:mouse buttons is usable correctly. Additional info: