M4 devices - VMs pre 13.4 fail to boot

Question

theevilbit OP

Created 1w

Replies 6

Boosts 6

Participants 4

Hi,

It seems that on M4 devices any virtual machine with macOS version older than 13.4 fail to boot, they stuck with a black screen. This is regardless of the virtualization software used (UTM, VirtualBuddy, Viable, etc...). After talking to many people everyone experiences the same.

At least for me, this is a massive limitation of the platform, I really hope this is a bug which can be fixed.

Thanks, Csaba

Answered by DTS Engineer in 814204022

I really hope this is a bug which can be fixed.

Rather than “hope”, it’s always best to file a bug.

And if you did file a bug, it’s always best to reference that in your discussions of the issue. Fortunately, I found the bug number (FB15774587) in Howard Oakley blog post.

I took a look at this bug and:

It’s definitely found it’s way to the right folks.
I don’t have any info to share as to when (or, being really timorous, if) it’ll be fixed.

I need a form moderator to change that (remove the accepted answer flag) for the reply above.

Bizarrely, we don’t have the ability to do that (r. 113568518). What I can do is recommend my answer, which is probably the right thing to do here anyway.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DuaneMIS OP

1w

I am also experiencing the same issues here. Am in desperate need of these virtual/emulated machines as we have legacy hardware that relie on specific O/S.

1

Answer 2

theevilbit OP

1w

Accepted Answer

Article by Howard Oakley on the subject: https://eclecticlight.co/2024/11/14/m4-macs-cant-virtualise-older-macos/

0

Answer 3

theevilbit OP

1w

Pressed "Accepted Answer" by mistake for the previous post. 🤦‍♂️ This is not an answer but additional information I wanted to add. I need a form moderator to change that (remove the accepted answer flag) for the reply above.

0

Answer 4

DTS Engineer OP

Apple

1w

Recommended

I really hope this is a bug which can be fixed.

Rather than “hope”, it’s always best to file a bug.

And if you did file a bug, it’s always best to reference that in your discussions of the issue. Fortunately, I found the bug number (FB15774587) in Howard Oakley blog post.

I took a look at this bug and:

It’s definitely found it’s way to the right folks.
I don’t have any info to share as to when (or, being really timorous, if) it’ll be fixed.

I need a form moderator to change that (remove the accepted answer flag) for the reply above.

Bizarrely, we don’t have the ability to do that (r. 113568518). What I can do is recommend my answer, which is probably the right thing to do here anyway.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1

Answer 5

theevilbit OP

1w

Hi Quinn,

Thanks for your reply! I was also advised to submit an enterprise bug report, which is FB15802246. Sorry I'm new to the forum, and bug reporting so wasn't sure what is the best way to proceed.

Fingers crossed for this being fixed.

Thanks, Csaba

0

Answer 6

DTS Engineer OP

Apple

10h

I don’t have any info to share as to when (or, being really timorous, if) it’ll be fixed.

I still don't have any timeline to share, but I had a quick chat with the engineering team and they confirmed that it is a bug and we do plan to fix it.

Oh, and it even made it into the release notes.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1