Proxmox ARM64 Explained: Can You Run Proxmox on an ARM Home Server?

Quick answer

Proxmox VE now has an official ARM64 edition, but that does not mean you can install the supported product on any ARM mini computer.

Proxmox VE 9.2 for ARM64 is fully supported on NVIDIA Grace Hopper and NVIDIA Vera platforms. Other UEFI-based ARM hardware is best-effort, while device-tree-only single-board computers such as the Raspberry Pi are explicitly unsupported.

For most home labs, an ordinary x86-64 mini PC or reused desktop remains the simpler Proxmox host today. ARM64 becomes interesting when you already have compatible server-class hardware, need ARM-native guests, or want to test where lower-power virtualisation is heading.

---

What Proxmox actually announced

On 5 August 2026, Proxmox released its first officially supported ARM64 edition of Proxmox Virtual Environment. It is not a community port or a separate lightweight product.

The ARM64 edition shares the Proxmox VE 9.2 codebase, package repositories and release lifecycle with x86-64. Its core platform includes:

• KVM virtual machines
• LXC containers
• software-defined networking
• clustering and high availability
• ZFS storage
• Ceph storage
• the familiar web interface and management tools

That is meaningful platform support. The limitation is the hardware and guest architecture around it.

ARM64 and x86-64 are different architectures

ARM64, also called AArch64, is a 64-bit instruction-set architecture used across phones, single-board computers and increasingly powerful servers. Most traditional home-lab PCs use x86-64, also called AMD64.

The practical difference is that a guest built for one architecture does not automatically become a native guest on the other.

Host	Guest	Practical result
ARM64 Proxmox	ARM64 VM	Native KVM virtualisation on supported hardware
ARM64 Proxmox	ARM64 LXC	Native container sharing the ARM64 host kernel
ARM64 Proxmox	x86-64 VM	Not a normal native KVM workload; architecture emulation is a separate, slower problem
ARM64 Proxmox	x86-64 LXC	Cannot run as an ordinary architecture-matched LXC guest
x86-64 Proxmox	x86-64 VM or LXC	The established home-lab path

An ARM64 Proxmox host therefore needs ARM64 operating-system images and ARM64 application builds. Check every critical image, package, driver and appliance before buying hardware.

Which ARM hardware is officially supported?

Proxmox draws three useful boundaries:

1. Fully supported: NVIDIA Grace Hopper and NVIDIA Vera platforms.
2. Best-effort: other UEFI-based ARMv9-A or newer systems; ARMv8-A may also work on a best-effort basis.
3. Not supported: device-tree-only systems, including Raspberry Pi boards.

An ARM64 host must boot with UEFI and describe its hardware through ACPI. That server-style firmware model matters more than the presence of a 64-bit ARM processor alone.

Before treating any ARM system as a candidate, verify:

• ARM generation and virtualisation support
• UEFI boot
• ACPI hardware description
• storage-controller support
• network-interface support
• IOMMU/SMMU support if PCIe passthrough matters
• availability of ARM64 guest images and application packages

“ARM64” on a product page is not enough.

Can you install official Proxmox VE on a Raspberry Pi?

No. Proxmox’s current requirements explicitly say that device-tree-only single-board computers such as the Raspberry Pi are not supported.

Older community projects have used Proxmox-related packages or unofficial ports on Raspberry Pi hardware. Those experiments are not the new supported ARM64 edition and should not be presented as equivalent to an official Proxmox VE 9.2 installation.

A Raspberry Pi can still be useful as a small Linux server, monitoring node, backup target or quorum device in an appropriately designed lab. It is simply not a supported Proxmox VE ARM64 host under the current requirements.

What feature parity means

Proxmox describes ARM64 as providing feature parity across KVM, LXC, ZFS and Ceph. This means those major platform stacks are present and maintained from the same product line.

It does not mean every x86-specific feature, guest image or binary works unchanged. Proxmox documents architecture-specific differences, including:

• ARM VMs use UEFI through AAVMF; SeaBIOS is unavailable
• AMD SEV and Intel GVT-g are x86-only
• ARM does not use the x86 intel-microcode or amd64-microcode packages
• live migration works only between nodes of the same CPU architecture
• a VM or container runs only on a node matching its guest architecture

A mixed x86 and ARM cluster can be managed together, but it is not one interchangeable compute pool. Backups and storage may move, while the guest still needs an architecture-compatible operating system and applications before it can start on the other architecture.

What ARM64 means for LXC containers

LXC containers share the host kernel. On an ARM64 Proxmox node, the straightforward route is therefore an ARM64 container template with ARM64 packages inside it.

