Thanks a lot, it works with an M3 Mac Pro (Sequoia). Just had to extract the disk image after the download. Perhaps a small improvement on step 2, to avoid novice people like me to stop trying.
I ran through this, following instructions multiple times, but I end up with “Display output is not active” every time. Any ideas?
1 Like
same error here!
I am also encountering the “Display output is not active” error, but I found a workaround.
You can add a serial device in “Built-in Terminal” mode and use that terminal to interact with HAOS.
To log in, simply type root. After logging in, you can run the command ha network info to view the IP address you need to connect to.
2 Likes
Set the emulated display card to virtio-gpu-pci
6 Likes
Hi @Jz777 - were you able to figure out the issue ? I am running into the same problem.
Nope, sorry.
I solved it by buying a used NUC on eBay for $35, only to find out my local university surplus had them for less. The NUC is doing fine running HAOS with no containers.
I definitely don’t regret spending the money to avoid problems with containers. It could be the smartest thing with HA that I’ve done to date. 
Hi all,
I am completely new to HA and while I can use CLI, I am in no way expert.
I am trying to get HA working on an iMac24. The UTM interfaces have changed a bit but I managed to follow the guide (thanks BTW) and work out what to do and now have the virtual instance running with the CLI prompt of -
ha >
However, I cannot access either port 8123 or 4357. I suspect it is a networking issue from reading the comments. The iMac 24 only ships with a wifi interface. I have an ethernet adapter but I have not found it to be 100% reliable.
When I set up the network I selected bridged but did not select an interface. I left it as Auto assuming it would find the WiFi interface and use it but it does not appear to have done so.
I cannot find a guide to run HA natively on a silicon Mac so UTM seems the best option but only if I can get the WiFi to respond. I stopped the machine, edited the network to be shared and relaunched it.
Port 8123 appears to open correctly (but I have yet to explore it) but Port 4357 runs up to a point but then gives the following repetitive error.
Home Assistant installation. Retrying in 30sec
2024-12-20 22:42:03.421 WARNING (MainThread) [supervisor.jobs] ‘Updater.fetch_data’ blocked from execution, no supervisor internet connection
2024-12-20 22:42:03.421 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sece
First question is will using the shared network in lieu of bridged give me issues?
Second question is why is the Supervisor page not completing properly?
Are there logs I should post?
Finally, is this the right place to ask these questions or should I open a new thread?
Thanks in Advance,
Geoff
Thank you, fmon! I can confirm that setting virtio-gpu-pci resolves the issue. On a side note, I also updated to HAOS 14.1, though I’m not sure if that update is also necessary.
1 Like
Well nobody replied to my post but I have persevered and am slowly getting somewhere but I have many questions. Is this the best place to post them sir is there another area I should be using please?
Geoff
I don’t think it was the exact same error, but it seems to have been a similar one. By the way, what option did you select under System > System?
My settings are as shown in the attached image, and while I don’t remember the exact option, I recall encountering a similar error when it was set to QEMU 9.1.
After switching to QEMU 7.0 ARM Virtual Machine (virt-7.0), it works properly.
Here does not seem to be the best place to post these issues. however, I have finally got the network to bridge and HA is running successfully over wiFi with a local LAN IP address.
I’ve just successfully got HA working with UTM. Thanks for the guide.
I notice that many UTM controls are missing for the HA VM - options like power off, suspend etc. Anyone know the reason for this? I’ve found that quitting UTM with the HA VM running does seem to do what looks like a suspend, because restarting the VM is very quick and puts me straight back into the command prompt. Would this be a safe thing to do?
This guide worked great for me. One quick question.
Did someone manage to automatically boot the VM upon power resumption for Mac mini (after a reboot)?
Hi @GeoffatMM, I think you placed your question exactly at the right spot, though that setting about network to be bridged was already in the instructions.
To provide some additional info, apart from my innuendos; a bridged network will make it possible you to use the DHCP server in your router to provide an IP address to your VM, while NAT will be creating a new local area network within the VM manager and will assign IP to your VM within that domain.
Hey!
The Installation worked flawless, I restored a backup from my Proxmox HA Install and the only Problem that still exists now is that my Raspberrymatic add-on cannot connect to my HB-RF-ETH. Maybe something with the container networks?
Thanks in advance!
Toby
I want to explain how I managed to do this exactly.
I’m using this AppleScript to start a VM (in this example Debmatic) and attach a USB device.
do shell script "/Applications/UTM.app/Contents/MacOS/utmctl start \"Debmatic\""
delay 1
do shell script "/Applications/UTM.app/Contents/MacOS/utmctl usb connect \"Debmatic\" \"50D4:8A02\""
I exported this script to an “.app” file and added this to the login apps in the os settings.
1 Like
Thanks Soner
Just getting the Shell> prompt in UEFI Interactive Shell.
Macbook Pro Apple M2 Max, Sonoma 14.6.1
UTM 4.6.4 (107)
haos_generic-aarch64-14.2.qcow2 (after unzipping).
Any suggestions on how best to proceed? (A very similar thing happened with VirtualBox.)
I had the same exact issue until I bumped into another thread where the solution was as simple as extract the qcow2 file from xz downloaded.
After I attached the qcow2 extracted file as a disk and changed the display to ‘virtio-gpu-pci’ (to avoid the ‘Display output not Active’ message), it worked first time.
Hope it helps.
1 Like