We are pleased to share two major milestones that will help us better serve our customers and partners worldwide.
Global 24/7 enterprise support
Starting October 19, 2026, Proxmox Enterprise Support will be available around the clock, 365 days a...
Ah that was helpful, thank you.
Now that I understood what tool to use, I was able to delete the keys using ceph auth del <key> for all of the offending keys.
Now a new error has cropped up when doing the dry run:
FAIL: These keys cannot be...
Es gibt ja die virtio 0.1.302 und ich habe nicht schlechtes bisher gehört.
Also gibt es die Version auch mit meinem Mod. virtio-mod
Weiterhin enthält diese Version ein Tool, welches die IP Konfiguration exportiert und nach den nächsten Boot...
Backups work for me (see below). What does not work is VM migration (with storage) because Proxmox doesn't like SeaBIOS with an EFI disk present. It will spit up an error like this: "2026-09-12 07:48:26 [pve3] VM 124 qmp command...
Thanks for your answer. I was just a bit worried, because I always went by the rule to not over-provision RAM. Which would be the case if the host and every LXC could in theory use 50% + the RAM that's actually allocated.
It is my understanding that shim-signed is not required for mainboards that support UEFI but not Secure Boot. There are a number of popular SuperMicro mainboards, including mine, that fall in that category.
My solution was the following:
apt -s...
Hi all,
after a routine apt full-upgrade, the Raphael iGPU on a testing PVE node stopped clocking down at idle. It now sits permanently at the highest DPM state (2200 MHz instead of 600 MHz), which costs roughly 7–9 W
Idle behaviour of the iGPU...
Hi,
From the log, it may be worth verifying where the DNS zone for `webmeup.dk` is actually managed, and whether the API token/credentials used by Proxmox have access to that zone.
ok, just had this issue, maybe in a littlebit different setup - as this forum was a helpful resource in fixing, here my notes (markdown)on what I observed today:
# Proxmox vmbr0 IPv6 (SLAAC) — working config & issue notes
## TL;DR — what works...
The Issue: Based on querying QEMU Guest Agent, PVE 9, shows Total RAM usage of a running VM (as labeled in free -h ) , which is a combination of used and buff/cache.
Thus, in guests with workloads that consume all available RAM for buff/cache...
Not in the GUI, no. I checked on 4.2.5 and it is still one group at a time. The Content list is a tree (namespace, group, snapshot, file) rather than a grid with checkboxes, so there is no multi-select for a bulk action to hang off...
50% is fine. This size is just the max size, it isn't reserving 50% of ram in case you write a file to /tmp, it will use memory for files as they are written, and free the memory again when they are deleted. The size is the limit where the...
Try without the -x. Failed network shares can often cause issues like this.
Read this: https://forum.proxmox.com/threads/high-boot-disk-usage-on-proxmox-9-2-node-ext4.183879/
I don't really see the relation to docker here. Two unrelated things...
Ich finde das ganze Thema problematisch.
Das Problem fängt da an, wenn amazonses.com, mailin.fr oder andere, halbseidene Absender involviert sind. Dann empfängt man nämlich auch eine ganze Menge andere Mails nicht mehr, ohne dass der Endnutzer...
50% is fine. This size is just the max size, it isn't reserving 50% of ram in case you write a file to /tmp, it will use memory for files as they are written, and free the memory again when they are deleted. The size is the limit where the...
Es gibt ja die virtio 0.1.302 und ich habe nicht schlechtes bisher gehört.
Also gibt es die Version auch mit meinem Mod. virtio-mod
Weiterhin enthält diese Version ein Tool, welches die IP Konfiguration exportiert und nach den nächsten Boot...
50% is fine. This size is just the max size, it isn't reserving 50% of ram in case you write a file to /tmp, it will use memory for files as they are written, and free the memory again when they are deleted. The size is the limit where the...
Can you confirm proxmox-kernel-6.8.12-33 (and later, e.g. -43) also includes the companion fix for CVE-2026-46113 (upstream commit 0cb2af2ea66a), not just CVE-2026-53359?