| | 1 | Feedback about this page and suggestions for improvements are always welcome on the vbox-dev mailing list<1>! |
| | 2 | |
| | 3 | 1. https://www.virtualbox.org/mailman/listinfo/vbox-dev |
| | 4 | |
| | 5 | = Investigating problems with keyboard input in !VirtualBox = |
| | 6 | |
| | 7 | The code which picks up keyboard events from the host for the default user interface it in the files: |
| | 8 | |
| | 9 | src/VBox/Frontends/VirtualBox/src/runtime/UIKeyboardHandler.cpp |
| | 10 | src/VBox/Frontends/VirtualBox/src/runtime/UIMouseHandler.cpp |
| | 11 | |
| | 12 | Unfortunately there is no logging available here. The code to read the keyboard is different for Windows, X11 and OS X. |
| | 13 | |
| | 14 | After this, the events are passed on to Main, which is the middle-layer between front-ends and virtual machines. |
| | 15 | |
| | 16 | src/VBox/Main/src-client/KeyboardImpl.cpp |
| | 17 | |
| | 18 | Main takes care of things which otherwise all front-ends would have to do (not much for the keyboard), then passes the events on to the device emulation code. The path here will be different depending on whether we are using PS/2 keyboard emulation (almost always) or USB keyboard. The device emulation makes the events appear on the guest virtual hardware. |
| | 19 | |
| | 20 | src/VBox/Devices/Input/ |
| | 21 | |
| | 22 | There is logging<2> code here, respectively log group "dev_kbd" and "usb_kbd" |
| | 23 | |
| | 24 | 2. wiki:VBoxLogging |
| | 25 | |
| | 26 | To monitor exactly what the guest is seeing you are best using native tools in the guest operating system, such as evtest, xinput and xev in Linux/X11 guests and keylook<3> in Windows guests. |
| | 27 | |
| | 28 | 3. https://superuser.com/questions/348070/equivalent-for-xev-on-windows |
