HAOS will not start on a Proxmox VM

root@prox4nanopi:~# lscpu
Architecture:             aarch64
  CPU op-mode(s):         32-bit, 64-bit
  Byte Order:             Little Endian
CPU(s):                   8
  On-line CPU(s) list:    0-7
Vendor ID:                ARM
  Model name:             Cortex-A55
    Model:                0
    Thread(s) per core:   1
    Core(s) per socket:   4
    Socket(s):            1
    Stepping:             r2p0
    CPU(s) scaling MHz:   81%
    CPU max MHz:          1800.0000
    CPU min MHz:          408.0000
    BogoMIPS:             48.00
    Flags:                fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
  Model name:             Cortex-A76
    Model:                0
    Thread(s) per core:   1
    Core(s) per socket:   4
    Socket(s):            1
    Stepping:             r4p0
    CPU(s) scaling MHz:   22%
    CPU max MHz:          2256.0000
    CPU min MHz:          408.0000
    BogoMIPS:             48.00
    Flags:                fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
Caches (sum of all):
  L1d:                    384 KiB (8 instances)
  L1i:                    384 KiB (8 instances)
  L2:                     2.5 MiB (8 instances)
  L3:                     3 MiB (1 instance)
Vulnerabilities:
  Gather data sampling:   Not affected
  Itlb multihit:          Not affected
  L1tf:                   Not affected
  Mds:                    Not affected
  Meltdown:               Not affected
  Mmio stale data:        Not affected
  Reg file data sampling: Not affected
  Retbleed:               Not affected
  Spec rstack overflow:   Not affected
  Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:             Mitigation; __user pointer sanitization
  Spectre v2:             Mitigation; CSV2, BHB
  Srbds:                  Not affected
  Tsx async abort:        Not affected

The failure is:

Using HAOS Version: 16.3
Virtual Machine ID: 102
Using Hostname: haos16.3
Allocated Cores: 2
Allocated RAM: 4096
Using Bridge: wan
Using MAC Address: 00:60:2F:6C:2F:65
Using Vlan: Default
Using Interface MTU Size: Default
Start VM when completed: yes
Creating a HAOS VM using the above advanced settings
 âś“ Using local for Storage Location.
 âś“ Virtual Machine ID is 102.
 âś“ https://github.com/home-assistant/operating-system/releases/download/16.3/haos_generic-aarch64-16.3.qcow2.xz
 âś“ Downloaded haos_generic-aarch64-16.3.qcow2.xz
 âś“ Extracted Disk Image
 âś“ Created HAOS VM (haos16.3)
 - Starting Home Assistant OS VM...kvm: Failed to put registers after init: Invalid argument
start failed: QEMU exited with code 1
/dev/stdin: line 315: DIAGNOSTICS: unbound variable

I am not new to HAOS, but I am new to KVMs.

Any ideas on a fix?

BTW - I am happy to DEDICATE this host to HAOS - so don’t really need a VM - but my understanding is that HAOS needs to run in a VM now for Long term support as Home Assistant Core support is going away.

On a machine like yours I would look into installing HAOS directly on the hardware.
Your ram is just on the edge of having benefit of a VM. Your storage is definately not and your CPU is probably not really that over powered for just HAOS alone.

1 Like

This is referring to the install method called Home Assistant Core…
All versions of HA use the core as a base, but that method uses core and you provide everything else.
I agree, HAOS on bare metal is where I would go with that. I run 2 copies on marginal hardware and it’s fine.

Your machine would be absolutely fine for HAOS in Proxmox WITH a larger hard drive. Then you would have ability to have snapshots, easier backup/restore, and possilbly even another container or VM for something small if you ever want. Likewise, add another “server” or two down the line and you can cluster these and have High Availability (depending on your smart home network requirements and implementation.

Also, just my 2 cents… start now with Proxmox 9.x so you don’t have to go through a semi-complicated upgrade in about a year when 8.x is no longer supported.

How did you installed proxmox on arm? As far as I know it is and probably never be officially supported by proxmox. So that might be issue.

Easy: The vendor of the NanoPi R6C provides it.

https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R6C#Downloads

OK - MORE than happy to do a dedicated install on this box.

Based on this page, I am not sure how :

Installation options:

  • RPi: My host is ARM64, but not an RPi
  • Other: My host is neither Odroid nor X86
  • Linux: This is a good candidate … but says to run in Docker VM
  • Other systems: includes KVM/Promox. The Promox option failed for me.

I can install these OSes on my host:

What should I try next?

Oops, sorry I didn’t catch that it was an ARM processor. Somehow I read AMD. Probably won’t work on ARM. (Proxmox is not officially supported on ARM)

You can check GitHub releases of HAOS there is also generic arm image

That might help but I never used nanoPi nor this generic image.

When I was running HA on RPi4 8Gb I used docker for it as I wanted more flexibility of other containers. (I was not sure is I will not need something outside add-ons shop, in the end I didn’t )

But with docker install there are some traidoffa like not having add-ons and not able to upgrade nicely from within the HA

Solved:

  1. Used Ubuntu 20.04.06
  2. Got virt-manager installed and working.
  • This was the hardest. A few issues related to ARM64, but finally google searches helped me fix the problems
  1. Used HAOS Linix install with qcow2 file

Thanks for the advise.

1 Like

Small correction:

Used this file haos_generic-aarch64-16.3.qcow2.xz