Hello I try to run the script on a PVE 7 fresh install and I get an error message:
[ERROR] 25@147 Unknown failure occured.
Donโt know what to do about this
Are you using btrfs? if so it wonโt work with the current scripts. It relies on subvol instead of raw
BTRFS integration is currently a technology preview in Proxmox VE.
https://pve.proxmox.com/wiki/BTRFS
Iโd suggest using extfs
yep you are right Iโm in btrfs (raid1) for Pve install
I manages to install it manualy via cmd line finally.
@kanga_who May I know how is the CPU usage for your HA VM? I have an old HA VM with Proxmox 6 in an old notebook. It was running very well till few months back when the CPU usage is always hovering around 90-100%. I used 2 cores of CPU. When it was doing fine few months back, the CPU would be around <25%.
Thinking something could be wrong, I installed Proxmox 7 in a newer Dell 7080 micro I recently bought and again use the script to create the HA VM. With HA being totally bare and I have not setup anything yet, below are the CPU usagesโฆ
- 1 CPU core, CPU usage is 55-70%.
- 2 CPU cores, the CPU usage is 20-45%.
Did the newer versions of HA uses more CPU?
No issues for me
Thanks for confirming. 
I found the culprit. It is actually the old HA VM in the Proxmox 6 notebook. Once i turned off that VM, all systems CPU usage went down to <10%.
Not sure what is wrong in that VM. I have not changed any settings so far except upgrading versions. Looks like now I have no choice but to force myself to move everything to the new 7080 micro. Hopefully everything will turn out fine. 
Update: Moving to the new system did not help after I configured network. As I have 3 networks that HA is connected to, the mDNS implementation of HA was causing issues even though I have not changed any settings previously both on my network and HA. I now have resolved the problem with a very simple fix that I mentioned in the other thread (Setup VLAN and HA tutorial - #66 by skull29). Hopefully it helps anyone encountering the same issue as me 
@kanga_who this might be a stupid question, but is there a reason why you recommend putty instead of using the Shell option that is available within Proxmox?
I donโt only access Proxmox, so use Putty for all my SSH connections. Easier to have everything in one place.
Like @kanga_who I use terminal (I run MacOS) for all remote connections.
Worth remembering that putty/terminal is a remote connection and the Proxmox shell is a console connection as if you have plugged in a keyboard and monitor to the system - that is it works even without networking in the KVM/LXC.
This is depend on your need, in my case if I want a quick changes I will use Proxmox console which usually performing update etc. However some hard function which required copy paste then I will use the SSH terminal. I know that in most cases depend on your console setup you can also perform the same task on console. But anyway that is just me. Everyone will have their own preferences
@kanga_who thank you for your contribution! Moved from the raspberrypi install methods to new proxmox box!
The script installs Home Assisnatnt OS 8 RC version, followed instruction all went smooth, restored my old config fro HA untill I noticed random (under investigation) Home Assistant reboots. VM does not restart.
Then started from scratch deleted VM made manual install, Home Assisnatnt OS 7.6 same. Deleted VM again, manually istalled Home Assisnatnt OS 7.6 and new home assistant configuration from zero same results. Changed recorder to default (i was using mariadb in my Supervised raspberry install), same.
Nothing obvious in all the logs. Switched logger to info today.
Any clues where to look?
Worked like a charm. Very much appreciated.
Running it on Promox 7 now on a Intel J4215 plattform with 4 cores and 16GB RAM.
So, Iโve installed using this guide and donโt see the IP address coming up. It shows โGuest Agent not runningโ.
Just like Installing Home Assistant OS using Proxmox 7 - #180 by Judman13 this user experienced, the output Iโve got when running the update commands is:
# sudo apt update && sudo apt dist-upgrade -y && sudo apt install qemu-guest-agent -y && sudo apt autoremove --purge -y
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://ftp.debian.org/debian bullseye InRelease
Hit:3 http://download.proxmox.com/debian/pve bullseye InRelease
Hit:4 http://ftp.debian.org/debian bullseye-updates InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
qemu-guest-agent is already the newest version (1:5.2+dfsg-11+deb11u1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
What should I do to have this solved?
If youโve used the script above in the past 24hrs, it is broken, it downloads the wrong image (haos_generic-aarch64-8.0.rc3.vmdk)
Yes, Iโve used it today. Any idea for a solution or workaround?
Hereโs my take on โis the wayโ
Prior to Section 1, you will want to ensure UEFI Boot & Virtualisation is enabled and Secure Boot is disabled in the bios of your machine.
Section 1 - Use this guide
Section 2 - Use Proxmox VE 7 Post Install script*
Section 3 - Use Home Assistant OS VM script*
*Always remember to use due diligence when sourcing scripts and automation tasks from third-party sites.
Enjoy
1 Like
After many days of testing I realized that at random my addons were not loading at all, same with my system tab that has the logs and supervisor info etc, my network usage was decreasing, cpu and ram usage was increasing. That time I was having either a home assisntant restart or addons staying frozen with integrations working.
The problem seems to be the odd home assistant OS DNS behaviour described here and in many more post at github:
Solution here:
I am using Home Assistant OS on Proxmox with pfSense running on the same VE.
Hope that I have helped !
I have been banging my head against a wall for hours following the original guide with scripts multiple times and not getting anywhere. Glad I scrolled all the way down here. I have been trying to fix a "Guest Agent not runningโ issue but really the container never really started up to initiate the Guest Agent I suppose. Thanks.
1 Like
Iโve installed HAOS via the script ten times. I still cannot get past the Preparing Home Assist screen. Iโve scoured these forums, cutting and pasting from my error log. Nothing. Hereโs where I think the problem is:
22-05-03 00:15:28 ERROR (MainThread) [supervisor.supervisor] Update of Supervisor failed: Canโt install ghcr.io/home-assistant/amd64-hassio-supervisor:2022.04.0: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=2022.04.0&fromImage=ghcr.io%2Fhome-assistant%2Famd64-hassio-supervisor&platform=linux%2Famd64: Internal Server Error (โGet โhttps://ghcr.io/v2/โ: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)โ)
22-05-03 00:15:28 CRITICAL (MainThread) [supervisor.core] Canโt update Supervisor! This will break some Add-ons or affect future versions of Home Assistant!
Any suggestions as to where Iโm going wrong with this install would be greatly appreciated. Thanks!