# UTM On M1 Mac Emulating Intel MacOS?

**URL:** <https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255>\
**Category:** Other\
**Created:** [22 January 2025 17:25 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255 "2025-01-22T17:25:33Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![bkeeney](https://ifnotnil.com/user_avatar/ifnotnil.com/bkeeney/32/225_2.png) [@bkeeney](https://ifnotnil.com/u/bkeeney)\
**Post date:** [22 January 2025 17:25 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/1 "2025-01-22T17:25:33Z")

</div>

Casting a wide net here since we’ve been unable to figure it out. We just got Apple Silicon Macs and running VSCode on them is no problem. However, our app is still Intel and the Delve (go) debugger won’t properly drop into the debugger with Intel apps running on Arm.

So I’ve started looking at UTM to run MacOS Intel in emulation. However, I have yet to find instructions on how to get Intel MacOS installed. I can install an Arm Mac/Win/Linux no problems but not in emulation. Every time I do I drop into a UEFI terminal and no commands work in it.

My GoogleFoo and LLMFoo is clearly lacking. So, please just don’t copy/paste from an LLM since I’ve already tried that with no luck.

---

<div class="post-metadata">

**Author:** ![Abbie](https://ifnotnil.com/user_avatar/ifnotnil.com/abbie/32/4533_2.png) [@Abbie](https://ifnotnil.com/u/Abbie)\
**Post date:** [22 January 2025 20:03 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/2 "2025-01-22T20:03:46Z")

</div>

You have to treat it like a hackintosh and install it with opencore(?).

Outside of that, intel mac for debugging may be the way to go, and are generally stupid cheap at the moment. Check a local university to see if they are tossing any, and/or better yet, get your company to pay you for these efforts too. 😃

> [@bkeeney](#):
>
> So, please just don’t copy/paste from an LLM since I’ve already tried that with no luck.

I asked Eliza, but their response was, “Why does however, our app is still Intel and the Delve (go) debugger won’t properly drop into the debugger with Intel apps running on Arm make you feel that way?”

---

<div class="post-metadata">

**Author:** ![Abbie](https://ifnotnil.com/user_avatar/ifnotnil.com/abbie/32/4533_2.png) [@Abbie](https://ifnotnil.com/u/Abbie)\
**Post date:** [22 January 2025 20:04 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/3 "2025-01-22T20:04:36Z")

</div>

Sidenote, IIRC, debugger architecture should match app architecture.

---

<div class="post-metadata">

**Author:** ![Jerry-Fritschle](https://ifnotnil.com/letter_avatar_proxy/v4/letter/j/b5a626/32.png) [@Jerry-Fritschle](https://ifnotnil.com/u/Jerry-Fritschle)\
**Post date:** [22 January 2025 20:40 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/4 "2025-01-22T20:40:25Z")

</div>

> [@Abbie](#):
>
> the Delve (go) debugger won’t properly drop into the debugger with Intel apps running on Arm make you feel that way?”

That describes my feelings perfectly. 🙂

---

<div class="post-metadata">

**Author:** ![bkeeney](https://ifnotnil.com/user_avatar/ifnotnil.com/bkeeney/32/225_2.png) [@bkeeney](https://ifnotnil.com/u/bkeeney)\
**Post date:** [23 January 2025 16:19 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/5 "2025-01-23T16:19:40Z")

</div>

> [@Abbie](#):
>
> Outside of that, intel mac for debugging may be the way to go, and are generally stupid cheap at the moment. Check a local university to see if they are tossing any, and/or better yet, get your company to pay you for these efforts too.

Well, we have Intel Macs currently and they gave us the shiny new M4 but our supporting libraries aren’t all Arm yet.

---

<div class="post-metadata">

**Author:** ![YogiYang](https://ifnotnil.com/letter_avatar_proxy/v4/letter/y/ecccb3/32.png) [@YogiYang](https://ifnotnil.com/u/YogiYang)\
**Post date:** [28 January 2025 12:06 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/6 "2025-01-28T12:06:03Z")

</div>

Check out this Git Repo.

> **[GitHub - sickcodes/Docker-OSX: Run macOS VM in a Docker! Run near native OSX-KVM...](https://github.com/sickcodes/Docker-OSX?tab=readme-ov-file)**
>
> Run macOS VM in a Docker! Run near native OSX-KVM in Docker! X11 Forwarding! CI/CD for OS X Security Research! Docker mac Containers.

This may help you also…

> **[GitHub - kholia/OSX-KVM: Run macOS on QEMU/KVM. With OpenCore + Monterey +...](https://github.com/kholia/OSX-KVM/tree/master)**
>
> master

---

<div class="post-metadata">

**Author:** ![Abbie](https://ifnotnil.com/user_avatar/ifnotnil.com/abbie/32/4533_2.png) [@Abbie](https://ifnotnil.com/u/Abbie)\
**Post date:** [28 January 2025 12:12 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/7 "2025-01-28T12:12:07Z")

</div>

The first one won’t work, but the second definitely might!

---

<div class="post-metadata">

**Author:** ![bkeeney](https://ifnotnil.com/user_avatar/ifnotnil.com/bkeeney/32/225_2.png) [@bkeeney](https://ifnotnil.com/u/bkeeney)\
**Post date:** [28 January 2025 14:12 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/8 "2025-01-28T14:12:09Z")

</div>

I’m curious why you think the 1st one won’t work.

---

<div class="post-metadata">

**Author:** ![Abbie](https://ifnotnil.com/user_avatar/ifnotnil.com/abbie/32/4533_2.png) [@Abbie](https://ifnotnil.com/u/Abbie)\
**Post date:** [28 January 2025 15:48 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/9 "2025-01-28T15:48:53Z")

</div>

If you are debugging Intel, you’d need stuff compiled on Intel to run on Intel.

Virtualizing it with Docker at best will just be like Rosetta with extra steps. You’re still running on ARM. It’s great for other situations tho. Utterly fantastic, and I’m glad it’s brought up because I have use cases.

But where QEMU can emulate x86 as if you were on it (to the best of it’s ability), there’s nothing in Docker that will unless I missed something large.

---

<div class="post-metadata">

**Author:** ![PatrickSalo](https://ifnotnil.com/user_avatar/ifnotnil.com/patricksalo/32/670_2.png) [@PatrickSalo](https://ifnotnil.com/u/PatrickSalo)\
**Post date:** [28 January 2025 23:32 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/10 "2025-01-28T23:32:11Z")

</div>

Another thing to consider is that x86 emulation under UTM can be pretty slow. Not as bad as say [Virtual PC](https://en.wikipedia.org/wiki/Virtual_PC) under PPC, but if running macOS is anywhere similar to my experience with x86 Windows under it, you might want to find another solution. I’m sure it’ll work for occasional use, but if it ends up being a daily driver, then I suspect you’ll end up pulling your hair out over the experience.

As Abbie mentioned, why not just supplement your M4 with an x86 Mac, maybe even a Mac mini that you can run headless and just screen share over to.

P.S. I’m M1 Pro over here and the M4 might have enough new “umph” to make the UTM experience better enough to be usable.

---

<div class="post-metadata">

**Author:** ![madamov](https://ifnotnil.com/user_avatar/ifnotnil.com/madamov/32/4677_2.png) [@madamov](https://ifnotnil.com/u/madamov)\
**Post date:** [10 February 2025 06:33 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/11 "2025-02-10T06:33:43Z")

</div>

It is so slow that it’s not usable. Recent version of Parallels has emulation technology preview, but I didn’t try it.

---

<div class="post-metadata">

**Author:** ![MarkusWinter](https://ifnotnil.com/user_avatar/ifnotnil.com/markuswinter/32/32_2.png) [@MarkusWinter](https://ifnotnil.com/u/MarkusWinter)\
**Post date:** [6 January 2026 22:25 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/12 "2026-01-06T22:25:41Z")

</div>

> [@PatrickSalo](#):
>
> P.S. I’m M1 Pro over here and the M4 might have enough new “umph” to make the UTM experience better enough to be usable.

Wait for the M5 - large jump in performance due to AI capabilities integrated into each core

---

<div class="post-metadata">

**Author:** ![npalardy](https://ifnotnil.com/user_avatar/ifnotnil.com/npalardy/32/10_2.png) [@npalardy](https://ifnotnil.com/u/npalardy)\
**Post date:** [6 January 2026 23:37 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/13 "2026-01-06T23:37:19Z")

</div>

So its just going to make shit up for predictive branching ?

😛

---

<div class="post-metadata">

**Author:** ![MarkusWinter](https://ifnotnil.com/user_avatar/ifnotnil.com/markuswinter/32/32_2.png) [@MarkusWinter](https://ifnotnil.com/u/MarkusWinter)\
**Post date:** [10 January 2026 02:41 UTC](https://ifnotnil.com/t/utm-on-m1-mac-emulating-intel-macos/4255/14 "2026-01-10T02:41:18Z")

</div>

> **[Meet the new M5 MacBook Pro: Smarter, faster, and AI-ready – Tech Advisory](https://www.techadvisory.org/2025/10/meet-the-new-m5-macbook-pro-smarter-faster-and-ai-ready/)**

> **[Apple Unleashes M5, the Next Big Leap in AI Performance for Apple Silicon](https://www.techpowerup.com/341930/apple-unleashes-m5-the-next-big-leap-in-ai-performance-for-apple-silicon)**
>
> Apple today announced M5, delivering the next big leap in AI performance and advances to nearly every aspect of the chip. Built using third-generation 3-nanometer technology, M5 introduces a next-generation 10-core GPU architecture with a Neural...
