Search results

Container mit folgende Kommando starten: lxc-start -n 400 -F -lDEBUG -o lxc-400.log

vielleicht "unprivileged" ist das Problem... Im Host muss aber als "/dev/ttyACM0" erscheinen.

ja, es ist bei Proxmox 7 anders (cgroup -> cgroup2): lxc.cgroup2.devices.allow: c 189:* rwm lxc.mount.entry: /dev/bus/usb/001/018 dev/bus/usb/001/018 none bind,optional,create=file https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Old_Container_and_CGroupv2

I removed the ifupdown package leftover configs, after reboot no network connectivity, all network interfaces are down. After "networking" service enable and reboot, all network interfaces are up. Maybe "networking" service not enabled by default and ifupdown2 don't working without this?

try with remove ldconfig-aux-cache: rm /var/cache/ldconfig/aux-cache;/sbin/ldconfig

lxc-start 127 20210710164511.505 DEBUG conf - conf.c:run_buffer:305 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 127 lxc pre-start produced output: directory '/hdd_data_raidz/vm_backup' does not exist please run and post the output of: pct config 127

try start with: lxc-start -n 127 -F -lDEBUG -o lxc-127.log share the "lxc-127.log" with us.

+1 to this issue! (Running VM cloning on ZFS storage: TASK ERROR: clone failed: block job (mirror) error: drive-efidisk0: 'mirror' has been cancelled) proxmox-ve: 6.4-1 (running kernel: 5.11.21-1-pve) pve-manager: 6.4-9 (running version: 6.4-9/5f5c0e3f) pve-kernel-5.11: 7.0-2~bpo10...

"Did you install something additional or not?" no, i'm not...

pfsense 2.6 / FreeBSD 12.2: # info balloon balloon: actual=3072 max_mem=3072 # qom-get /machine/peripheral/balloon0 guest-stats { "stats": { "stat-htlb-pgalloc": 18446744073709551615, "stat-swap-out": 18446744073709551615, "stat-available-memory"...

Hi George, on PVE Host: run: sysctl -w net.ipv4.ip_forward=1 for permanent change, uncomment the "net.ipv4.ip_forward=1" line in /etc/sysctl.conf Julio

My opinion, Proxmox "pressure/inflate/deflate on mem. balloon" algorithm is not "aggressiv" enough for FreeBSD. Maybe new Option (FreeBSD) in OS Type, and more "aggressive" algorithm for mem. balloon handling? pfsense 2.5.0-DEVELOPMENT (FreeBSD 12.2-STABLE): Proxmox Monitor (in my case, for...

i've tested and works for me. Test setup: Host: 4 Disk - ZFS RaidZ-2 /etc/lvm/lvm.conf: global_filter = [ "r|/dev/zd.*|", "r|/dev/mapper/pve-.*|", "r|/dev/mapper/.*-(vm|base)--[0-9]+--disk--[0-9]+|", "r|/dev/sda|", "r|/dev/sdb|", "r|/dev/sdc|", "r|/dev/sdd|", "r|/dev/sde|" ] /etc/hdparm.conf...

please edit "lvm.conf" at the host!

Is there any news?

try with this: https://forum.proxmox.com/threads/upgrade-from-5-x-to-6-x-harddrives-dont-sleep-no-more.69672/post-312634

please restart your server, the newest kernel is not yet running...

please post your pve version again (pveversion -v)

"When I run apt update and apt upgrade and apt dist-upgrade, there are no new packages available." your system is not up to date, proxmox-ve: 6.1-2 vs. proxmox-ve: 6.2-2 (11.23.2020) please check your Package Repositorys, for example Proxmox VE No-Subscription Repository...

Temporary solution: https://forum.proxmox.com/threads/bug-container-with-bind-mount-backup-error-unable-to-parse-volume-id.79334/post-351351