Proxmox's official table says 2026-08 and does not give a day. What tends to fall outside the headline is that Debian 12's extended support runs to June 2028 through the usual channel, so apt will keep installing real patches on an unsupported node. What exactly freezes, how to check it, the order of the upgrade to 9.2, and why forcing it in August can be worse than being late.
Since Ceph Quincy the scheduler for BlueStore OSDs is mClock, and the work ceiling it shares out does not come from the vendor datasheet: it comes from a benchmark each OSD runs at boot. If that measurement is discarded, you are left with 315 IOPS for a spinning disk and 21,500 for a solid-state one, whatever you bought. How to check what your cluster believes, which parameters stopped having any effect, and when the drive really is the problem.
Proxmox VE's own documentation sets the ceiling: about 2 minutes of error detection and failover, and no more than 99.999% availability. What really happens when a node dies (a cold start, not a live migration), why a healthy node reboots itself 60 seconds after losing quorum, the requirements everybody skips, and when we do not deploy HA at all.
Every migration plan has a line that says "if it goes wrong, we roll back". Almost none says what you roll back to, or until when. Proxmox has shipped an ESXi import wizard since 8.2; the way back is not a button. And the window closes from three directions at once: the contract, the unpatched hypervisor, and the data delta.
On 24 and 27 June, two of the certificates Microsoft has used to sign the boot chain since 2011 expired. Not a single machine went down: Microsoft states plainly that the device keeps starting and updating normally. What stops is something else — revocations, the boot manager, early-boot mitigations — and it raises no alert at all. A third date is still open: 19 October. How to check in two minutes whether your Windows estate, your Linux servers and — this is the one nobody looks at — your virtual machines already carry the 2023 certificates.
Two Linux kernel flaws published this week break the two boundaries we take for granted: the virtual machine (Zapscape, CVE-2026-64561) and the container (SCTPhantom, CVE-2026-64564). Understanding them is the easy part. The hard part is answering whether the kernel your node actually boots already carries the fixes, because the versions in the advisory — 6.12.101, 7.1.6 — do not exist on your server: Proxmox does not use Debian's kernel. The exact proxmox-kernel versions that do close them (and why 7.0.14-9 is not enough), how to check in four commands, and who genuinely needs to hurry.
Ceph Tentacle ships Fast EC, the erasure coding performance work people had been waiting years for. And it arrives switched off: you enable it pool by pool, with one command, and the monitor then refuses to clear it — rolling back means draining and recreating the pool. On top of that, the "at least double" in the headline was measured with a 16K stripe unit, which is precisely what an existing pool cannot have. The conditions the monitor enforces, the half of the improvement frozen on the day you created the pool, what happens to the cluster when you flip it, and why three-way replication is still faster.
On 5 August Proxmox shipped the first officially supported edition of Proxmox VE 9.2 for arm64: same codebase, same repositories, same lifecycle and feature parity with x86-64. Buried in the announcement there is one sentence that decides how you design your infrastructure: guests only run on nodes matching their architecture, and live migration only works between nodes of the same architecture. What they actually shipped, what you give up crossing to Arm, why the Raspberry Pi is left out, and the five questions we ask before quoting an Arm node.
Ceph's lifecycle table puts the estimated end of life of Squid (19.2) on 19 September 2026: fifty days from today. Its replacement, Tentacle (20.2), has been stable since November and Proxmox has marked it stable since 9.2. The problem is not the jump, it is that it is not a jump: it is a sequence of three maintenance windows whose order you do not get to choose, with two details almost nobody has looked at — the mgr/zabbix module is gone, and erasure coding optimisations do not switch themselves on.
The lifecycle table in Proxmox's official documentation puts the end of life of the 8 branch in August 2026. Just over thirty days are left, and the typical reaction is to block out a weekend and jump to 9. Our stance is the opposite: there are six situations where upgrading this August is a worse idea than being late. The live-migration asymmetry that turns your rollback into a restore, why Ceph means two windows and not one, the containers with old systemd that will not start, and a realistic split of the thirty days left.
Today Proxmox Server Solutions announced it is joining the NVIDIA Mission Control ecosystem: Proxmox VE as the virtualisation and high-availability layer beneath the management services of AI factories, with engineering work for the Grace and Vera CPUs. What the announcement actually says, where Proxmox sits in that picture and where it does not, and why an announcement changes the conversation in a boardroom but changes none of the things that decide your migration.
Same fault tolerance and twice the usable space: pitched like that, erasure coding sounds obvious. We run Ceph in production and our VMs are still on 3-way replication. The space math, the write math, the recovery math and the node math — and where we do use erasure coding.
86% of VMware customers are shrinking their footprint, yet only 4% have completed a full migration. Broadcom, meanwhile, signs Standard Chartered. What the data actually says two years in, and what we would do with a renewal due in 2027.
The hardening checklist we apply to every Proxmox VE 9.2 cluster in production: 2FA, least-privilege tokens, firewall, segmented Ceph, immutable backups, and what we deliberately skip.
Proxmox welcomes Zabbix as an official Solution Provider: native API-based monitoring of clusters, nodes, VMs, LXC, storage and network. What it means and how we run it in production at everyWAN.
Broadcom has increased VMware costs by up to 1,200%. Real impact analysis, available alternatives, and step-by-step Proxmox VE migration plan for enterprises.
Real case study: migration of 512 virtual machines across 12 ESXi hosts to Proxmox VE with Ceph. 10 weeks, zero data loss, -72% cost reduction. The complete process step by step.
Objective Proxmox VE vs VMware vSphere comparison in 2026: licensing costs, features, performance measured on identical hardware, and ecosystem. Real engineer data, not marketing.
Proxmox has launched its secret weapon for enterprise-scale virtual infrastructure management: Proxmox Datacenter Manager 1.0. Discover how this first stable release revolutionizes the management of multiple Proxmox VE and Proxmox Backup Server environments.
To receive IT stories, everyWAN news and exclusive subscriber offers, sign up to our mailing list
Gestiona tus servicios de forma
ágil y 100% segura
Microsoft 365
ES 
CAT 
EN