Proxmox VE Officially Supports Arm64: Virtualization Moves to ARM

Proxmox VE Officially Supports Arm64: Virtualization Moves to ARM

Data centers are wrestling with energy bills, and ARM has become the fastest growing architecture in the server world. But the virtualization layer stayed tied to x86 for years. On August 5, 2026, Proxmox broke that wall: Proxmox Virtual Environment (VE) 9.2 shipped with its first official Arm64 edition. Here are the details of the announcement, the supported hardware, the architectural differences, and the community's first reactions.

The Rise of ARM Servers and the Gap That Just Closed

Over the past five years, ARM-based servers positioned themselves as a serious alternative to x86. AWS's Graviton line, Ampere's Altra processors, and NVIDIA's Grace architecture turned the heads of cloud providers and data center operators. The reason is not just energy savings; running far more cores in the same power budget, high memory bandwidth, and an increasingly mature software ecosystem all play a part.

The missing piece was an enterprise-grade virtualization layer for that hardware. In the open source world, Proxmox VE runs on more than 2 million hosts and is one of the most widespread platforms around. The system unifies KVM, LXC, ZFS, and Ceph behind a single interface, yet until now it officially supported only x86-64. On the ARM side, you were stuck with community forks or the closed solutions of big cloud providers. This announcement closes that gap.

How Did Proxmox Get Here?

To fully understand this announcement, some background on Proxmox helps. Proxmox Server Solutions was founded in Vienna in 2005. The company's product philosophy was clear from the start: open source server software, vendor independent, backed by subscription support. Since its first stable release in 2008, Proxmox VE grew as a cost-free alternative to commercial hypervisors by combining KVM-based virtual machines and LXC containers in a single panel.

Today the platform runs on more than 2 million hosts worldwide, with over 225,000 community members and 3,000 integration partners. That scale turned Proxmox into a platform considered not only by homelab enthusiasts but also by regulated industries and public clouds. CTO Thomas Lamprecht and COO Tim Marx are the two names fronting the announcement. Both make the same point: ARM support is not a side project, it is the main product ported to a second architecture.

Proxmox VE 9.2 Arm64: What Changed?

According to the official announcement, the Arm64 edition shares the same code base, package repositories, and release lifecycle as its x86-64 counterpart. This is not a separate project; it is the same Proxmox VE ported to a second architecture. The release is built on Debian 13.5 "Trixie" with Linux kernel 7.0 as the stable default. QEMU 11.0, LXC 7.0, and ZFS 2.4 ship in identical versions to the x86-64 builds. Internal test builds for Proxmox Backup Server and other products are ready as well; enterprise demand will set their priority.

The most critical point is full feature parity. KVM virtual machines, LXC containers, software-defined networking, high-availability clustering, backup, and the Ceph storage stack all work on ARM exactly as they do on x86. The Proxmox team explicitly notes that ZFS and Ceph were tuned to deliver the same performance, reliability, and feature parity as existing x86 deployments. That is a clear answer to anyone who thought of the ARM edition as an experimental side project.

Supported Hardware: Grace, Vera, and the Best-Effort World

The first release has two fully supported platforms: NVIDIA Grace Hopper and NVIDIA Vera. Both architectures target demanding data center, cloud, accelerated computing, and AI training and inference workloads. Proxmox engineers ran the port in close collaboration with NVIDIA and Supermicro; joint validation on Grace Hopper Superchip systems means the platform is already operating in production environments from day one.

For other hardware, support is best-effort. UEFI-based ARMv9-A or newer servers generally work, and ARMv8-A systems are mostly supported too. The key requirement: the host must boot through UEFI and describe its hardware through ACPI. Device-tree single-board computers, meaning Raspberry Pi and similar boards, are not officially supported.

That restriction did not stop the community. Jeff Geerling called the installation on his 128-core Ampere Altra Max system a breeze. On the forums, users got Proxmox running on Raspberry Pi 4 and Pi 5 using UEFI firmware projects such as pftf/RPi4 and rpi5-uefi. Official support is absent, but the architecture does not close the door on determined users.

Architectural Differences: How Virtualization Works on ARM

The Proxmox team honestly documented the parts that did not port over one-to-one. These details matter:

• Virtual machines always boot through UEFI. The ARM build uses AAVMF, the ARM port of OVMF; the SeaBIOS option available on x86 does not exist on ARM.
• Some security and graphics features are x86-only. AMD SEV memory encryption and Intel GVT-g mediated vGPU sharing are absent from the ARM edition.
• No microcode package. Operating-system-level CPU microcode updates like intel-microcode and amd64-microcode are not needed on ARM.
• Guests are bound to their architecture. A guest only runs on nodes matching its architecture, and live migration is possible only between nodes of the same architecture.
• Mixed-architecture clusters are not officially supported. Although not technically blocked, mixing x86 and ARM nodes in one cluster is not recommended. To move an existing guest to ARM, you transfer the data through backup and restore or shared storage, then reinstall or reconfigure the guest for the new architecture.

These differences reflect the reality of the ARM ecosystem rather than a list of limitations. The firmware and security layers that accumulated on x86 over decades simply are not that layered on ARM yet. Proxmox documenting them transparently is the right move for enterprise users who do not want surprises.

The NVIDIA Collaboration and AI Factories

This announcement is the continuation of a partnership revealed on July 28. Proxmox VE joined the NVIDIA Mission Control ecosystem to manage the infrastructure layer of AI factories. NVIDIA Mission Control handles developer workload scheduling, orchestration, and autonomous recovery for AI workloads on Blackwell and Vera Rubin platforms; Proxmox VE serves as the virtualization layer beneath that system. For teams building local AI infrastructure in enterprise environments, this collaboration shows how far an open source base can go.

