Proxmox VE on arm64: Where Official Support Begins and Ends

Proxmox VE’s arm64 support does not mean compatibility with every 64-bit ARM machine. The documented boundary depends on the platform, processor generation, boot firmware, and method used to describe hardware to the operating system.

Proxmox distinguishes among three broad categories:

1. Named NVIDIA platforms with official support
2. Other qualifying ARM systems supported on a best-effort basis
3. Unsupported systems, including device-tree-only boards such as Raspberry Pi

This article explains those documented boundaries. No arm64 hardware or Proxmox VE arm64 build was tested.

Requirements at a glance

The installation guide names NVIDIA Grace Hopper and NVIDIA Vera as platforms with native arm64 support. Other UEFI-based hardware with ARMv9-A or newer processors receives best-effort support (installation guide).

The roadmap uses the broader wording NVIDIA Grace and NVIDIA Vera for full official support (roadmap). The supplied documentation does not provide a model-by-model inventory of covered servers, boards, peripherals, or configurations. Confirm that a particular system falls within the named platform category rather than assuming that a related processor is sufficient.

Separate release status from hardware eligibility

The roadmap identifies Proxmox VE 9.2 as the first planned Proxmox VE release for a CPU architecture other than x86-64. The same page warns that roadmap items describe development directions and may be reprioritized (roadmap).

The installation documentation now describes native arm64 requirements, but the roadmap alone does not establish current general availability of a particular installer or deployment path. Before buying hardware, answer two separate questions:

• Does the system meet the documented hardware requirements?
• Is the required arm64 release and installation path currently available for that system?

The supplied sources describe general installation options but do not map every installer image or procedure to every eligible ARM platform.

UEFI and ACPI are both required

An eligible arm64 host must:

1. Boot through UEFI
2. Describe its hardware through ACPI

Legacy BIOS boot and device-tree-only hardware are not supported on arm64 (installation guide).

These are distinct requirements. UEFI satisfies the boot requirement, but its presence alone does not establish that the system exposes its hardware through ACPI. Nor do UEFI and ACPI automatically provide full official support: an unlisted ARMv9-A-or-newer system that meets both requirements remains in the best-effort category (roadmap).

The bootloader documentation reflects this boundary. On arm64, Proxmox VE boots only through UEFI and installs GRUB in EFI mode using the arm64-efi target. It does not use the x86 i386-pc target or a BIOS boot partition (host bootloader documentation).

Why Raspberry Pi-class hardware is excluded

A 64-bit ARM processor is not enough. Proxmox explicitly excludes device-tree-only single-board computers and names Raspberry Pi as an example (roadmap).

Consequently, these statements are not equivalent:

• The board has an arm64 processor.
• Linux can run on the board.
• The board provides some form of UEFI.
• The board meets Proxmox VE’s documented arm64 requirements.

The relevant test is whether the complete system falls within the documented platform, processor, UEFI, and ACPI boundaries. Community methods and unofficial ports are outside this assessment and do not place a board in Proxmox’s documented official-support category.

Which familiar capabilities remain?

Proxmox says the arm64 build shares its code base, package repositories, and release lifecycle with the x86-64 build. It also describes configuration, tooling, and documentation as identical except for architecture-specific differences (roadmap).

Combined with Proxmox’s general feature documentation, that indicates the familiar management model remains relevant on arm64:

• KVM virtual machines
• LXC containers
• The web management interface
• Command-line tools
• The REST API

Proxmox documents KVM and LXC as its integrated virtualization technologies and says management functionality is available through the web interface, CLI, and REST API (features).

This is a documentation-based conclusion, not verification of every operation. The supplied sources do not establish compatibility with every arm64 guest operating system, image, peripheral, storage controller, or accelerator.

Architecture-specific exceptions

Shared code and tooling do not mean complete feature parity. Proxmox explicitly names several x86-specific capabilities that are unavailable on arm64:

• SeaBIOS for virtual machines
• AMD SEV
• Intel GVT-g

The roadmap also says S3/S4 ACPI power states and Hyper-V enlightenments are disabled for ARM-based virtual machines (roadmap). These are examples rather than a guaranteed exhaustive list: the documentation says unavailable features include them.

Mixed-architecture cluster boundaries

A Proxmox VE cluster may contain both x86-64 and arm64 nodes, but guest execution and live migration remain architecture-specific.

A virtual machine or container can run only on a node matching the guest’s architecture. Live migration is also limited to nodes of the same architecture (installation guide).

In practical terms:

• An arm64 guest can run on an arm64 node.
• An x86-64 guest can run on an x86-64 node.
• A guest cannot live-migrate across the x86-64/arm64 boundary.
• Moving guest data to another node does not make that guest runnable on a different CPU architecture.

An ARM node can therefore participate in a mixed cluster, but it is not a drop-in destination for existing x86-64 guests.

Installation context

Proxmox generally documents two installation approaches: complete Debian-based Proxmox VE installation media, or installation on top of an existing Debian system. The Debian route is recommended only for advanced users because it requires detailed Proxmox VE knowledge (installation guide).

Those general approaches do not prove that every image or procedure is available for every eligible arm64 platform. Confirm the documented installation path for the specific system before purchase.

The decision rule

Choose the official-support category only for a named NVIDIA platform that also satisfies the required UEFI and ACPI environment.

Treat an unlisted system as best-effort only if it has an ARMv9-A-or-newer processor, boots through UEFI, and describes its hardware through ACPI.

Device-tree-only systems, legacy-boot machines, and unlisted systems below the documented ARMv9-A threshold fall outside the stated boundary. “arm64 support” therefore should not be read as support for Raspberry Pi-class boards—or for every ARM server.

Sources and further reading

• https://pve.proxmox.com/pve-docs/chapter-pve-installation.html
• https://pve.proxmox.com/wiki/Roadmap
• https://pve.proxmox.com/wiki/Host_Bootloader
• https://www.proxmox.com/en/products/proxmox-virtual-environment/features