> An optimal solution to this would be that the driver knows somehow when > we are in a server mode and when we are in a client mode. However this > information isn't available in the driver nor in the vdagent. Could you explain why an optimal solution require this knowledge? Also "However this information isn't available in the driver nor in the vdagent." does not make sense to me. The vdagent is sending this information to the driver so this information is available in vdagent. Frediano > On Mon, Aug 8, 2016 at 6:33 PM, Christophe Fergeau < cfergeau@xxxxxxxxxx > > wrote: > > On Mon, Aug 08, 2016 at 06:19:41PM +0300, Sameeh Jubran wrote: > > > > > > > > > This patch enables the driver to send move commands to the QXL device > > > when > > > > vdagent is off. > > > > This maybe the reason you are not getting any move commands. > > > But don't we have exactly the same issue with a fedora guest or a win7- > > > guest? I've observed the same with a Fedora guest at least. > > > Also I don't think there is a strict equivalence between vdagent is > > > running and mouse is in server mode, so if we were to change this at the > > > agent level, are we going to fix all cases? > > > Christophe > > -- > Respectfully, > Sameeh Jubran > Linkedin > Junior Software Engineer @ Daynix . > _______________________________________________ > Spice-devel mailing list > Spice-devel@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/spice-devel _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel