Red Hat Bugzilla – Bug 618242
position of mouse pointer displayed in the spicec is different from real mouse pointer position on guest
Last modified: 2013-08-25 20:30:59 EDT
Description of problem:
I found that mouse coordinates become somehow garbled after changing resolution from lower to higher.
I was able to reproduce this issue on Win7 guest with 2 displays. I'll try to find out how much system/display specific the issue is.
Version-Release number of selected component (if applicable):
Guest contains software installed from RHEV-toolsSetup_2.2_46140 media
Steps to Reproduce:
1. sudo /usr/libexec/qemu-kvm -vga qxl -device qxl -m 1024 -spice port=3001,disable-ticketing -usbdevice table <win7.img>
2. /usr/libexec/spicec --host localhost --port 3001
3. change resolution of gues from lower to higher (in my case 1024x768 -> 1440x900)
Both (x,y) coordinates seems to be dependent on distance from upper left corner of primary display (0,0)
I think that it behaves like (x += x, y+=y)
Displayed position of the cursor should be equal to the real position.
Display coordinates seems to be like (x += x, y+=y) from upper left corner of the primary display.
Created attachment 434418 [details]
Created attachment 434419 [details]
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Please retry with the following in mind:
1. Do not use -usbdevice tablet when running with multi-monitor spice.
2. Use spice-vmc device (-device virtio-serial -device spicevmc,nr=0)
3. Install qxl driver on guest
4. Install spice-vmc driver on guest
5. Install appropriate vdagent and vdservice (they are not the same as in
RHEV-2.2, adjusting to the new spicevmc device)
6. Make sure vdservice and vdagent are running
- start -> run -> cmd + net start vdservice (or check the logs)
Following the above, with a Win XP guest, I could not reproduce the bug.
Ping me on IRC if you need any help.
This issue has not been reproduced on el6 any more.