Proxmox VE on ARM64: What Works in a Homelab

Proxmox VE 9.2 officially supports ARM64 with its own ISO. Which hardware is supported, why Raspberry Pi and RK3588 boards are not, and what that means for a homelab.

A Proxmox VE dashboard running on a stack of Raspberry Pi and Orange Pi single-board computers.

In August 2026, Proxmox released Proxmox VE 9.2 for ARM64, its first officially supported build on a second CPU architecture. According to CNX Software and Jeff Geerling, it is built on Debian 13.5 “Trixie”, uses the same code, tools and documentation as the x86-64 version apart from architecture-specific differences, and comes with its own ISO installer. Proxmox says it is not a technology preview: it gets the same release lifecycle and support windows as x86-64.

Which hardware

  • Officially supported: NVIDIA Grace Hopper and Vera server platforms.
  • Best effort: other UEFI-based Armv9-A hardware; Armv8-A generally works as well. Ampere Altra systems have been reported working.
  • Not supported: device-tree-only single-board computers, including the Raspberry Pi. The host has to boot through UEFI and describe its hardware through ACPI.

That last point is the one that matters for most homelabs. The cheap ARM boards people own (Raspberry Pi 4/5, Orange Pi 5 and other RK3588 boards) boot with device trees. Community UEFI firmware projects exist (for example for the Pi 4, and EDK2 ports for RK3588), and people have reported getting Proxmox running that way. It’s unsupported, depends on that firmware’s quality, and can break with updates.

Installing

Use the official ARM64 ISO from the Proxmox downloads page on a UEFI machine, the same way as on x86. Don’t follow older guides that add the Proxmox repository to a Debian install on an ARM board: the bookworm (Proxmox VE 8) repository was amd64 only, so there were no ARM64 packages there.

Things to plan for

  • Guest images must be ARM64: VMs need ARM64 operating systems, and containers need arm64 images. Most popular images are multi-architecture, but check before you plan around one.
  • No live migration across architectures: a VM built for ARM64 can’t move to an x86 node, or the other way round.
  • Power and cost: efficient ARM servers exist, but the officially supported platforms are data-centre hardware. For a low-power homelab today, a small x86 mini PC is still the simpler, supported route; ARM becomes attractive as more UEFI-compliant ARM machines reach sensible prices.

Bottom line

Official ARM64 support is real and a big step for Proxmox, but it targets UEFI/ACPI servers. If your plan is a Raspberry Pi cluster, you’re in unsupported territory. If you have UEFI ARM hardware, the ARM64 ISO is the way in.

What’s Next

Frequently Asked Questions

Does Proxmox VE run on a Raspberry Pi 5 now?
Not officially. Proxmox VE for ARM64 needs hosts that boot via UEFI and describe their hardware with ACPI. Device-tree-only boards such as the Raspberry Pi are explicitly unsupported. Community UEFI firmware projects can make some boards work, entirely at your own risk.
Which ARM hardware is supported?
Officially NVIDIA Grace Hopper and Vera platforms. Other UEFI-based Armv9-A hardware (Armv8-A generally works too) is supported on a best-effort basis; Ampere Altra systems have been reported to work.
Can I mix ARM64 and x86 nodes in one cluster?
Check the Proxmox documentation before trying. Even where cluster membership works, a VM can't be live-migrated between CPU architectures, because the guest itself is built for one architecture.

Get notified when new articles and designs land:

No spam. Unsubscribe any time.

Sergej Voronko
Sergej Voronko
SAP Basis · Senior Operations Manager · Linux infrastructure engineer
About the author →

[discussion]

Comments are powered by Giscus — backed by GitHub Discussions. Sign in with GitHub to join the conversation.