![]() Now that you’ve noted the devices you want to use evdev with, it’s time to enable it in your libvirt XML. For example, if you see two entries for your keyboard, with one ending with “event-kbd” and the other ending with “event-mouse,” you will generally want to pick “event-kbd.” Some hardware manufacturers hate following standards, though, and you might find yourself needing to switch this up. Select the input device that corresponds to your device. A lot of mice will have keyboard inputs, and some keyboards even have mouse inputs. ![]() Another issue to be wary of is the input device type. If not, try another until you find the correct one. If garbled characters appear on-screen, you have selected the correct one. ![]() Press random keys on the keyboard you want to pass through. The best method to find out which one is correct is to use “cat.” Run: cat /dev/input/by-id/ The first is an “if01” or “if02” or similar near the end of an input device name. Be careful here, as I have noticed two common discrepancies. Take note of which ones you want to pass through. dev/input/by-id is generally preferred, as you can pass through input devices without worrying about the file path changing if you plug/unplug additional devices. The Linux kernel exposes two different locations for evdev devices: /dev/input, and /dev/input/by-id. This can get a little finicky, as some keyboard manufacturers do this differently. To start, you will need to find the input device IDs for your mouse and keyboard.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |