Hello everyone,
I am trying to set up Haiku on Mac m1 in UTM, but every time I try to run Haiku, the following thing shows up.
Can anyone suggest how to fix it?
Hello everyone,
I am trying to set up Haiku on Mac m1 in UTM, but every time I try to run Haiku, the following thing shows up.
Can anyone suggest how to fix it?
This is the efi shell, it is not related to Haiku.
This probably means haikus bootloader wasnt started.
How did you set up this vm?
Hi I’ve shared my UTM package, you will need to add the Haiku ISO to the IDE CD Drive in UTM and also create an IDE Hard Drive for it to work.
But this configuration works on my Mac Studio M2 Max
https://drive.google.com/drive/folders/1VeM4tK6LkySjNOrucpuSGjf21q6Yd-gF?usp=drive_link
Thank for your response.
While setting up UTM for Haiku, this notification occurs. I am not sure if this is the issue. Can you please tell?
Does your UTM instance look like this, with the machine listed as:
“Standard PC (i440FX + PIIX…)”
I use UTM all the time. PM me and I’ll send you a VM that works.
Thank you sir.
Hello mate.
No, it seems a bit different.
I tried yours as well. But maybe the issue is in my UTM as I am facing the same problem when I am using yours as well.
Sounds like you have an apple M(1-4) ARM machine. Haiku is not compatible with this cpu architecture
Check if you can emulate x86-64, otherwise it will not work.
UTM settings with UEFI boot unticked works fine on my MacBook Pro (Intel)
Thanks!
I am able to see this after the emulation. But I cannot untick UEFI boot as the “edit selected VM” is disabled. Maybe I need to figure it out first.
you need to right click the UTM VM on your left hand side and select “stop” to force close the VM instance, then you can edit the VM
I am actually new to this community and recently have learnt about Haiku. As I am just a beginner, my problems might be silly. But your cooperation really means a lot to me. Thank you so much!
There is no need to disable EFI boot, haiku supports this aswell.
But in this instance UEFI booting isn’t working correctly, so in order to boot they needed to disable UEFI.
They used the wrong architecture in the emulation software, their issue was not caused by EFI. And apart from that there are no issues reported for this emulation software with our EFI loader.
You can see above that they already had the VM working without changing this setting.
My UTM file had UEFI enabled and didn’t work for them as above, until they disabled UEFI
If you had an issue with this please report a bug on the bugtracker. The problem in this thread was not caused by it.