[Resource Mappings] Allow wildcard VID:PID for USB-Mappings

[haertelgu]

Hi,


I was wondering if there was a way to allocate a raw USB port as a USB mapping. I use Proxmox to create an isolated development environment for embedded projects.


I know that I could just allocate a raw USB slot to a VM, but this requires logging in as the root user. I want to give other developers the option to simply use a USB port for their projects.


For example, if a developer needs another USB device in their VM, they could go to a labeled USB hub, connect to an empty port, and add that port to their VM.


Currently, this is not possible because the [VID : PID] must match the one assigned when the mapping was created.


Having the option to use a wildcard here would be useful. I understand the security risks, but the server room has access control anyway, and the server is exclusively used for embedded development.


Is there a way to achieve what I just described, or would this require the Proxmox team to implement it first?

Best Regards
Eric

(auto-corrected by a LLM)

 

[cwt]

An alternative would be an USB over LAN solution, either ootb hardware like Silex or software based (VirtualHere, Eltima, etc.). I personally use VH in many customer projects. For dongle servers, NC machines, etc. Usually a small system like an RPi is more than enough. Chained USB hubs are possible and since last year they also have a KVM solution. Within the VM you can connect to the desired USB device regardless of Proxmox.

 

[haertelgu]

i know that there are valid workarounds (also messed around with VirtualHere), but just allowing wildcard mappings would simplify things alot, and i don't see a downside of allowing that (with a appropriate warning of the implied security Risk of course).