Search results

I tried to start from the beginning: I plug the key: [253457.618475] usb 1-3.1: new full-speed USB device number 55 using xhci_hcd [253457.758345] usb 1-3.1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 4.00 [253457.758359] usb 1-3.1: New USB device strings: Mfr=1, Product=2...

Thanks for your time. In my case only the serial will make the difference: root@pve:/mnt# udevadm info --name=/dev/bus/usb/001/049 --attribute-walk Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all...

Ok, I got it: on my CTX: My script try to open the device but I got an error: . It works with a VM hosted on Proxmox. root@nad:/dev/bus/usb/001# python3 /root/nad-rs232-rest/nad-rs232-rest.py 2025-10-08 10:14:15,727 - INFO - Starting mqtt thread 2025-10-08 10:14:15,730 - DEBUG - [MQTT]...

sorry, I am lost. My objective is to have my USB device attached to my container. So for this, we can not use the UI because only for VM. We need to custom the /etc/pve/lxc/109.conf right ?

Thanks for the prompt reply: so I understand that the path must be /dev/xxx but I don't know it as it is not configured yet in the CTX till the start of the CTX ? e

Hello, Here below my conf of my ctx: root@pve:~# cat /etc/pve/lxc/109.conf #lxc.cgroup.devices.allow%3A c 189%3A43 rwm #lxc.mount.entry%3A /dev/bus/usb/001/043 dev/ttyUSB1 none bind,optional,create=file arch: amd64 cores: 1 features: nesting=1 hostname: nad memory: 512 net0...

you are right, thx a lot

Hello. I Have Proxmox 8.4 and I tried to find my backup config file: root@pve:~# root@pve:~# cat /etc/pve/vzdump.cron # cluster wide vzdump cron schedule # Automatically generated file - do not edit PATH="/usr/sbin:/usr/bin:/sbin:/bin" root@pve:~# But where is my below conf so : Thanks...

it works with that: /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on iommu=pt pcie_aspm=off pcie_port_pm=off"

for people who may have the samie issue, it works with that: /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on iommu=pt pcie_aspm=off pcie_port_pm=off" /etc/modprobe.d/vfio.conf options vfio-pci ids=10de:10fa,10de:1f82 disable_vga=1 /etc/modules vfio vfio_iommu_type1 vfio_pci...

I've seen that for this case vendor-reset is needed. My kernel, 6.14.8-3-bpo12-pve doesn't have the vendor-reset compatible?

It sounds better: [ 6042.826109] vfio-pci 0000:01:00.0: vgaarb: deactivate vga console [ 6042.826121] vfio-pci 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem [ 6044.812982] vfio-pci 0000:01:00.0: not ready 1023ms after resume; waiting [ 6045.895526]...

Thanks I can remove it. So even with kernel 6.14, I have to modify /proc/cmdline even if I already edit grub as below: root@pve:/mnt/diskint# cat /etc/default/grub # If you change this file or any /etc/default/grub.d/*.cfg file, # run 'update-grub' afterwards to update /boot/grub/grub.cfg. #...

I've been told that if you boot with efi don't need to fill /proc/cmdline ? since pve 8.0 :-/ root@pve:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.14.8-2-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on root@pve:~#

Yes, I've done but it seems ok:

Thanks for your quick reply. When I started the VM, and type root@pve:~# lspci -nnks 01:00 proxmox stucks and not accessible anymore even by ICMP requests

you re right my mistake. How can we see that it is load by vfio ?

Very good question I have made a mistake, now: root@pve:~# cat /etc/modules # /etc/modules is obsolete and has been replaced by /etc/modules-load.d/. # Please see modules-load.d(5) and modprobe.d(5) for details. # # Updating this file still works, but it is undocumented and unsupported. vfio...

Thanks @Impact Yes I did: root@pve:~# update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-6.14.8-2-pve Running hook script 'zz-proxmox-boot'.. Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace.. No /etc/kernel/proxmox-boot-uuids found...

Hello. I did a fresh install of PVE 9.0.1 and tried to make a passthrough of the GTX1650: root@pve:~# lspci -nnk -s 01:00.0 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) Subsystem: Gigabyte Technology Co., Ltd Device...