gistfile1.txt
1. Plug USB device |
root@proxmox01:~# lsusb |
[...] |
Bus 004 Device 005: ID 0658:0200 Sigma Designs, Inc. |
[...] |
2. Take a look of device |
root@proxmox01:~# ls -l /dev/bus/usb/004/005 |
crw-rw-r-- 1 root root 189, 388 Oct 25 16:19 /dev/bus/usb/004/005 |
Take note of ID (example: 189, 388) |
3. Edit lxc configuration |
root@proxmox01:~# nano /etc/pve/nodes/proxmox01/lxc/101.conf |
lxc.cgroup.devices.allow: c 189:388 rwm |
lxc.mount.entry: /dev/bus/usb/004/005 dev/bus/usb/004/005 none bind,optional,create=file |
commented Jun 21, 2018
A little bit more detailed version of the same:
# pct stop 102
# cat /var/log/lxc/102.log
5. Now, by taking the Bus and Device from the previous output.
# pct start 102
# cat /var/log/lxc/102.log |
R/Proxmox: A place to talk about Proxmox. However, if you are doing GPU passthrough, you might be out of luck, at least for now. Many new BIOS (both on X470 and X570). Add a serial port on 0. Change Display to Serial terminal 0. With this we have a template we can edit in console. Note: I am aware that passthrough is an experimental feature in Proxmox VE and that some purist will not like the FREENAS running in a VM. But trying to make a all in one test system ala Patrick. Following this I managed to passthrough one device successfully: Pci passthrough - Proxmox VE But as soon as I add a second device the VM will not start?
commented Jan 10, 2019
Hi, would you mind adding the source for the gistfile1.txt ? Thanks. |
commented Jan 14, 2019
And how exactly do we access the USB? After these steps, I don't see anything using fdisk -l in order to mount it to a directory. |
commented Apr 21, 2019
i followed the instructions above and my will bind with the CT just fine. But if I happen to shutdown or restart the Host for any reason the device number will change to something different. Then I need to edit the 'conf' file with the new device number and also allow permission to the Host with 'chmod o+rw /dev/ttyACM0' again to get it working. Is this normal for this to happen? Wonder if a cron job could be done to update the device ID on a restart of the Host to solve this? |
commented Aug 25, 2019
Hey, I did it little bit different way and it's working with persistent path using udev rules... On Proxmox: Get USB idProduct and idVendor: Create udev rule: Reload and trigger udev: Get cgroup config: Update your LXC config: On your LXC container: In my case I'm using this modem with smstools, so in config I pointed smstools to /dev/sms. It works like a charm ;-) |
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment