Description of problem: Mouse pointer within virtual MacOS doesn't move at the same speed as real mouse pointer. It seems like the the acceleration of motion does matter - when i make a short, but fast movement - mouse moves all along the screen. The problem persist in Windows virtual machines, but it is solved by enabling tablet device (that use absolute mouse positioning) which cannot be added to MacOS. The bug does not affect system that use X (e.g. fedora). The problem is not localized in virt-manager or VNC or spice, using html5spice and virsh, vnc and virt-manager does not change a thing. Version-Release number of selected component (if applicable): qemu-kvm-1.2.2-6.fc18.x86_64 How reproducible: always Steps to Reproduce: 1. Install qemu-kvm and any virtual machine manager (e.g. virt-manager) 2. Install MacOS, run (or install Windows and disable tablet device) 3. Move mouse in VM Actual results: Virtual mouse moves faster than actual mouse Expected results: Virtual mouse is synced with actual mouse
There is a choice between 3 pointing devices, ps/2 mouse (relative motion), usb tablet (absolute motion), spice guest agent (absolute motion). AFAIK, the spice agent isn't ported to OX-S, so that leaves the USB tablet as the only option if you want to have a mouse point that moves at the same speed in the guest as in the host. I find it hard to believe that OS-X doesn't support the USB tablet, since this is a designed to support the generic tablet capability that is part of the USB HID spec which basically any OS will support.
I made a mistake, i can add usb tablet, but it does not override ps/2 relative mouse, so active mouse is still relative and overspeeded. Figured it out by spice debug message (through html5spice), that reports mouse mode as "SPICE_MOUSE_MODE_SERVER", while absolute position mouse is reported as "SPICE_MOUSE_MODE_CLIENT" mouse mode. OS X is 10.4.7 if it does matter.
hmm, libvirt unconditionally adds a ps2 mouse on the qemu command line, but that hasn't caused a problem for other OS. maybe the fix here is to allow disabling the ps2 mouse with libvirt, but that would probably need some hacky XML addition handling like <input type='none' bus='ps2'/> or something.
(In reply to Cole Robinson from comment #3) > hmm, libvirt unconditionally adds a ps2 mouse on the qemu command line, We don't specify anything actually. QEMU always gives you a ps2 keyboard + mouse no matter what & AFAIK, there's no way to disable that. Any other mouse should override the PS2 mouse, provided the guest OS actually initializes the non-ps2 mouse.
(In reply to Daniel Berrange from comment #4) > (In reply to Cole Robinson from comment #3) > > hmm, libvirt unconditionally adds a ps2 mouse on the qemu command line, > > We don't specify anything actually. QEMU always gives you a ps2 keyboard + > mouse no matter what & AFAIK, there's no way to disable that. Any other > mouse should override the PS2 mouse, provided the guest OS actually > initializes the non-ps2 mouse. hmm, my mistake. not sure what to do with this bug though, it's not a virt-manager or libvirt issue, and since macosx support is considered pretty experimental at the qemu level, my recommendation to the reporter is to try to eliminate libvirt from the equation and see if you can get qemu working directly from the command line. if you can't get that working, report an upstream qemu bug. if you can qemu working, maybe there's some special incantation that libvirt needs to support.
Well... I would have liked to test windows 10 VM with a ps2 mouse disabled too. My issue is that Windows does not detect the mouse as a touchpad but as a ps2/mouse. This means there is no "palm detection" when I am typing in my VM....