greg396

Hello @greg396
What exactly are you trying to achieve?
 
I assume you want to run Home Assistant in a virtual machine on ARM64.
That's possible, but you need to install some prerequisites.
According to your links, you're using an Orange Pi 5 Plus (RAM unknown).
It's powerful enough, but I recommend at least 8GB. 🙂
 
First, install an ARM64 clone of Proxmox Virtual Environment (PXVirt).
https://github.com/jiangcuo/pxvirt  
Then install HA:
https://pimox-scripts.com/scripts?id=pimox-haos-vm
 
`bash -c "$(curl -fsSL https://raw.githubusercontent.com/asylumexp/Proxmox/main/vm/pimox-haos-vm.sh)"`  
Done.
 
If you run it on a home server it's OK!
 
---
 
I personally use a Raspberry Pi 4 with 8GB of RAM running Armbian (trixie) since 1,5 year with PXVirt.
It's running:
Home Assistant (ARM64) Pi-hole OMV VM-Trixie Everything performs very well. 😃
 
Regards, Markus

OK I see, now I remember, HAOS aarch64 has been there for download for a long time, I even recommended it to some one on another forum who also only saw the Intel VM, but as I indicated, is a bit hidden on github:
https://github.com/home-assistant/operating-system/releases/
and direct latest link:
https://github.com/home-assistant/operating-system/releases/download/17.2/haos_generic-aarch64-17.2.img.xz
 
I personally don't want the Proxmox stuff indicated by Markus, I just use the standard packages available In Debian (or Opensuse) for years, on both Intel and Arm. Like indicated install virt-manager. 
It is manual install, but at least then more control. I used/use a mix of LVM based block devices and also just raw images (like unxz the one referenced).
 
I see on RPi4 I have the HAOS VM configured with 2 vCPUs and 1GB RAM.
 
On RK3588, so OPi5+, you will need CPU pinning if you use the vendor kernel (6.1) as it does not support mixing big and little (Cortex-A76 and Cortex-A55). Or use just 1 vCPU for the VM, then de-facto no mixing. Mixing is no problem with mainline based kernel, so then you can just use 8 vCPU's if you want. I currently have my NanoPi-R6C running with kernel 6.19.10+deb14-arm64-16k (from Debian sid) and works fine with VM's and all 8 cores.
 

Running VirtualBox on Armbian is generally not a good fit for what you’re trying to do. Armbian is primarily designed for ARM-based single-board computers, and VirtualBox is built with x86 hosts in mind and relies on kernel modules that are not well-supported (or sometimes not available at all) on ARM kernels like the one in your chosen Armbian image. Even if you manage to install the package, it’s very likely you’ll run into missing kernel module issues or lack of hardware virtualization support, especially on boards like the Orange Pi 5 Plus.
If your goal is to run Home Assistant without containers, a more reliable approach would be to either run Home Assistant OS directly on supported hardware, or use a lightweight hypervisor that works well on ARM (such as KVM/QEMU, if your board and kernel support it). Alternatively, if you specifically want VirtualBox, you’ll have a much smoother experience running it on a standard x86 Debian/Ubuntu system rather than Armbian.

Generic aarch64 or x86 image has all needed support for most comon virtual environments. On a side we provide cloud images, optimized to run inside KVM / QEMU virtualized environment - super lean kernel.

https://armbian.com/boards/uefi-arm64
https://armbian.com/boards/uefi-x86

Look for cloud kernel images.
 
 
Here it can only be a problem if host (Orangepi) supports qemu or not. I don't run it here but I think it must just work.
 

There won't be any difference compared to standard Debian / Ubuntu. Armbian is more polished in general, comes with several important improvements.

Securing support for virtual targets is relatively easy compared to any custom hardware. And this was done long time ago. We use Armbian UEFI and QCOW2 virtual images to drive our infrastructur and also automated testing, but of course we target KVM / Quemu not Virtualbox. Which anyway can run normal image. Our runners and cloud services mainly run Armbian Noble cloud.

Our website (dual core x86 vps):


 
www:/boot:% du -h vmlinuz-6.18.10-cloud-x86 15M    vmlinuz-6.18.10-cloud-x86 + 17M for modules (normal image has 150-200M for modules, for things you never need in virtualized environment)
 
 

Yep, that's the best path for this use case.

No error anymore, working expected. After restart the fan spins get quiet after a short time :)