Hi, > > Seems I'll try to start from the curses.c then, if that's better way > > (my knowledge of qemu codebase is zero and I'm not a good developer > > either, but I may try in my free time since I need this and I'd like
I wouldn't bother with curses. Better grab input events directly at the source, like virtio-input-host does. Check out hw/input/virtio-input-host.c, or https://www.kraxel.org/cgit/input/ (probably gives a better idea how to interpret the linux input layer events). Also note that hw/input/virtio-input-hid.c has a qcode -> linux mapping table, which should be usable to generate a reverse mapping. You'll need that to feed linux keyboard events into the qemu input code. > > to see it upstream - there are more people trying vga passthrough who > > possibly need this :)) At least keyboard, mouse is nice to have, but > > that can be done with the virtio-input, it's not crucial eg. during > > installation where you may not have those drivers. If virtio-input works for the mouse it should work equally well for keyboard. Guest drivers are upstream in kernel 4.1 & newer. Fedora 22 should work once you've updated the kernel (shipped with kernel 4.0.x, now at 4.2.x). With the just released Fedora 23 virtio-input should even work on the install media (didn't test that yet though ...). > > I was just wondering if you don't have a bunch of testing VMs that > > you've already used for this to quickly rule out one side (host or > > guest). I'm using standard fedora install, without any special tweaks (other than a self-compiled kernel in the early days, but even that isn't needed any more). cheers, Gerd
