Home Assistant OS (HAOS) with Proxmox VE 8.0 Install Guide

Installation
82

Great tutorial, thanks !

I don’t remember if it was your tutorial i used a couple of years ago when going from HAOS on RasPi to HAOS VM on Proxmox 8.2 … but it has been running great.

I have decided it is time for me to reinstall HAOS in a new VM (leaving the old as a backup) and configure it using all the new HA bells & whistles (especially HA voice PE instead of my rhasspy RasPi voice satellites).

However the new VM couldn’t boot. Looking in the comments on your blog post I saw DJones cryptic comment on July 2, 2024 3:00 am

Nvm fixed you can’t use q35 on a proxmox system running in legacy bios mode and use OVMF (UEFI) you have to use i440fx. q35 will work on seabios vm just not with HAS

Which reminded me that I had trouble the first time around. I think that when I setup proxmox on my 2nd-hand Dell Optiplex was the first time I was faced with BIOS or UEFI, and so I may have stuck with the legacy system I was familiar with. For the HAOS VM I remember having trouble with Machine Type and BIOS - ending up using Machine type “i440fx” and BIOS “OVFM (UEFI)” which uses 2 hard disks.

This time the script defaulted to Machine type “q35” and “OVFM (UEFI)” BIOS - but created only one partition (ie no EFI Disk), and then couldn’t find anything to boot from. Changing to SeaBIOS didn’t help.

Removing the new VM and trying again, this time selecting Machine Type i440fx and only 32GB Hard disk (I will increase it later) again failed to boot over IPv4 or IPv6. Checking the “Hardware” section and … Machine “q35”, BIOS “OVMF (UEFI)” and only one Unused disk (no EFI Disk).

So now I’m thinking … I know Proxmox 8.4 and 9.0 are out now. Would I be better off in the longer term wiping this PC, configure for UEFI BIOS, and install latest proxmox ?

83

I would stay away from Proxmox 9 for the moment

https://freedium.cfd/https://medium.com/@PlanB./why-your-ram-vanishes-after-upgrading-to-proxmox-9-and-what-you-can-actually-do-about-it-5b71de32453d

1 Like
84

Ahhh yes, there it is … in the shell script the qm create instruction has machine q35 hard coded, ignoring the users selection :frowning:

msg_info "Creating Home Assistant OS VM shell"
qm create "$VMID" -machine q35 -bios ovmf -agent 1 -tablet 0 -localtime 1 ${CPU_TYPE} \
  -cores "$CORE_COUNT" -memory "$RAM_SIZE" -name "$HN" -tags community-script \
  -net0 "virtio,bridge=$BRG,macaddr=$MAC$VLAN$MTU" -onboot 1 -ostype l26 -scsihw virtio-scsi-pci >/dev/null
msg_ok "Created VM shell"

and combined with a UEFI BIOS but no EFI disk partition means no boot.

85

Thanks @os.habitats.tech … your instructions worked great !

I had spent 1 days trying lots of variations of the derekseaman.com guide to create a new homeassistant VM, and ½ day trying to re-install voice on my existing HA VM - but always something went wrong. I suspect (a) because my host PC was installed using BIOS, (b) because the previous voice installation left some remnants that stopped wyoming from starting.

86

Thank you so much for this Guide.
I’ve just moved from a Pi4 with a failing SD card to HA on Proxmox. I couldn’t have done it without the guide, thank you.