Renowned virtualization platform Proxmox VE has officially launched its Arm64 edition, marking the first instance of PVE expanding beyond the x86-64 architecture to support a novel hardware platform. As announced in the official forum thread regarding Proxmox VE for 64-bit Arm, bare-metal ISO images and software repositories are now available for deployment, with enterprise-grade support accessible on demand. Crucially, this new iteration is not an experimental community release tailored for single-board computers like the Raspberry Pi; rather, it is purposefully engineered for enterprise servers and AI data centers.
Unified Lifecycle and Feature Parity
According to official Proxmox release documentation, version 9.2 for amd64 and arm64 architectures shares an identical codebase, package repository, and release lifecycle. Both editions utilize identical underlying core components, including Linux Kernel 7.0, QEMU 11.0, LXC 7.0, and ZFS 2.4. Consequently, Proxmox VE for Arm64 represents a fully integrated product within the official maintenance framework rather than a preliminary technical preview.
At the functional level, Proxmox emphasizes complete feature parity between the Arm64 edition and existing x86-64 deployments. This parity encompasses KVM virtual machines, LXC containers, the web management GUI, software-defined networking, clustering, high availability, backup capabilities, and the ZFS/Ceph storage stack. This functional equivalence remains vital for enterprise adoption, as ARM server platforms restricted to rudimentary virtualization offer limited utility in production environments.
Official Hardware Support and Limitations
Regarding hardware compatibility, Proxmox explicitly confirmed initial official support for NVIDIA Grace Hopper and Vera CPU architecture platforms. Other UEFI-compliant Armv9-A or newer server platforms receive best-effort support, while Armv8-A hardware can generally be tested but falls outside the scope of full official support.
Furthermore, single-board computers such as the Raspberry Pi are strictly unsupported. Proxmox mandates that Arm64 host systems boot via UEFI and describe hardware through ACPI. Single-board computers relying on Device Trees cannot meet these prerequisites. Therefore, Proxmox VE for Arm64 targets enterprise AI data centers rather than home lab enthusiasts.
Architectural Distinctions and Clustering Constraints
Architectural differences require Arm64 virtual machines to boot exclusively through UEFI utilizing AAVMF (Arm-built OVMF), rendering SeaBIOS unavailable. x86-specific technologies – such as AMD SEV memory encryption and Intel GVT-g vGPU – are likewise absent from the Arm64 edition. Although nodes of differing architectures can technically coexist within the same cluster, Proxmox officially discourages mixed-architecture clusters. Virtual machines can only run and live-migrate between nodes sharing identical CPU architectures.
Support Our Threat Intelligence
If you find our CVE report and cybersecurity news helpful, consider supporting our work.