ada/Surferlul.github.io
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update 2022-07-21-input-to-vm.md

Browse Source
This commit is contained in:
Lu Baumann 2023-10-07 19:53:39 +02:00 committed by GitHub
parent 3bd7b44e82
commit 5bdc91cb6a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
_posts/2022-07-21-input-to-vm.md
View File

@ -40,7 +40,7 @@ tag, located in
<devices>
~~~
This will allow the mouse cursor to move from inside of the VM. This is also needed for any other type of passthrough, for example USB passthrough. But the displayed cursor lags all of the time, only updating its position if it mouses over a animated element. A way to get around this in GNOME and GDM is by enabling the Zoom feature in the Accessibility menu. Set the magnification factor to 1.0 and enable it. Now the mouse cursor is smooth, and the content is still displayed properly. Configure this for your GNOME desktop and GDM. For configuring the magnification factor check out [Configure GDM](/configure-gdm). To change the magnification factor from the terminal, execute
This will allow the mouse cursor to move from inside of the VM. This is also needed for any other type of passthrough, for example, USB passthrough. But the displayed cursor lags all of the time, only updating its position if it mouses over an animated element. A way to get around this in GNOME and GDM is by enabling the Zoom feature in the Accessibility menu. Set the magnification factor to 1.0 and enable it. Now the mouse cursor is smooth, and the content is still displayed properly. Use Wayland for this approach, because X11 will lag. Configure this for your GNOME desktop and GDM. For configuring the magnification factor in GDM check out [Configure GDM](/configure-gdm). To change the magnification factor from the terminal, execute
~~~bash
dconf write /org/gnome/desktop/a11y/magnifier/mag-factor 1.0
@ -48,7 +48,7 @@ dconf write /org/gnome/desktop/a11y/magnifier/mag-factor 1.0
# Setting up the script
Now install [remote-evdev-python](https://github.com/Surferlul/remote-evdev-python) on your host and guest machine. For this you need a minimum python version of 3.10 with pip installed.
Now install [remote-evdev-python](https://github.com/Surferlul/remote-evdev-python) on your host and guest machine. For this, you need a minimum Python version of 3.10 with pip installed.
~~~bash
git clone https://github.com/Surferlul/remote-evdev-python
@ -56,13 +56,20 @@ cd remote-evdev-python
./setup <machine type>
~~~
replace \<machine type\> with guest, host, or nothing (for both) respectively. Check for Permission errors. On the guest you need permission to /dev/uinput. On the hosts you need permissions to /dev/input/event\*. Permissions for these devices are often handled through the "input" group. Consider adding yourself to the group, or modifying the permissions for the input devices.
replace `<machine type>` with guest, host, or nothing (for both) respectively. Check for Permission errors. On the guest, you need permission to `/dev/uinput`. On the hosts, you need permissions to `/dev/input/event\*`. You can execute the scripts as root. If you use root you will have to install the directory `./remote-evdev/` as root.
~~~bash
sudo pip3 install ./remote-evdev/
~~~
If you want to execute them as an unprivileged user, you have to give yourself the permissions. Permissions for these devices are often handled through the "input" group. Consider adding yourself to the group, or modifying the permissions for the input devices. For `/dev/uinput` you also have to modify group permissions.
~~~bash
# Add yourself to the group
sudo usermod -aG input $USER
# Modify permissions for uinput
sudo chown root:input /dev/uinput
sudo chmod +060 /dev/uinput
# Modify permissions for event devices
sudo chown root:input /dev/input/event*
~~~
@ -88,4 +95,4 @@ Now you can modify the "host" and "guest" script respectively. The guest script
To find a event for a device you can cat the event files in /dev/input, /dev/input/by-path and /dev/input/by-id. Try not to use the files in /dev/input, because those can change in contrary to the files in by-path and by-id. If you need to you can also switch the server and client roles around ("--server" and "--client"). But you'll also need to modify the ip addresses (probably 192.168.122.1 for the guest client and 0.0.0.0 for the host server).
Now you can start the server and then the client. You can switch between host and guest inputs by holding left and right control keys simultaneously. To quit press left control, right control and backspace simultaneously.
Now you can start the server and then the client. You can switch between host and guest inputs by holding left and right control keys simultaneously. To quit press left control, right control and backspace simultaneously.