Great guide. Very detailed.
I followed, but wasn’t able to get hassos running. I did install proxmox 6.3 without realizing though…not sure if that is my issue. Looking at the summary there is no IP address and it says guest not running.
Anyone have any advice on what to look into?
Thanks
Is Homeassistant running though Dan? Check your router for a homeassistant instance and try to connect that ip on port 8123.
The no ip address and guest agent not running could simply be because the guest agent “drivers” aren’t installed and everything else is ok.
I know this sounds like a Christopher Nolan film, but it’s not really that complicated. Just running Virtualbox on a Macbook with Proxymox. And trying to run HA OS in Proxmox.
You are unnecessarily complicating things, install Proxmox as the OS, run a HA OS VM. Keep it simple.
The more layers you have to pass things through, the more issues you are likely to face.
2 Likes
Definitely was not running, but for giggles I tried a fourth time last night and today it worked. Showed an IP in the summary and was there ready with the onboarding page.
Why is it using HassOS 4.2 though? I tried to update to 5.9 three times and it says it is working on it, but never does successfully update to 5.9.
I’d be inclined to download the VM image again and reinstall.
The script currently looks for an image with a .gz extension. The newer releases of HA are xz compressed. I’ve just made a couple of edits to the script and will pass them on to the creator of the script.
Edit: Should have checked more… someone else has already submitted the pull request… If you want to see what changes you can go here: https://github.com/whiskerz007/proxmox_hassos_install/pull/98
2 Likes
I’ve forked the script to my Github and have updated this guide and the install script to reflect these changes. I have tested and can confirm it works correctly and downloads HassOS-5.10 (current).
Where are the addons on the harddisk within the vm?
I installed the addon DOODS, but it’s not working, I think it’s failed to copy files over to /opt/doods/models/coco_ssd_mobilenet_v1_1.0_quant.tflite.
So I’m trying to find the install location to copy them manually.
Taken from the linked info in the OP, Backing up and Restoring your configuration…
- If you are currently using Home Assistant OS on a Pi, other SBC or in a VM, your files are located at
/config
I don’t think the addons are under /config.
I’m looking for the addon - doods directory.
Go up one folder 
I’ve switched to Proxmox about a month ago following this guide and the transition really went like a charm. I have had since then however some CPU variances that I think I can narrow down to systemd-resolved.
and here is what a journalctl -fn50 -u systemd-resolved results in, an infinite scrolling of this:
Jan 06 19:36:22 homeassistant systemd-resolved[1477677]: Hostname conflict, changing published hostname from 'homeassistant226988' to 'homeassistant226998'.
Jan 06 19:36:22 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant226988\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN TXT ""
Jan 06 19:36:22 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant226988\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN SRV 0 0 0 homeassistant226988.local
Jan 06 19:36:22 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant226998\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN TXT ""
Jan 06 19:36:22 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant226998\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN SRV 0 0 0 homeassistant226998.local
Jan 06 19:36:22 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant226998.local IN A 10.1.40.179
Jan 06 19:36:22 homeassistant systemd-resolved[1477677]: Hostname conflict, changing published hostname from 'homeassistant226998' to 'homeassistant227002'.
Jan 06 19:36:22 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227002\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN TXT ""
Jan 06 19:36:22 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227002\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN SRV 0 0 0 homeassistant227002.local
Jan 06 19:36:22 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227002.local IN A 10.1.40.179
Jan 06 19:36:22 homeassistant systemd-resolved[1477677]: Hostname conflict, changing published hostname from 'homeassistant227002' to 'homeassistant227003'.
Jan 06 19:36:23 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227003\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN TXT ""
Jan 06 19:36:23 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227003\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN SRV 0 0 0 homeassistant227003.local
Jan 06 19:36:23 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227003.local IN A 10.1.40.179
Jan 06 19:36:23 homeassistant systemd-resolved[1477677]: Hostname conflict, changing published hostname from 'homeassistant227003' to 'homeassistant227013'.
Jan 06 19:36:23 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227013.local IN A 10.1.40.179
Jan 06 19:36:23 homeassistant systemd-resolved[1477677]: Hostname conflict, changing published hostname from 'homeassistant227013' to 'homeassistant227016'.
Jan 06 19:36:23 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227013\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN TXT ""
Jan 06 19:36:23 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227013\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN SRV 0 0 0 homeassistant227013.local
Jan 06 19:36:23 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227016.local IN A 10.1.40.179
Jan 06 19:36:23 homeassistant systemd-resolved[1477677]: Hostname conflict, changing published hostname from 'homeassistant227016' to 'homeassistant227024'.
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227016\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN TXT ""
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227016\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN SRV 0 0 0 homeassistant227016.local
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227024.local IN A 10.1.40.179
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Hostname conflict, changing published hostname from 'homeassistant227024' to 'homeassistant227027'.
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227024\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN TXT ""
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227024\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN SRV 0 0 0 homeassistant227024.local
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227027.local IN A 10.1.40.179
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Hostname conflict, changing published hostname from 'homeassistant227027' to 'homeassistant227035'.
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227027\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN SRV 0 0 0 homeassistant227027.local
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227027\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN TXT ""
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227035\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN TXT ""
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227035\032\091f82e32391f07425383dd5fbb3a6beafa\093._workstation._tcp.local IN SRV 0 0 0 homeassistant227035.local
Jan 06 19:36:24 homeassistant systemd-resolved[1477677]: Detected conflict on homeassistant227035.local IN A 10.1.40.179
Has anyone else encountered that issue before ? Any clue what I should be looking for ?
Thank you
Home Assistant 2021.1.0
HA OS 5.9 / Supervisor 2020.12.7
Proxmos 6.3-3
Sort of having this problem as well. That is guest-agent is installed and everything, but it will go up and down in my hass VM.
So sometimes I can ping it, and sometimes not.
a systemctl status will give inactive(dead) dependency failed.
I’m not quite sure I guet the wiki , do you have to install the quemu-guest-agent i HA as well? Or is it enough to enable it via GUI?
This has started to be a problem just recently, and not quite sure why,
Seems like the problem was an add-on, bluetooth presence monitor. Removed it and so far so good…
1 Like
Seems I was to hasty, still problem with the guest-agent going on an off.
So no problem ping hass when the guest-agent is connected, and suddenly it says it’s not connected and I cant ping, and then it will go back on again.
But I still have one question, on the proxmox wiki it says you have to install guest-agent on the GUEST, wich I take be the hassio VM, and not the proxmox node itself as I understand the guide. At least that what I had to do to get my other VMs guest-agent to run.
The problem here is that as far as I know this is not possible to do.
1 Like
You don’t need to install it to the HA VM.
I did a test install on a old machine yesterday, fresh install of Proxmox and HA VM as per the guide. Worked as expected as has been online for almost 24 hours.
Is there a way to do this without using UEFI? I’ve used this guide and every so often I get dropped into UEFI interractive shell and all i can do is keep reverting back to a previous snapshot for it work again
I’ve installed Proxmox and followed the script. lots of errors when I restore which I have to work through. The first is that I don’t see my usb zwave stick as one of the hardware devices. It ran fine when I was running this AM with debian docker supervised install on the same computer. I’m trying to reinstall everything now using the proxmox install…and using the backup I took just before installing proxmox and this script.
I can find and add the USB stick to the container hardware…which I’ve done…but it doesn’t respond to Home Assistant. I uninstalled the integration, resinstalled it to make sure that the /dev address was correct…and it was…but all of the devices show up as dead in the log.
I’m stumped…
Follow up: I reinstalled using debian 10/docker and the USB zwave card works perfectly.
I had the same issue and found the solution here: https://pve.proxmox.com/wiki/USB_Devices_in_Virtual_Machines#Simple_Way:_pass_the_USB_device_ID_to_the_guest
In particular the qm set command to pass the device ID to the guest.