Device passthrought on LXC

wolframio

Member
Dec 15, 2021
73
12
13
42
why adding a "Device passthrough" in LXC is not "so intuitive" as it is when one does it for a VM??

Thanks!
 
Hi,

on what version of Proxmox VE are you? Since 8.2, this is natively supported via the web interface, via CLI/API it has been since 8.1.

In the web interface, there should be a entry Device Passthrough when clicking on Resources > Add.
 
Hi,

on what version of Proxmox VE are you? Since 8.2, this is natively supported via the web interface, via CLI/API it has been since 8.1.

In the web interface, there should be a entry Device Passthrough when clicking on Resources > Add.
Thanks for the reply... To be clear, in a VM i can do a USB passthrought adding the device just selecting it from a list... For the LXC you have to enter the path of the device (/dev/xxx).
 
To be clear, in a VM i can do a USB passthrought adding the device just selecting it from a list... For the LXC you have to enter the path of the device (/dev/xxx).
That is simply due to the major difference how VMs and CTs work and expected to work like that.

For VMs, the device is passed through as a whole, e.g. the operating system has to load its own drivers etc.
For CTs, the device drivers are loaded by the (hypervisor) host, these then create certain device interface (character) files, which then can be passed to a CT.
 
That is simply due to the major difference how VMs and CTs work and expected to work like that.

For VMs, the device is passed through as a whole, e.g. the operating system has to load its own drivers etc.
For CTs, the device drivers are loaded by the (hypervisor) host, these then create certain device interface (character) files, which then can be passed to a CT.
Is it possible that instead of the wizard asking for the "path" of the device to be passed through, it asks what type of device you want to add (storage, USB port, PCI, etc.) and displays a list of devices connected to the host?

The actual way (where you have to set the device path) can be an "advanced option".

Thanks!
 
I agree, it should be easier. I don't find any step by step guide which explain how to get a device path. I want to get the device path of my Skyconnect to pass it to my LXC container to run Zigbee2mqtt and I'm not able to find what's the right path for Skyconnect
 
I agree, it should be easier. I don't find any step by step guide which explain how to get a device path. I want to get the device path of my Skyconnect to pass it to my LXC container to run Zigbee2mqtt and I'm not able to find what's the right path for Skyconnect
same, i cant find the path of many of my dell R420 server...