Installing Home Assistant OS using Proxmox 8

@tteck @kanga_who

Just wanted to take the opportunity to thank you for excellent work!

Migrated from RPi4 (8gb - 128gb SSD) running HAOS to DELL OptiPlex 7040 micro (8gb - 128gb NVME) running Proxmox VE 7.3-6, HAOS VM, cups printer server on host etc…

Piece of cake with your scripts and instructions. Upgraded PVE, installed HAOS, migrated old backup from HA, a little house cleaning with bits and bobs (shell commands, IP addresses etc. mac address assignments etc…) and bobs your uncle, system up and running about 20x faster than before. Measured approx. 10w power consumption - better than expected.

I went the VM route because I wanted other stuff together with HA, and still have a supported HA installation + addons.

Just putting all this out there, in case anyone has some decision-making todo about migrating. I’m no IT specialist, and it took under an hour including hardware installation.

Anyway, again a much appreciated THANKS for this guide & scripts.

4 Likes

Hi, I am currently using a RPi4 with 4GB RAM and an SSD.
Some sensors, nothing too fancy, glances, grafana, mqtt, zigbee2mqtt, nodered and wireguard.
I would like to also use Vaultwarden ans possibly Adguard home.

I do not want to experiment too much with my RPi, as it is the core of the house.

I am specially worried about the power comsupton, as at this moment it is almost nothing.

I am looking at a HP Elitedesk 800 G3 DM Intel i5-6500T RAM 16GB Disco 250GB for 158€ in Amazon Renewed (1 year of warranty). What do you think it will be the Power Consumtion with the above services? Is it a great update?

I have been invetigating and this Proxmox route seems to be what I am looking for in case I decide to upgrade.

Thanks for your help!

Going forward, versioning will no longer be utilized in order to avoid breaking web-links in blogs and YouTube videos (for the final time). So, as a result, the name of the shell script has been updated from haos-vm-v5.sh to haos-vm.sh .

3 Likes

Hi, I do not really understand the difference or the advantage of using an LXC containter instead of a docker container over a Linux distribution.

On the other hand, there are several scripts that says that you can use Alpine Linux to create the LXC container with faster creation time and minimal resources. What is the disadvantage? Why not use that way if it seem to be much better?

At last, I am confused about how the creation of other docker container should be done: by installing any Operative system LXC or by using the Docker LXC . In both methods I cannot see how the resources escalate (the docker LXC takes 1 Gb RAM, as an example)

Sorry if I am asking pretty basic questions, but I am completely new to Proxmox.

I would be very grateful if you could explain a bit the above or tell me where to study those questions.

Thanks!

As the question is not related to the current topic, it would be more appropriate to ask it here.

1 Like

I’ve missed that one never saw/clicked on the “Discussions” there, for these “Components” where i “checked it out”, it usually was “dead-threads” if any at all, thx for the hint :+1:t4:

1 Like

Thanks, I will post it where you suggested. Right now I am trying to figure out if I should upgrade, what hardware is better for my needs and if it is really going to improve the actual situation, and this includes the possibilities that Proxmox gives. This is why I am asking.

Hi.

I tried yesterday to install HAOS 9.5 in a fresh pve 7.4-3 with the script given in the first post, but I could not make the VM get an IP.

It appears as running, but in the IP field, “Guest Agent not running” appears:

But, it is enabled in the VM options:

And the boot order is correct:

image

As I read in posts above, I installed the qemu-guest-agent package in proxmox host (which it was not installed, actually) through the console:

apt-get install qemu-guest-agent

And deleted and reinstalled the VM, but nothing. I cannot make it get and IP.

Anyway, in proxmox documentation, it seems it must be enabled/installed in the guest VM. But, it appears enabled and, if I cannot connect to the guest, I cannot try to install anything!

In fact, it is enabled, but not running:

image

Any clues, please?

Thanks!

@dml33 What does your router show in terms of connected devices - either an IP address that it has assigned to your HA guest, or anything in tte logs which might show a reason why an IP address request isn’t being serviced? If you migrated to proxmox, we’re you using a static IP for your previous HA instance? Have you restricted access on your network via mac address or anything like that previously?

Well… I have been investigating a little. It seems that HAOS does not actually boot up.

In the VM Console, GRUB appears. Slot A seems to try to start, but hangs and the VM restarts. Slot B does not do anything at all.

image

image

I have tried different HW configurations (BIOS, Display, Machine, SCSI Controller), but I cannot find the right way to boot it up.

1.1) Before proceeding with the installation, make sure that UEFI Boot & Virtualization is enabled and Secure Boot is disabled in your machine’s BIOS.

Were you careful to follow this?

Yes. It seems it related to Proxmox itself:

Downgrading to pve-edk2-firmware=3.20220526-1 made it work (for now).

@tteck Love your scripts, thank you! Used the HAOS and InfluxDB scripts on Proxmox and went smoothly. Two minor suggestions:

  1. On the HAOS VM, set the disk cache mode to “write through”. This can better protect against sudden power loss filesystem and database corruption.

  2. On the InfluxDB 1.x LXC install, could you add Chronograf and Kapacitor? Chronograf is needed for a simple UI to help setup InfluxDB to be used with HA.

I included a choice within the “Advanced” settings to configure the disk cache between none (default) or Write Through.

Awesome! Any thoughts on adding the two packages to InfluxDB?

" Which storage pool you would like to use for the HAOS VM?"

I couldnt go further :frowning:

spacebar = select

omg :)) thank you very much

1 Like

Had a simular problem (the same sympthoms) after upgrading to proxmox 7.3 . Non of the VM-s started, they were stuck in a loop. Tried creating a new VM for HA with the same result.
I managet to solve the problem by setting the processor type of the virtual machines from the default to HOST. (Hardware>Processors - edit and set type to HOST the default i think was KVM or QEMU).
After setting all of my VM-s to this processor type all started again.

1 Like

Is it helpful to include that option in the installation script (CPU Model)?

Edit: I included a choice within the “Advanced” settings to configure the CPU model between kvm64 (default) or host.