Replies: 5 comments 11 replies
-
I believe this is due to the default VM settings being too high for M1 Macs to handle, this will be addressed once custom hardware configuration is implemented. |
Beta Was this translation helpful? Give feedback.
-
I also have an error when installing a macOS 13 VM, on a base Mac Studio and using both versions of VirtualBuddy and latest stable macOS 12 as host. I don't think it's the same error. I have many messages linked to the Virtualization framework in the Console : Let me know what I can do to help debug the installation process. Thanks @insidegui for your great work by the way ! 👍 |
Beta Was this translation helpful? Give feedback.
-
There is a workaround to make this work.
Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
Same problem here. M1 MBP |
Beta Was this translation helpful? Give feedback.
-
Latest release fixed all my issues, I will now hopefully create a video soon! |
Beta Was this translation helpful? Give feedback.
-
Due to the unknown network error issue I downloaded the latest Ventura IPSW from the Apple Developer website to install instead. However, that runs through the first parts of "preparing", and then hits this screen:
If I go to launch the VM after this state it appears to still be in DFU Mode (as iMazing Mini tells me by sensing a Mac is attached in DFU Mode). Trying to boot it results in this screen:
Ultimately I cannot get this VM Mac to start up in any mode. It does appear in the VirtualBuddy manager, as well as Apple Configurator and iMazing, but none let me get any further. Deleting the VM and starting over does not give me any better outcome. How can I get this to work better, or should I wait for an update that fixes the unknown network error? However, I am not sure that an install from that other method will work any better once it reaches this point.
Host hardware:
Mac mini M1
16 GB memory
2 TB SSD
Beta Was this translation helpful? Give feedback.
All reactions