Have you tried to stop, then restart the HA VM?
It doesn’t respond to reboot or shutdown commands. I have been resetting it. Not sure if that is the right thing to do.
Edit: Probably because the guest agent isnt running so the VM doesn’t respond to ACPI commands.
Perhaps delete the VM altogether, then in Proxmox run;
apt-get install qemu-guest-agent
systemctl start qemu-guest-agent
then re-run the installer script
sudo bash -c "$(wget -qLO - https://github.com/whiskerz007/proxmox_hassos_install/raw/master/install.sh)"
moxmanager@pve:~$ sudo apt-get install qemu-guest-agent
[sudo] password for moxmanager:
Reading package lists... Done
Building dependency tree
Reading state information... Done
qemu-guest-agent is already the newest version (1:3.1+dfsg-8+deb10u8).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
moxmanager@pve:~$ sudo systemctl start qemu-guest-agent
A dependency job for qemu-guest-agent.service failed. See 'journalctl -xe' for details.
moxmanager@pve:~$ sudo journalctl -xe
Oct 31 22:11:00 pve systemd[1]: pvesr.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pvesr.service has successfully entered the 'dead' state.
Oct 31 22:11:00 pve systemd[1]: Started Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has finished successfully.
--
-- The job identifier is 105419.
Oct 31 22:11:07 pve systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start timed out.
Oct 31 22:11:07 pve systemd[1]: Timed out waiting for device /dev/virtio-ports/org.qemu.guest_agent.0.
-- Subject: A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has finished with a failure.
--
-- The job identifier is 105346 and the job result is timeout.
Oct 31 22:11:07 pve systemd[1]: Dependency failed for QEMU Guest Agent.
-- Subject: A start job for unit qemu-guest-agent.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit qemu-guest-agent.service has finished with a failure.
--
-- The job identifier is 105274 and the job result is dependency.
Oct 31 22:11:07 pve systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'.
Oct 31 22:11:07 pve systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start failed with result 'timeout'.
Oct 31 22:11:07 pve sudo[2306]: pam_unix(sudo:session): session closed for user root
Oct 31 22:11:17 pve sudo[2545]: moxmanager : TTY=pts/0 ; PWD=/home/moxmanager ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Oct 31 22:11:17 pve sudo[2545]: pam_unix(sudo:session): session opened for user root by moxmanager(uid=0)
lines 3713-3748/3748 (END)
Have you checked to confirm your apt source list is correct as per section 2.3 of the guide? Just wondering if it’s a dependency issue from Proxmox not updating. I may be completely wrong, but worth checking.
pve-enterprise.list is blank, per the instructions.
Here is my sudo apt update return:
moxmanager@pve:~$ sudo apt update
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Hit:2 http://download.proxmox.com/debian/pve buster InRelease
Hit:3 http://ftp.debian.org/debian buster InRelease
Hit:4 http://ftp.debian.org/debian buster-updates InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
moxmanager@pve:~$
I can not reproduce the problem on an existing Proxmox install. I have re-run the install script on 2 different machines in 2 different locations, one at home, one in my business.
I have a spare machine at home, so will try a fresh install of Proxmox this evening, or tomorrow and report back.
Thanks. I am going to try and restart from scratch as well.
1 Like
It is enabled. I have tried disabling and reenabling with no change in behavior.
1 Like
I have a very basic question. Why should I use Proxmox? Let me explain. I started with HA on a RPi3…moved to an RPI4 4g/ssd boot and I have a Wyse 5020 running MINT to play with. I also have an older Intel (775) system that I’m about to convert to Linux. I run rtl_sdr and mosquitto on a Pi 0…and PiHole on the 5020. My background is all windows and home assistant…but I’m now diving into the linux world to see what’s interesting. Given all that…I’m tempted to install Proxmox on the 5020 and intel systems…but I don’t understand why I should 
Similar question on Portainer…sounds like I should use it…but why?
OK, I’ve done a fresh Proxmox install on a (very) old Dell 1525 laptop, and have both Proxmox and HA up and running.
At first, I could not get the HA VM to boot after running the install script, and upon checking the boot order, for some reason the SSD installed in the laptop was not selected as the primary boot device, instead, network was. This is what I did to correct it.
Click on the HA VM, then Options, then double click on Boot Order and select you internal drive, such as ‘Disk sata0’ from the list in Boot Device 1. Reboot the Proxmox machine.
Perhaps you can double check this and let me know if you have the same?
Other than that, HA is up and running perfectly. I made to sure run
sudo apt install qemu-guest-agent
during the apt update process to make double sure it was installed before trying the HA script.
So, fresh install of proxmox and homeassitant following the guide to the letter. Same result.
Guest agent not running.
Edit: Okay boot order set, reboot and still no guest agent.
Edit2:
I removed the Home Assistant VM, rebooted, installed the guest as suggested above. Then I ran the script, set the boot order, and rebooted the machine.
Now I have an IP…I have no idea why my proxmox was not setting the boot order right or why the Guest agent wasn’t installed, but it’s running!
Did you check what I just posted above? I have done 2 installs following the guide, with the only change the added steps of making sure guest agent is installed, and changing the boot device (as noted above)
Can reply now, but check edits above. Finally have an IP and got to the web interface!
Excellent. I have added those steps to the instructions.
1 Like
I have installed HA in Proxmox and its up right now but I am having issues with the homekit bridge app. I keep getting an “Accessory not found” on my phone. Has anyone been successfull on getting Homekit bridge working on Proxmox.
I think my issue is that I cannot seem to get Avahi to work properly on Proxmox.
trying ProxMox out on an old Acer Revo 3900 atom processor… proxmox installs normally. I followed the instructions to the letter but when hass vm boots it doesnt get an IP address, tried everything above you suggested to get the guest agent running, but results are always the same with no agent running/ no IP.
also hass vm console output has errors .
any suggestions ?
Is the CPU able to do virtualization? I’m not sure many, if any Atom processors do.
Do a google search to check the specs for the processor, and if it does support virtualization, make sure it is enabled in the bios.
I dont believe it does support cpu virtualisation extensions, but I also read that you can disable this in the Guest machine by switching off KVM hardware virtualisation.
1 Like