On Sun, 2017-04-30 at 10:48 +0100, Dan Oram wrote: > On 25/04/17 15:50, Patrick O'Callaghan wrote: > > On Tue, 2017-04-25 at 14:09 +0200, Javier Celaya wrote: > > > Another option is to use input-linux: > > > https://www.kraxel.org/blog/2016/04/linux-evdev-input-support-in-qemu-2-6/ > > > I'm not sure how to use it with libvirt, though, I always use qemu from > > > the > > > command line. > > > > > > However, take into account that it does not work reliably until qemu > > > 2.9.0-rc3 (I sent a patch to fix it that was included upstream on March > > > this year) > > > > > > > I have 2.7 so I'll keep an eye on this, thanks. > > > > poc > > > > _______________________________________________ > > vfio-users mailing list > > vfio-users@redhat.com > > https://www.redhat.com/mailman/listinfo/vfio-users > > > > I've used it reliably since 2.7 though until the recent patch I had to > add a virtio input device for keyboard and mouse in addition to the > built in PS/2 device. Looking at the patch I guess that worked because > virtio has much better buffering. I might keep it though as it's more > likely to be immune to windows update and I swear that is out to get me. > > Definitely the approach to recommend. No ctrl-alt-backspace getting > redirected to your host X server or losing focus on the host to a dialog > and so losing input. Beyond essential if you've got a single monitor or > are using fullscreen applications such as games where the mouse needs > it's own scale / boundary constraints.
I'll definitely give it a go, thanks. poc _______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
