Hi On Mon, Nov 16, 2015 at 4:34 PM, Victor Toso <lists@xxxxxxxxxxxxxx> wrote: > Hm.. I would either prefer that mouse mode did not change if it can't > because the function and its documentation suggested that it will only > try to change the mouse mode. I am testing this series again, and trying to understand your issue. I am still not able to reproduce it though. I can only imagine the guest is having vmport enabled (check Xorg.log "for VMWare VMMouse"). Spice expects server mode to be working in general (whereas client mode depends on having a tablet + agent running). So there is no easy check to know if the server mode should work, as it should. We could have qemu tell if vmport is enabled, but that would be a configuration issue anyway since there would be no way to make server mode work correctly when vmmouse abs/rel mismatched with what the client/server selected. You could also have multiple "pointers" attached to the same input source in qemu, one using absolute and the other relative... One can conclude that spice is incompatible with vmmouse (since we don't detect vmmouse configuration mismatch and can easily get stuck mouse, also vmmouse is redundant with the tablet we use), so I will send a patch to qemu to disable it by default when spice is used and error when enabled. -- Marc-André Lureau _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel