Search results for query: lxc

...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.

...on the node (once transferred by FTP, needing a separate way to access here - https://forum.proxmox.com/threads/how-to-connect-by-ftp-to-a-ubuntu-lxc.57686/) Installed Drivers for GPU: https://www.nvidia.com/en-us/drivers/ chmod +x NVIDIA-Linux-x86_64-595.58.03.run sudo...

...INFO: Error: no password input mechanism available INFO: cleanup temporary 'vzdump' snapshot ERROR: Backup of VM 25021 failed - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup '--crypt-mode=encrypt' '--keyfd=15'...

...behave like a normal click (download / launch behavior), without opening an extra useless browser tab 3. Scope This would be useful for: - VMs - LXC containers - node shell Why this would help: A lot of admins work with many guests and many consoles at the same time. Managing them as...

...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 openvswitch-switch: 3.5.0-1+b1 proxmox-backup-client: 4.2.0-1 proxmox-backup-file-restore: 4.2.0-1...

...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...

please open a new thread and include: - pveversion -v - container config - pct start XXX --debug on the working and non-working kernel versions - journal for both container starts

...versus ifupdown2? What are you trying to achieve? If everything works for you you don't need to change anything. If however you have some network issues like the one described earlier in the thread it would make sense to change the lxc installed from the old template to match the newer one.

You can move back to the prior kernel (and keep on kernel 6.x) by doing this (this is from memory though, so be careful with it): 1. Create the APT preferences file (/etc/apt/preferences.d/proxmox-default-kernel) which instructs apt to keep on the 6x series kernel: Package...

I have LXCs from using standard proxmox templates: debian-13-standard_13.1-1_amd64.tar.zst and debian-13-standard_13.1-2_amd64.tar.zst. Based on output from `apt list --installed | cat`, I see: debian-13-standard_13.1-1_amd64.tar.zst LXC has: ifupdown/stable,now 0.8.44+deb13u1 amd64 [installed]...

...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...