How to Install Proxmox VE 9.2 on ARM64: Hardware Support, Setup, and Limits
Proxmox · Virtualization · ARM64
How to Install Proxmox VE 9.2 on ARM64: Hardware Support, Setup, and Limits
Proxmox VE now has an official ARM64 build. The important detail is not simply whether a server has an Arm processor. Proxmox VE 9.2 expects an ARM64 host that boots with UEFI and describes its hardware through ACPI. NVIDIA Grace Hopper and NVIDIA Vera platforms receive full support. Other qualifying ARM servers are best effort, and device-tree-only boards such as a standard Raspberry Pi are outside the supported path.
This guide helps you decide whether your hardware fits, prepare the official ARM64 installer, complete the first boot, and avoid the architecture traps that matter when you already run x86 Proxmox nodes.
Reviewed: August 2026
What changed in Proxmox VE 9.2
On August 5, 2026, Proxmox released its first official build for a CPU architecture other than x86-64. The ARM64 edition shares the same code base, package repositories, documentation, and release lifecycle as the x86-64 build. The initial ARM release is based on Debian 13.6, uses Linux kernel 7.0, QEMU 11.0, LXC 7.0, ZFS 2.4, and Ceph Tentacle 20.2.3.
This is not labelled a technology preview. That statement still needs context. Proxmox lists NVIDIA Grace Hopper and NVIDIA Vera as the fully supported platforms. Other UEFI-based ARMv9-A servers, and many ARMv8-A servers, receive best-effort support.
The announcement attracted active discussion. A Hacker News submission reached 96 points and 40 comments, while recent r/Proxmox threads asked about ARM home labs, Apple Silicon, NVIDIA DGX Spark, and Raspberry Pi-class hardware. Those discussions show interest, not compatibility evidence. The firmware model is the deciding technical requirement.
Check your hardware before downloading anything
A server can have a capable ARM64 CPU and still fail the official compatibility test. Work through these checks in order.
1. Confirm the CPU architecture
If Linux is already installed, run:
uname -m
lscpu | grep -E 'Architecture|Model name'
uname -m should report aarch64. Proxmox documents ARMv8-A as the minimum evaluation baseline and recommends ARMv9-A or newer.
2. Confirm UEFI boot
Run:
test -d /sys/firmware/efi && echo "UEFI boot detected" || echo "UEFI boot not detected"
The official ARM64 build does not support legacy BIOS boot.
3. Confirm ACPI hardware tables
Run:
test -d /sys/firmware/acpi/tables && ls /sys/firmware/acpi/tables
A populated ACPI table directory is the signal you want. Proxmox does not support device-tree-only hosts. Some boards offer experimental UEFI firmware but still do not provide a complete server-class ACPI implementation. Treat that as a lab experiment, not a supported deployment.
4. Classify the support level
| Hardware type | Proxmox status | Editorial recommendation |
|---|---|---|
| NVIDIA Grace Hopper or NVIDIA Vera | Fully supported | Suitable for supported production planning |
| UEFI and ACPI ARMv9-A server | Best effort unless listed otherwise | Validate storage, NIC, console, and reboot behavior before use |
| UEFI and ACPI ARMv8-A server | Generally works, best effort | Good lab candidate, but test every device path |
| Device-tree-only SBC | Not supported | Do not use the official ARM64 deployment path |
| Raspberry Pi with its normal firmware model | Not supported | Choose a qualifying server instead |
| Apple Silicon Mac | Not listed as a supported bare-metal host | Use a supported server or evaluate nested/lab options separately |
Installation plan
The installation process resembles x86 Proxmox, but a careful preflight matters more because ARM server firmware and device support vary.
Back up or evacuate the target disk
The installer repartitions the selected disk. Copy any data you need to another system and verify the copy before continuing. If this ARM host will join an existing environment, export the current network map, storage plan, VLAN IDs, and DNS settings before touching the disk.
For production hardware, confirm remote console access through BMC or the platform's management controller. A local keyboard and display are not a substitute for recovery access on a remote server.
Download the ARM64 ISO and verify it
Download the ARM64 build from the official Proxmox download page. The current file reviewed for this article is:
proxmox-ve_9.2-1-arm64.iso
For that exact file, Proxmox publishes this SHA-256 value:
b1619dcd1f5b1a6d67d77b59e7e2fa2033174551d1e1b9dc22b2171ec093abbd
Verify your download on Linux:
sha256sum proxmox-ve_9.2-1-arm64.iso
Only continue if the output matches the checksum on the official download page. If Proxmox has released a newer ISO, use the checksum displayed for that newer file rather than the value above.
Write the ISO to a USB drive
First identify the whole USB device:
lsblk -o NAME,SIZE,MODEL,TRAN,MOUNTPOINTS
Unmount any mounted partitions on that USB drive. Then write the image. Replace /dev/sdX with the whole USB device, not a numbered partition.
sudo dd bs=1M conv=fdatasync \
if=./proxmox-ve_9.2-1-arm64.iso \
of=/dev/sdX
This command destroys the contents of the selected destination. Check the device name, model, and size again before pressing Enter. Proxmox explicitly advises against UNetbootin for its installer image.
Configure firmware and boot the installer
In the server firmware:
- Select UEFI boot mode.
- Confirm that ACPI is enabled and current firmware is installed.
- Enable the platform SMMU if you plan to use PCIe passthrough.
- Put the USB device first for this boot.
- Keep a remote console open so you can capture early boot failures.
Start with Install Proxmox VE (Graphical). If graphics or input fails, retry with Install Proxmox VE (Terminal UI). Proxmox documents the terminal installer as the better fallback for very new or unusual hardware.
Complete the installer deliberately
Choose the target disk, filesystem, locale, administrator password, email address, management interface, hostname, static IP address, gateway, and DNS resolver. Use a stable management address. Avoid placing the web interface on an untrusted or public network.
For storage, do not automatically choose ZFS because it is familiar. Confirm that the ARM platform's storage controller and available memory suit the design. Proxmox recommends additional memory for ZFS and Ceph, roughly 1 GB per TB of used storage in addition to memory for the host and guests. ZFS and Ceph should not sit behind a hardware RAID abstraction.
When the installer finishes, remove the USB drive and reboot.
First-boot validation
Open the web interface at:
https://SERVER-IP:8006
Sign in as root using the PAM realm. A certificate warning is expected until you install a certificate trusted by your clients.
Run these checks from the host shell:
uname -m
pveversion -v
ip -br address
systemctl --failed
pveperf
Expected results:
uname -mreportsaarch64.pveversion -vlists the installed Proxmox VE 9.2 packages.- The management bridge and address match your plan.
systemctl --failedshows no unexplained failed units.pveperfcompletes. Treat it as a quick baseline, not a full benchmark.
Also review storage health, NIC link speed, kernel messages, NTP status, and several cold reboots. Best-effort hardware needs more than one successful boot before you trust it with persistent workloads.
Create the first ARM64 guest
Use an ARM64 guest ISO. An x86-64 Ubuntu, Debian, Windows, or appliance image will not become compatible because the Proxmox host is running QEMU.
In the VM wizard:
- Upload an
arm64oraarch64operating-system image. - Create the VM on the ARM64 node.
- Keep the default UEFI firmware. ARM guests use AAVMF, the ARM build of OVMF.
- Select VirtIO devices only when the guest includes the required drivers.
- Install, patch, and verify the guest normally.
SeaBIOS is unavailable on ARM64. Appliances that assume legacy BIOS or ship only x86 binaries need a different image or a rebuild.
Clusters, migration, and mixed architectures
Proxmox does not technically block a cluster containing both x86-64 and ARM64 nodes, but the vendor does not officially support mixed-architecture clusters. Plan separate failure domains unless you have a specific test objective.
The rules are straightforward:
- Live migration works only between nodes of the same architecture.
- A VM or container runs only on a node matching the guest architecture.
- Backup and restore, offline migration, or shared storage can move guest data across architectures.
- Moving the data does not translate the operating system or applications. The guest must be reinstalled or reconfigured for ARM64 before it can start.
This matters for high availability. An ARM64 guest needs another compatible ARM64 node if you expect automatic recovery elsewhere.
Security and operations after installation
Do not expose TCP port 8006 directly to the public internet. Place the management interface on a trusted VLAN or private network, restrict access with the Proxmox firewall and an upstream firewall, and use a VPN for remote administration. Create named administrator accounts, enable a second factor, and keep root access for recovery.
Configure an update repository immediately. Proxmox provides an ARM64 enterprise repository and the same enterprise support service levels for subscribed hosts. Public repositories remain available for systems without a subscription, with the usual distinction that the enterprise repository receives additional testing.
Before adding important guests, configure backups to a separate failure domain and perform a restore test. Proxmox stated in its release announcement that ARM64 builds of some other products, including Proxmox Backup Server, were internal test builds at that time. Verify the current supported architecture of your backup target instead of assuming every Proxmox product has reached ARM64 release status.
If the node will host AI workloads, confirm GPU and accelerator passthrough on the exact platform. An ARM64 host does not guarantee that an x86-oriented driver stack, container image, or appliance is available. The same architecture check applies to every layer.
Common problems
The USB installer does not appear in the boot menu
Confirm that the ISO was written to the whole USB device and that the server is set to UEFI boot. Recreate the media with dd, try the terminal installer, and update server firmware. Do not switch to legacy BIOS as a workaround because Proxmox ARM64 requires UEFI.
The installer starts but cannot see storage or networking
This usually points to a kernel-driver or firmware-description gap on best-effort hardware. Capture dmesg, PCI device IDs, ACPI information, and the exact firmware version. Test a current Debian 13 ARM64 environment to separate general Linux support from a Proxmox-specific issue.
An x86 VM will not start on the ARM64 node
That behavior is expected. Reinstall the guest with an ARM64 operating-system image and restore application data, or keep the workload on an x86 node. Proxmox does not provide transparent cross-architecture guest execution.
A Raspberry Pi has UEFI firmware, so should it work?
Experimental firmware may let some boards boot farther than their default setup, but Proxmox explicitly excludes device-tree-only boards such as the Raspberry Pi from supported ARM64 hosts. A community demonstration is not equivalent to vendor support. Use a qualifying UEFI and ACPI server for a dependable deployment.
FAQ
Is Proxmox VE on ARM64 a technology preview?
No. Proxmox says the ARM64 edition is not a technology preview. Full vendor support is currently limited to the NVIDIA Grace Hopper and NVIDIA Vera platforms; other qualifying ARM servers are best effort.
Can Proxmox VE 9.2 run on a Raspberry Pi 5?
Not through the supported path. Proxmox requires UEFI boot and ACPI hardware description and explicitly states that device-tree-only boards such as the Raspberry Pi are unsupported.
Can I add an ARM64 node to my x86 Proxmox cluster?
It is not technically blocked, but mixed-architecture clusters are not officially supported. Guests and live migration remain restricted to matching architectures.
Can an ARM64 Proxmox host run x86 virtual machines?
Not as ordinary Proxmox guests. Use ARM64 guest images or keep x86 workloads on x86 nodes. Cross-architecture emulation is a different design and is not the normal supported virtualization path described here.
Does Proxmox ARM64 support ZFS and Ceph?
Yes. The ARM64 release includes ZFS 2.4 and Ceph Tentacle 20.2.3. Hardware, memory, and storage-controller design still determine whether either option is appropriate.
Is enterprise support available for ARM64?
Yes. Proxmox provides an ARM64 enterprise repository and enterprise support for subscribed supported hosts. ARM64 subscriptions are separate from x86-64 subscriptions and were available on request at the time of the release announcement.
Final recommendation
Proxmox VE 9.2 on ARM64 is ready for serious evaluation, but it is not a shortcut for turning any Arm board into a supported hypervisor. The safe purchase decision begins with UEFI, ACPI, server-class device support, and ARM64 guest availability. Choose NVIDIA Grace or Vera when full vendor support is mandatory. For Ampere and other qualifying servers, treat the first deployment as a hardware-validation project before moving persistent workloads.
For broader lab planning, see Best Home Lab Services to Run in 2026. If ARM64 is part of an AI lab, also review How to Run Local LLMs with Ollama and Open WebUI on Your Homelab and confirm that each model runtime, accelerator driver, and container image supports your architecture.
Sources
Bikram Bhujel is an IT Infrastructure Specialist based in Nepal, writing about enterprise networking, server administration, and home lab setups at bikrambhujel.com.np
No comments:
Please Don't Spam Comment Box !!!!