This can work well for services already published for multiple architectures. Before migrating a container, check:

• the distribution provides an ARM64 root filesystem
• every application package supports ARM64
• Docker images inside the guest publish an ARM64 manifest, if Docker is nested in a VM or container
• hardware devices and drivers have ARM64 support
• backup and restore procedures have been tested on the target node

Do not assume an existing x86 LXC backup will simply boot on ARM.

ZFS and Ceph on ARM64

ZFS and Ceph are included in the ARM64 platform, but availability is not the same as suitability for a small home server.

ZFS benefits from adequate memory, reliable storage and a sensible backup design. Ceph is a distributed storage system designed around multiple nodes, multiple disks and resilient networking; it is rarely justified for a single compact home server.

For a first ARM lab, start with simple local storage and prove the platform. Add ZFS only when its integrity, snapshot or replication features solve a real requirement. Consider Ceph only when the lab has the node count, network and operational discipline to support it.

Can ARM lower home-lab power use?

Potentially, but architecture alone does not guarantee a lower electricity bill.

Measure the complete system:

• idle power at the wall
• storage and network-controller consumption
• performance per watt under the real workload
• memory capacity and expansion
• hardware video support
• replacement cost
• software compatibility

An inexpensive x86 mini PC that idles efficiently and runs every required image may be a better home-lab choice than rare ARM server hardware. ARM becomes compelling when compatible hardware, workloads and acquisition cost line up.

What about Jellyfin on ARM Proxmox?

Jellyfin publishes ARM64 software and container images, so the application architecture is possible. The harder question is hardware acceleration.

Check the entire path:

ARM host firmware
→ Proxmox kernel and device support
→ passthrough or device access
→ ARM64 guest driver
→ FFmpeg support
→ Jellyfin configuration

Do not buy an ARM host for Jellyfin solely because the CPU is power efficient. Verify the exact GPU or media engine, driver, guest-access method and codec support first. If predictable transcoding is the goal, established Intel or AMD x86 hardware may still be easier to deploy and troubleshoot.

Use Jellyfin Direct Play vs Transcoding to reduce avoidable transcoding before redesigning the host.

Should you use ARM Proxmox in a home lab today?

Situation	Sensible direction
You already own supported NVIDIA Grace/Vera hardware	ARM64 Proxmox is a genuine supported option
You have another UEFI/ACPI ARM server	Treat it as best-effort and test every device and guest
You want to reuse a Raspberry Pi	Use a normal Pi Linux distribution; official Proxmox VE is not supported
You rely on x86-only appliances or containers	Stay with x86-64 unless replacements are proven
You want a simple first home lab	x86-64 remains the lower-friction route
You are researching ARM-native infrastructure	A separate test node can be worthwhile

For most SmallGrid readers, the right interpretation is watch and test, not “replace the current x86 home server.” The announcement matters because Proxmox now has a maintained ARM foundation. The home-lab hardware market still needs to catch up with accessible, well-supported systems.

Hardware worth watching

Look for systems that combine:

• ARMv9-A or newer CPU cores
• documented UEFI and ACPI support
• useful virtualisation extensions
• standard NVMe or SATA storage
• multiple reliable network interfaces
• SMMU/IOMMU support
• vendor firmware updates
• upstream Linux driver support
• enough RAM for the intended guests
• pricing that competes with efficient x86 hardware

Ampere-class servers and future compact ARM server platforms are more relevant than Raspberry Pi-style boards to the current Proxmox design. Do not assume best-effort hardware will receive the same support outcome as the validated NVIDIA platforms.

Official sources

• Proxmox VE launches official ARM64 support
• Proxmox VE ARM64 announcement and architecture details
• Proxmox VE system requirements
• Proxmox VE 9.2 ARM64 ISO

Related SmallGrid guides

• Proxmox VE 9.2: What Home Lab Users Need to Know
• How to Add a Second Hard Drive to Proxmox
• Docker Compose Explained for Beginners
• Jellyfin Direct Play vs Transcoding
• Backups That Don’t Lie: 3-2-1 for Home Servers

---

Recap

Proxmox VE ARM64 is an official product, not a Raspberry Pi release. It delivers the main Proxmox platform on supported ARM server hardware, but guests must match the host architecture and current full support begins with NVIDIA Grace Hopper and Vera platforms.

For a home lab, confirm firmware, ACPI, device support, guest images and hardware acceleration before buying anything. ARM Proxmox is now real; broadly accessible ARM home-lab hardware is still the part to watch.