On August 5, 2026, Proxmox Server Solutions GmbH announced that Proxmox Virtual Environment officially supports 64-bit Arm (arm64/aarch64) hardware. Until now, Proxmox VE only ran on x86-64. This is the first time in the project’s history that it officially targets a second CPU architecture, according to the Proxmox press release and a forum announcement posted by CTO Thomas Lamprecht.
What actually shipped
Proxmox VE 9.2 for arm64 isn’t a side project or a preview build. Per Lamprecht’s post, it shares the same code base, package repositories, and release lifecycle as the x86-64 version. It’s built on Debian 13.5 "Trixie" with Linux kernel 7.0 as the default, and it runs the same component versions on both architectures: QEMU 11.0, LXC 7.0, and ZFS 2.4. Configuration and documentation carry over directly, aside from a short list of hardware differences covered below.
Proxmox also says ZFS and Ceph, the two storage stacks most self-hosters care about, went through full validation on arm64 and now perform the same way they do on x86-64.
The hardware question
This is the part worth reading closely before getting excited about running Proxmox on whatever Arm board is sitting in a drawer.
Full, guaranteed support on day one applies to two platforms: NVIDIA Grace Hopper and NVIDIA Vera. Both are server chips built for AI training and inference, not homelab gear. Proxmox developed and tested this port directly on Grace Hopper Superchip systems, working with NVIDIA and Supermicro, and says it’s already running in production on some enterprise deployments.
Everything else falls under "best-effort," which is Proxmox’s own term for hardware that generally works but isn’t guaranteed:
- Other UEFI-based Armv9-A server hardware, and most Armv8-A hardware
- Any host that boots through UEFI and exposes ACPI
One thing is ruled out entirely: device-tree-only single-board computers. Proxmox names the Raspberry Pi specifically as unsupported. So this announcement is not an "install Proxmox on your Pi cluster" moment. Blogger Jeff Geerling tested the release on an Ampere Altra Dev Platform, a UEFI-capable Arm server board, and reported a clean install through the standard graphical installer. That’s the realistic profile of hardware this actually targets right now: enterprise-grade Arm servers, not consumer single-board computers.
Differences from the x86-64 build
A handful of things work differently on arm64:
- Virtual machines boot through UEFI only, using the Arm build of OVMF (AAVMF). SeaBIOS doesn’t exist on this architecture.
- AMD SEV memory encryption and Intel GVT-g vGPU passthrough remain x86-only.
- There’s no OS-level microcode package, since arm64 has no equivalent to intel-microcode or amd64-microcode.
- Guests only run on nodes matching their own architecture, and live migration only works between nodes of the same architecture. Mixing x86-64 and arm64 nodes in one cluster isn’t technically blocked, but Proxmox doesn’t support it.
Getting it and getting support
The arm64 build is available now, either as a bare-metal ISO or through the same package repositories used for x86-64. The pve-enterprise repository is available on arm64 too, and Proxmox says enterprise support contracts can be arranged on request, though arm64 subscriptions are sold separately from x86-64 ones. According to the forum FAQ, other Proxmox products, including Proxmox Backup Server, already have internal arm64 test builds. Which ones actually ship depends on how much enterprise customers ask for them.
What this means if you run a homelab
If your Proxmox box is an x86-64 mini PC or an old office tower, nothing about your setup changes. This release doesn’t touch that hardware, and it isn’t meant to.
What it does is open a real, supported path for Arm server hardware that didn’t exist before, and Proxmox says it’s working with other server vendors to grow that list beyond Grace Hopper and Vera over time. Whether that eventually reaches more accessible Arm boards is an open question the company hasn’t answered yet.
For background on how Proxmox got to this point, see the history of Proxmox VE. And if you’re weighing a hypervisor against a dedicated NAS for your own build, Proxmox vs. TrueNAS covers the hardware and passthrough decisions that matter most.