On Tue, 2017-04-25 at 15:43 +0100, Patrick O'Callaghan wrote: > On Tue, 2017-04-25 at 06:43 -0700, Jamie Lawrence wrote: > > > On Apr 25, 2017, at 4:45 AM, Christopher Thompson > > > <chris.thomps...@synopsys.com> wrote: > > > > > > This sounds like the PS/2 driver/emulated hardware controller gets itself > > > in knots. PS/2 isn't hot plug, so if something goes wrong it's generally > > > stuffed until a reboot, which sounds like your issue. > > > > > > One common option is to use Synergy, which passes the keyboard and mouse > > > over the network, you set up the synergy service running on the Linux > > > host, with it configured to map an edge of the screen to your Windows VM, > > > then when the Windows VM is running and the synergy client connects you > > > can move the mouse over that edge of the screen and it will appear on > > > Windows (if you have multiple monitors this looks like the mouse > > > seamlessly goes from one screen to the other). > > > > I use Synergy, and the bug occurs with it as well. It adds a layer of > > confusion when it happens, but that's about it. (I use a hardware KVM > > switching two videocards to the same monitor, but the mouse isn't connected > > to it.) At least with the Synergy version I have, the UI locks up under > > windows, but it keeps functioning. The bug also happens without it running. > > > > Spent some time attempting to force the bug this weekend, but didn't manage > > to. I'll try again to get some logging soon. > > That's useful to know, thanks.
I installed Synergy and it just happened to me again. What isn't clear to me is if Synergy is actually being used. I know it's running on both host (as server) and guest (as client) but the guest also has the PS/2 mouse because virt-manager doesn't let you remove it. I wonder if it's necessary to run KVM/QEMU from the command line to get this to work properly. poc _______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
