Author: Eng. Moamen Sakr
The Problem:
If you use Fedora (or any Linux distro) as your daily driver and try to pass through a Redragon Gaming Mouse (or any composite HID gaming mouse) to a Windows VM in VMware Workstation to configure RGB, Macros, or DPI, you will likely face this stubborn error:
"Cannot connect '... Mouse' to this virtual machine. The host requires this device for input."
Because it's your primary pointing device, the Linux usbhid driver and VMware's safety mechanisms fiercely lock it and refuse to unbind it to prevent you from losing control of your host OS.
The "Traditional" Solutions (And why they suck):
* Editing .vmx files (usb.generic.allowHID="TRUE"): Often ignored by the host's strict Wayland/Systemd policies.
* Creating udev rules or restarting usbarbitrator: Overly complex, requires host reboots, and often fails.
* Buying a USB Hub or switching to KVM/QEMU: Unnecessarily expensive (good hubs cost $10+) and overly complicated just to change mouse settings.
* Windows To Go / Live USB: Costs money for a decent flash drive ($5-$10), takes time to boot, and interrupts your workflow.
The "Eng. Moamen Sakr" Bypass (Cost: $0.0 - $0.5, Time: 10 Seconds):
Instead of fighting the Linux kernel with software configurations, buying expensive hubs, or wasting time creating bootable USBs, I found a stupidly simple hardware workaround that bypasses the HID safety block completely. You don't even need to buy anything if you have an old spare mouse.
Step-by-Step:
- Plug in a secondary mouse: Grab any old, cheap, or borrowed mouse (literally a $0.5 mouse from years ago, even if half the buttons don't work, as long as it gets detected) and plug it into your laptop/PC. You now have *two* mice connected to the Linux host.
- Connect to VMware: Open your Windows VM. Go to VM -> Removable Devices -> select your Redragon Gaming Mouse -> Click Connect (Disconnect from host).
- Bypass the Prompts: Because you have a secondary mouse connected, VMware's safety check is satisfied (it knows you won't lose control of the host). It will prompt you a couple of times asking to confirm the connection.
- Approve and Save: Accept the prompts and check the box that says "Do not show this message again".
- Done! The Redragon mouse is now successfully connected to your Windows VM. Configure your Macros, DPI, and RGB on the official software and save it to the mouse's onboard memory.
The Magic (One-Time Setup):
You can now unplug the cheap secondary mouse and throw it back in the drawer.
When you shut down the VM, your Redragon mouse automatically reconnects to Fedora. The best part? The next time you open the VM, the Redragon mouse will automatically pass through *without needing the secondary mouse ever again*.
Enjoy configuring your mouse natively without fighting your OS!