Search results

it does !

Thanks, we will see if lxc-pve: 5.0.2-2 does the job ;-)

proxmox-ve: 7.3-1 (running kernel: 5.15.85-1-pve) pve-manager: 7.3-6 (running version: 7.3-6/723bb6ec) pve-kernel-helper: 7.3-4 pve-kernel-5.15: 7.3-2 pve-kernel-5.13: 7.1-9 pve-kernel-5.15.85-1-pve: 5.15.85-1 pve-kernel-5.15.83-1-pve: 5.15.83-1 pve-kernel-5.15.64-1-pve: 5.15.64-1...

Hey, does it still work for you - here the problem comes back again after rebooting the host. I need to delete the folder again day by day... Any ideas how to fix it sustainably ?

what also seem to work is to delete the old file in

Hi, I did a clone and it worked for a while - after 2 days the error came back, on the cloned LXC. Is there a stable solution - workaround is only short term solution. load_apparmor_profile: 979 Invalid argument - Failed to mmap old profile from...

sorry - just saw it. I guess that is the normal behavior

Hi and sorry for the stupip question: the temp dir, needs to be on PVE host, or on the NFS-Server?? what is needed 775? I can't backup my unprivileged containers anymore .. INFO: creating vzdump archive '/mnt/pve/TrueNAS/dump/vzdump-lxc-103-2022_04_21-10_15_09.tar.zst' INFO: tar...

okay, after quick search - I needed to exted the fs (of course) so: ... resize2fs /dev/mapper/pve-root done

okay, but still need a hint I did the deletion of the "local-lvm" by using: ... lvremove pve/data also resized the lvm by using: .... lvextend -L+8G pve/root so it looks like expected: ... LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert ... root pve...

what? edit: from the machine that want to join: pvecm add <target ip> -link0 <source ip> follow cli commands to identify incl OTP https://pve.proxmox.com/pve-docs/pvecm.1.html

from 7.1-8 you may want to use cgroup2 => lxc.cgroup2.devices.allow: c 166:* rwm

Ich hatte nochmals Editiert, da waren sie weg. Und ich habe nochmal geschrieben, usw. ;-) Danke Euch, für die Mühe und Hilfe!

Das wars! Tausenddank !!! Also lxc.cgroup2.devices.allow: c 166:* rwm

Hi, auch wenn es schon x-mal beschrieben wurde, ich habe Probleme meinen Zwave-USB-Stick im LXC anzusprechen. Das Blöde: vor 7.1-8 lief der gleiche Stick auf dem selben Host im selben Container jahrelang... nach dem Upgrade, kann der durchgereichte Serial-Port nicht mehr geöffnet werden...

Hi, auch wenn es schon x-mal beschrieben wurde, ich habe Probleme meinen Zwave-USB-Stick im LXC anzusprechen. Das Blöde: vor 7.1-8 lief der gleiche Stick auf dem selben Host im selben Container jahrelang... nach dem Upgrade, kann der durchgereichte Serial-Port nicht mehr geöffnet werden...

what do I need to be sure that the stick is mounted to the lxc correctly? the mounted device in lxc looks like: crw-rw---- 1 100000 100020 166, 0 Jan 5 10:11 /dev/ttyACM0 (By the way I changed the Group in udev rule to 100020 to refer the same as the crated folder is assigned to) anyway...

Wow, much appreciated ! Will work trough ! What proxmox version do you running? and finally, did you see the device under /dev/serial/by-id/ in the lxc?

Hallo Jürgen, habe das gleiche Setup, nach dem letzten Upgrade auf proxmox 7.1-8, sehe ich meinen Zwave-Stick nicht mehr, vorher lief das in gleicher Konstellation jahrelang. Auch die udev-Regeln vom drozmotix.github - Post bringen nichts. Eine Verständnisfrage vorab: siehst du den Conbee im...

Hi, I have exactly the same issue as TCS, but with a zwave stick. The stick runs for years on buster / proxmox 6.x. After the upgrade to 7.1-8 it doesn't work anymore - target container is the same as before. I changed to 100000:100020 as you mentioned but even 777 for /dev/ttyACM0 and...