In other words, Arm64 support is not a gesture to homelab enthusiasts; it is part of NVIDIA's next-generation data center strategy. Day-one support for Grace and Vera combines NVIDIA's upstream kernel contributions with the enterprise reliability reputation Proxmox has built over the years. Tim Marx's quote from the announcement sums it up: customers expect the same mission-critical stability on Arm64 that they rely on with x86, and Proxmox is working to deliver it.

x86 vs ARM: A Changing Paradigm

This announcement shifts the equations of the virtualization world too. For years, the dilemma was "ARM means energy savings, x86 means performance." NVIDIA Grace, with its 72 ARM cores and up to 480 GB of LPDDR5X memory, blurs that line. Most AI workloads already run on GPUs; the CPU side mostly manages data flow. ARM's high core density and memory bandwidth fit that workload profile perfectly.

The software side is completing the chain as well. Ubuntu, Debian, and other major distributions have treated ARM as a first-class citizen for years. On the storage front, TrueNAS formalized its ARM support last year. With Proxmox joining the picture, ARM server owners no longer have to rely on a "roll your own" approach. There is now an enterprise-supported platform with regular updates, backup, and clustering built in. We saw the signals of this shift in our earlier breakdown of NVIDIA's ARM-based superchip lineup.

Of course, x86 still has areas where it is unmatched: the widest software compatibility, a mature firmware ecosystem, and decades of operational experience. Even as ARM's share grows, the transition is not expected to be an all-or-nothing affair. Mixed data centers that pick the architecture per workload are a far more likely future.

What the Community Says: ARM in the Homelab

The liveliest reactions came from the homelab community. Users who spent years running Proxmox on ARM mini PCs through forks and patches welcomed the official ISO with open arms. In Jeff Geerling's Ampere Altra Max test, installation was smooth; the only hiccup was a VM crash during Ubuntu 24.04 setup on his ARMv8 system, which he reported on the forums. That is a real reflection of the "ARMv9 fully supported, ARMv8 best-effort" policy.

The Raspberry Pi side is interesting too. Official support is absent, but users managed to run Proxmox on Pi 4 and Pi 5 with UEFI firmware projects. One user shared a screenshot of pve-manager 9.2.9 with kernel 7.0.14 running on a 4-core Cortex-A72 Pi 4. Another wrote that they migrated their test lab from the aging Raspberry Pi OS based pxvirt repository to official Proxmox. "Not official but it works" has never been more true in the ARM community.

Small form factor ARM devices are drawing attention as well: the Minisforum MS-R1, the Radxa Orion O6, and Framework's ARM mainboard are natural candidates for spreading this release through the homelab. The audience of these energy-efficient boxes is exactly the crowd that wants to cut the power bill of 24/7 servers. Anyone interested in efficient edge computing, such as running small language models, can now combine virtualization and model serving on the same hardware.

Installation and Getting Started

For those who want to try it, the process is no different from x86. You grab the Arm64 ISO from the Proxmox download page and flash it to a USB stick; the graphical installer walks you through disk partitioning and network configuration just the same. If you have a UEFI/ACPI-capable ARM server, installation completes in one pass, as it did in Jeff Geerling's experience. If you already run Debian 13 "Trixie" on an ARM system, you can also install Proxmox VE on top of the existing Debian setup using the same procedure as on x86.

The first task after installation is switching to the enterprise repository or using the free no-subscription repository. The pve-enterprise repository is available for Arm64; the no-subscription repository works like it does on x86 for those without a subscription. On the guest side, you can import Ubuntu, Debian, and other ARM images, and move existing qcow2 images over shared storage. One community member reported importing existing ARM VM images into Proxmox on a Minisforum MS-R1 and running them without issues.

Who Benefits From This Release?

Who does this actually matter to? First, organizations planning to move to ARM-based infrastructure. As cloud providers push Graviton and Grace instance types, companies that want similar efficiency in their own data centers now have a legitimate virtualization choice. AI teams investing in NVIDIA hardware no longer have to ask "which architecture is supported" when picking a hypervisor.

The second group is homelab users looking to cut energy costs. ARM mini servers run the same workloads on a fraction of the watts an x86 desktop pulls. The third group is engineers following the open source ecosystem: the Proxmox ARM port is living proof of how mature QEMU and KVM have become on ARM. The intersection of these three audiences will set the pace of adoption.

What Comes Next?

Proxmox's roadmap is clear: talks with more hardware vendors are ongoing, and the list of supported platforms is expected to grow. On the forums, enterprise users are asking whether vendors like HPE will offer support for their ARM systems. Internal test builds of Proxmox Backup Server are ready; enterprise demand will decide which product gets ported first.

The subscription side is settled as well. The pve-enterprise repository is available for ARM, and enterprise support comes with the same service levels as on x86. ARM subscriptions are separate from x86 ones and are currently available on request through the sales team. So a company moving to ARM is not investing in unsupported software.

Conclusion

Proxmox VE's Arm64 support is more than a software release. ARM servers gaining enterprise-grade virtualization is a milestone that will shape the future of data center architecture. The deep collaboration with NVIDIA entrusts the infrastructure of AI factories to an open source platform, and the full-parity port of storage stacks like ZFS and Ceph removes the "second-class citizen" concern.

If you want to try virtualization on the ARM side, now is the right time. Download the official ISO and test it on a Grace Hopper system or any UEFI-capable ARM server. If you live in the homelab and insist on a Raspberry Pi, the UEFI firmware projects will get you there; but the real potential sits on enterprise ARM hardware. Share your thoughts in the comments, we are curious which hardware you tried it on.