INFRA Signal 446
Proxmox VE now available for ARM64
Proxmox VE now provides an official ARM64 build that mirrors its x86-64 counterpart in code base, tooling and release lifecycle.
Engineers can run the same virtualization platform on ARM-based servers, extending Proxmox's feature set to newer low-power hardware while preserving existing workflows. The port requires UEFI/ACPI firmware, so many single-board computers remain unsupported. Support is guaranteed only on a best-effort basis for other ARM servers.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The ARM64 release uses the same Debian base, kernel, QEMU, LXC and ZFS components as the x86-64 version and follows the identical update schedule.
Official support is guaranteed on NVIDIA Grace Hopper and Vera platforms, with best-effort compatibility on other UEFI-based ARMv9-A or newer servers; device-tree-only boards such as Raspberry Pi are not supported.
Virtual machines must boot via UEFI (OVMF), live migration and guest execution are limited to nodes of the same architecture, and x86-only features like AMD SEV or Intel GVT-g are unavailable.
THE READ
What elseif makes of it.
The release adds an official ARM64 variant of Proxmox Virtual Environment that shares the exact code base, package repositories and update cadence with the existing x86-64 product. Engineers therefore get the same web interface, command-line tools and documentation on the new architecture. The underlying Linux distribution, kernel, hypervisor and container stack are identical to those used on Intel/AMD systems. This means existing playbooks and automation can be reused without modification.
Adopting the ARM64 build requires hardware that boots through UEFI and exposes its topology via ACPI, ruling out many single-board computers that rely only on device tree. Officially supported platforms are the NVIDIA Grace Hopper and Vera servers; other recent ARM server boards are usable on a best-effort basis. Organizations must obtain a separate subscription for ARM64 hosts, as the entitlement is not shared with x86-64 licenses. Apart from the hardware change, no new management software needs to be installed.
Several x86-only capabilities are unavailable on ARM64: virtual machines can only start via UEFI (OVMF) and SeaBIOS is not provided, AMD SEV memory encryption and Intel GVT-g mediated vGPUs have no ARM equivalents, and there is no OS-level microcode package comparable to intel-microcode or amd64-microcode. Guest workloads are confined to nodes of the same CPU architecture, so live migration cannot cross between ARM and x86 servers. Consequently, a cluster that mixes architectures will not be officially supported and may lead to unexpected behavior.
Despite these limits, day-to-day operations remain unchanged because the CLI, API and GUI are identical across architectures. Enterprise support, including access to the pve-enterprise repository, is offered for ARM64 with the same service levels as on x86-64, though the subscription must be purchased separately. Teams can therefore treat the ARM64 deployment as another homogeneous node pool within their existing Proxmox environment.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER
↗