Search results for query: lxc

...Ahnung, warum) und startet jetzt nicht mehr... Hier mal die Config: arch: amd64 cores: 4 features: nesting=1 hostname: paperless-ngx-prod-lxc memory: 8192 net0: name=eth0,bridge=vmbr0,gw=192.168.0.2,hwaddr=BC:24:11:5D:4F:CE,ip=192.168.0.208/24,type=veth onboot: 1 ostype: debian rootfs...

...für vms und https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/lxc/{vmid}/remote_migrate für container. Sprich: Gerade als Entwickler einer unabhängigen App würde ich doch dringend dazu raten keine Setups zu unterstützen, die so nicht wirklich vorgesehen und "Build to break" sind...

From what I know, Proxmox is basically Debian with KVM QEMU LXC Ceph/ZFS Corosync + Pacemaker Linux networking some sort of noVNC for console some sort of web GUI to show I would like to know if there is a guide on how to get Proxmox (or near) by install and configuring the components one by...

...zwar nicht auf 100 (da müsste ich den Container vorher löschen), aber liegt jetzt erst mal auf 104: pct restore 104 BackupNAS:backup/vzdump-lxc-100-2026_05_07-02_10_00.tar.zst --rootfs 8 --storage local-lvm 8GB Rootdisk ist für das winzige Containerchen zwar eigentlich Overkill, aber Platz...

Probier mal pvesm list BackupNAS. Ich nehme an der Pfad ist BackupNAS:backup/vzdump-lxc-103-2026_05_08-02_11_03.tar.zst aber warum raten. Vielleicht funktioniert ein richtiger SSH Client besser.

...zstd INFO: filesystem type on dumpdir is 'cifs' -using /var/tmp/vzdumptmp2704184_100 for temporary files INFO: Starting Backup of VM 100 (lxc) INFO: Backup started at 2026-05-08 02:10:13 INFO: status = running INFO: CT Name: nexa2mqtt INFO: including mount point rootfs ('/') in backup INFO...

...1.3.0 libpve-notify-perl: 9.1.2 libpve-rs-perl: 0.13.0 libpve-storage-perl: 9.1.2 libspice-server1: 0.15.2-1+b1 lvm2: 2.03.31-2+pmx1 lxc-pve: 6.0.5-4 lxcfs: 6.0.4-pve1 novnc-pve: 1.6.0-4 proxmox-backup-client: 4.2.0-1 proxmox-backup-file-restore: 4.2.0-1 proxmox-backup-restore-image: 1.0.0...

Oder halt pct restore 100 XXX:backup/vzdump-lxc-100-... --rootfs YYY --storage ZZZ Du kannst den genauen Pfad via pvesm list ... und pvesm path ... finden.

...for non-VM datasets to create snapshots by time schedule. Then, for the end users: take a look at https://github.com/bashclub/zamba-lxc-toolbox They do Samba with ZFS-snapshots which are simply visible in the Windows File Explorer as "Previous Versions". It is a Container with...

Before I waste a bunch of time on this... has anybody either succeeded in doing this in an LXC, or ("expertly") concluded that zfs snapshot automation must be done in the PVE host? I too of course would love to see Proxmox add a feature for dataset snapshot automation ( every M minutes, every H...

...noch einen anderen Server etwa raspberry hat) das umgehen, das Setup hat dunuin hier mal beschrieben: https://forum.proxmox.com/threads/pi-hole-lxc-with-gravity-sync.109881/ Das bezieht sich aber noch auf ältere Versionen von pihole, heute nimmt man nicht mehr gravity-sync sondern...

Unfortunately not. I had an extra NIC on the motherboard so I put that on passthrough for the VM which hides the problem. Problem NIC is a AQtion AQC113CS. Would love an actual fix.

Hi, the same happend to my Home PVE. The Disk is fine and working as long the VM/LXC's that depend on it are not stopped or an Snapshot/Backup happened. Failed Volume is on /dev/sda: Just as with jaytee129, /dev/sha is missing here: If i try to readd the group there is no unsused disk...

It’s simply the requirement of a network card/interface… Either a real one in bare-metal setups or virtual in a VM/LXC. Obvious that you need it, lol.

@Gnosh - I've hit this as well - specifically Tailscale traffic leaving my LXC (also via direct connection) that basically stops with kernel 7.0 - reverting to 6.17 (and no other changes) is an instant fix. No problems connecting, but if I then try transfer files or stream video, it just stops...

...changes it includes may impact PVE7. Nor upgrade, unfortunately :rolleyes: At the time proposed that too, but customer doesn't want to invest in those clusters as they are already migrating apps to a different architecture without LXC on a different cluster. That will take them time, though.

I was looking through documentation, and I've noticed that in the system requirements is requested a "dedicated nic". I have some PDM installed as LXC, for little pve cluster, and if I was in need to control a big environment I could have choose for a VM or even a single machine, and obviously a...

...Why is that package update also needed? Asking because I have two legacy PVE7.4 clusters that can't be upgraded due to dependencies with old LXC (systemd vs cgroup2 compatibility) and they won't receive that pve-container packate update. Thanks! [1]...

Can confirm Debian 13 LXC 13.1-2 and Proxmox 9.1.9 issue is still there but the fix with apt update && apt upgrade -y && apt install ifupdown -y && reboot worked

...direkt opnsense zu installieren. Ich hatte aber das Gefühl dass das zu Problemen geführt hat Dir muss im klaren sein, das Proxmox eine Virtualisierungsumgebung ist. Wenn dein Proxmox Server läuft, werden darin die anderen Maschinen wie z.B. opensense usw. in einzelnen VMs oder LXC aufgesetzt.