INFRA Signal 370
Proxmox VE Officially Expands Beyond x86 With Arm64 Support
↗
Proxmox VE now provides an official Arm64 edition that delivers the same virtualization, storage, and management features as its x86-64 counterpart.
Engineers can deploy Proxmox on Arm-based servers without relying on community ports, gaining access to the full enterprise toolset and support. This opens hardware options for workloads that benefit from Arm efficiency, such as AI training on NVIDIA Grace Hopper systems. However, the lack of cross-architecture live migration and mixed-cluster support means heterogeneous environments must be planned around uniform architecture nodes.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The Arm64 release uses the identical codebase, package repositories, release lifecycle, and documentation as the x86-64 version.
Official hardware support is limited to NVIDIA Grace Hopper and Vera processors, with best-effort coverage for other UEFI-based ARMv9-A or later servers and no support for device-tree only boards like the Raspberry Pi.
x86-specific features such as AMD SEV and Intel GVT-g are unavailable, guests must match the host architecture, and live migration or high-availability placement requires homogeneous architecture nodes.
THE READ
What the cluster adds up to.
Proxmox VE 9.2 for Arm64 is built on Debian 13.5 'Trixie' and runs the Linux kernel 7.0 by default. It includes the same versions of core components as the x86-64 release, such as QEMU 11.0, LXC 7.0, and ZFS 2.4. The web-based management interface, clustering tools, backup facilities, and Ceph integration are present unchanged. This means existing operational procedures and documentation apply directly to the Arm64 variant.
Official support targets servers that use the NVIDIA Grace Hopper Superchip or NVIDIA Vera processors, which are aimed at data-center, cloud, AI, and accelerated computing workloads. For other UEFI-based ARMv9-A or later systems, support is provided on a best-effort basis, and ARMv8-A hardware may work similarly but without guarantees. Boards that rely solely on a device tree for hardware description, such as the Raspberry Pi, are excluded from official support, though community attempts are possible outside the supported range.
Arm64 virtual machines must start via UEFI using the Arm version of OVMF (AAVMF) because SeaBIOS is not available for this architecture. Consequently, x86-specific technologies like AMD Secure Encrypted Virtualization and Intel GVT-g mediated graphics virtualization cannot be used. Guests can only run on hosts with the same CPU architecture, so an Arm64 VM requires an Arm64 node and live migration is only possible between nodes of identical architecture. Mixed-architecture clusters are not officially supported, and high-availability placement must keep guests on compatible nodes.
Moving existing x86-64 workloads to an Arm64 host cannot be done by simple transfer; the guest OS must be reinstalled or reconfigured for Arm64 after data migration via offline methods, backup/restore, or shared storage. Proxmox provides an Arm64 enterprise repository and commercial support at the same service levels as for x86-64 customers. Internal test versions of Proxmox Backup Server for Arm64 exist, with any public release timing driven by enterprise demand.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER