After the latest Kernel-Upgrade PSA-2026-00019-2: "DirtyFrag" Local Privilege Escalation on some nodes LXC containers don't start. The reason is, that /run/pve is missing. After creating /run/pve manually the container do start just fine.
Many thanks for replying! From 8.xxx to 9. I tried a rollback to the old kernel 6.8.12-22 (proxmox-boot-tool kernel add) but automatically returns to -23. This my NIC situation (in attach).
From what to what did you upgrade?
If you upgraded kernels there are some posts in https://forum.proxmox.com/threads/opt-in-linux-7-0-kernel-for-proxmox-ve-9-available-on-test-and-no-subscription.182328/page-6#post-851777
If you pin the prior...
Hello to All!
As per the title, I performed the dist update for my node (single point to failure) and unfortunately the network interface stopped working. Searching the forum, I noticed several threads about this and tried various suggested...
from what I have seen the one of them was in a raid, which I destroyed.
each disk at each reboot has been cleaned using the tutorial sgdisk --zap-all $DISK
and as I said nothing appears on the zfs or zpool command.
the tutorian is the official...
Those disks were used earlier? In a "bpool"?
I did not read read the tutorial you've mentioned; you may erase them completely by something like "dd if=/dev/null of=/dev/disktobeerased bs=1M state=progress" or read man zpool-labelclear
I kinda was wondering now why does modesetting have a priority over actual nvidia drivers especially during boot via gpu pass thru, so therefore did s a quick search turns out that it might be driver issues and modesetting is currently disabled...
first i dont think it matters because proxmox has their own efi cert, and you could turn off secure boot, but process for me was below if you want to try:
i have some old dell workstations for a lab and this was the process to get the 2023 cert...
Probably: yes.
If I remember correctly removing a snapshot means to integrate the modified blocks (since the point in time when the snapshot was taken) into one single file. That's plain and simple a slow operation. Problems like like this...
I was eventually able to solve this, just wrote this post a day to early :D. The issue is indeed related to PCIe power management. The VM boots on the most recent kernel with pcie_port_pm=off added to my kernel commandline.
Ganz klar.
Darum mein genereller Verweis aufs Inet um sich umfassend selbst zu informieren, bevor man anfängt zu Fuß nach einem von mir angeführtem Kochrezept am Bootmechanismus rumzufummeln.
So war ich mir z.B. nicht sicher, ob man auch ein...
Ganz klar.
Darum mein genereller Verweis aufs Inet um sich umfassend selbst zu informieren, bevor man anfängt zu Fuß nach einem von mir angeführtem Kochrezept am Bootmechanismus rumzufummeln.
So war ich mir z.B. nicht sicher, ob man auch ein...
I had the problem for a very long time. At each reboot I had to ("storage2" is my lvm volume) :
systemctl stop pvedaemon pvestatd
lvchange -an storage2/storage2_tmeta
lvchange -an storage2/storage2_tdata
lvchange -ay storage2/storage2
wait a few...
Hi team,
I have some problems about that installation of zfs on debian 13 on a virgin dedicated server before to load up aftrer that proxmox.
After the step
zpool create \
-o ashift=12 \
-o autotrim=on \
-o compatibility=grub2 \...
Hi, thanks for that, I actually followed this guide within 20 mins of my post and for first time had a working windows passthru, so nice one ;) wondering if this also works for vgpu?