Latest activity
-
HHank42 replied to the thread <span>nodename</span> showing up in front of everything.No helper scripts - fresh install of 8.4 - > upgrade to 8.4.13 (adding to an existing cluster is the goal). Hoping this helps someone else as I found the root cause and fixed my issue . To resolve the issue, I did a force (re)install of...
-
ProxmoxSecurityAdvisory replied to the thread Proxmox Backup Server - Security Advisories.Subject: PSA-2026-00010-1: "Crackarmor" apparmor vulnerabilities Advisory date: 2026-03-13 Packages: proxmox-kernel-* Details: Qualys discovered several vulnerabilities in the AppArmor LSM (Linux Security Module) code of the Linux kernel... -
ProxmoxSecurityAdvisory replied to the thread Proxmox Virtual Environment - Security Advisories.Subject: PSA-2026-00010-1: "Crackarmor" apparmor vulnerabilities Advisory date: 2026-03-13 Packages: proxmox-kernel-* Details: Qualys discovered several vulnerabilities in the AppArmor LSM (Linux Security Module) code of the Linux kernel...
-
bbgeek17 replied to the thread Proxmox + NVMe/TCP : Is LVM-thin supported and suitable for fast VM provisioning?.Hi @lxiosjao , No. I am not sure if the new tech-preview PVE9 LVM snapshot-as-volume-chain may optimize anything for you. If I recall correctly, it still require 100% space overhead reservation for snapshots/clones. Blockbridge : Ultra low... -
VictorSTS replied to the thread backup stop mode doesn't stop the VM.You need to understand how backup works. Specifically in stop mode: VM is running PVE tries to do a shutdown of the VM: If QEMU Agent is configured and running, shutdown signal is issued with it. Else, sends an ACPI signal which guest OS may or... -
WWonkyDonkey replied to the thread Deleted current kernel using dpkg - Now get Kernel Panic.Many thanks for the prompt response. However. I'm failing at the first hurdle as I get a "Read-Only Filesystem" error when I try and create /mnt/RESCUE
-
Mmws replied to the thread two node setup with local Dell R600 series storage with replication.I think my only choice is ZFS if I want replication too it seems? Wish veeam supported it already for replication instead of just backup! thanks!
-
Hhargibi replied to the thread Failing SAS Passthrough on Proxmox 9 with 8.14 kernel.Had the exact same problem since after the 6.8 kernel. Now i can finally update to 6.17 kernel :) Thanks!
-
Wwbk replied to the thread two node setup with local Dell R600 series storage with replication.If you want to use HW RAID, ZFS is off the charts. LVM is fine, especially if your current environment is on LVM as well. People love ZFS for the ease with which advanced features are available, such as checksumming, RAID, caching...
-
Bberryblast replied to the thread RTX 5080 (Blackwell GB203) VFIO Passthrough Failing on PVE 9.1 / Kernel 6.17 — Has Anyone Solved This?.I'm having the same issue sadly. I don't have a "Kernel DMA Protection Indicator" setting in my bios so that doesn't fix it either. I've tried everything to get this to work. I want to use my 5080 for streaming games with sunshine and moonlight...
-
MDann reicht es doch, den PC nur dann anzumachen, wenn du zocken oder mit künstlicher Dummheit experimentieren willst. Oder willst du was betreiben, wofür die lokale KI die ganze Zeit laufen soll? Ich persönlich finde es durchaus vernünftig...
-
bbgeek17 replied to the thread <span>nodename</span> showing up in front of everything.@Hank42, have you installed helper scripts on your system at any point? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
-
Mmikewich replied to the thread <span>nodename</span> showing up in front of everything.we were already 9.1 out of the gate so I was a bit surprised we had this issue, but mentioned above, a host rebuild fix it. We run FC storage and have a 3 node test cluster, so it didn't take long to get back into working again.
-
Mmikewich reacted to Hank42's post in the thread <span>nodename</span> showing up in front of everything with
Like.
FWIW - identical proble, but this is going form 8.4 to 8.4.13 upgrade from CLI using these steps: apt-cache policy pve-manager apt install pve-manager=8.4.13 apt dist-upgrade apt-mark hold proxmox-ve pve-manager apt dist-upgrade rebooted and... -
HHank42 replied to the thread <span>nodename</span> showing up in front of everything.FWIW - identical proble, but this is going form 8.4 to 8.4.13 upgrade from CLI using these steps: apt-cache policy pve-manager apt install pve-manager=8.4.13 apt dist-upgrade apt-mark hold proxmox-ve pve-manager apt dist-upgrade rebooted and...
-
WWonkyDonkey posted the thread Deleted current kernel using dpkg - Now get Kernel Panic in Proxmox VE: Installation and configuration.A lesson if ever one was needed NOT to do things when tired late at night. So I've stupidly got my numbers mixed up when trying to tidy up after updating Proxmox and accidentally deleted the current kernel using dpkg and unsurprisingly I now get...
-
LLBP321 posted the thread All ZFS Pools Showing as 97% Full in PVE in Proxmox VE: Installation and configuration.Hello everyone, I use Proxmox and Proxmox Backup Server. I have a single ZFS-formatted 8TB archive HDD that I use with Nextcloud that's showing 97% full, a RAID1 ZFS 8TB HDD pool that I use with PBS for backups that's showing 97% full, and a...
-
JJohannes S reacted to alexskysilk's post in the thread Ceph 20.2 Tentacle Release Available as test preview and Ceph 18.2 Reef soon to be fully EOL with Like.
I feel you. this leaves you with 2 options- 1. do not use pveceph. which you totally CAN 2. open a feature suggestion here: https://bugzilla.proxmox.com/enter_bug.cgi
-
443n12y replied to the thread OSD Segmentation faults (safe_timer).The crashed OSDs have very diffrent age, some are just a few days. But some are older then 4 years. So at first glance it seems no related with creation time or version.
-
SteveITS reacted to SleepyCircuit's post in the thread High VM-EXIT and Host CPU usage on idle with Windows Server 2025 with Like.
Here is a follow-up on my initial post. I was running out of ideas, so I've decided to let Claude code SSH connect to my production host (because why not?). Figured it might be able to shed some new light on the issue. Turns out it really did...