Page 1 of 1

After updating to MacOS Monterey 12.5 VM Restarts Constantly

Posted: 16. Sep 2022, 03:26
by NoDudi
Hi All,

I recently got into VirtualBox and X-Code, since I can't afford an iMac at the moment. Upon first installation of the VM, I had Mac OS BigSur and needed to update my MacOS to Monterey 12.5 in order to download X-Code.

When trying to display my code through the emulator in x-code or even just on the canvas, my VM restarts.

I was unable to upload the log since it exceeds upload limit so I have included a link to full log, I am not sure which you might need! I hope you can help me. I have tried to follow a few other form posts: Lowering base memory, Only using 1 CPUs, applying the following code in CMD: VBoxManage setextradata "nameofVM" "VBoxInternal/TM/TSCMode" "RealTSCOffset".

Thank you so much! :D

VBox.log = pastebin.pl/view/5c9dfe32
VBoxHardening.log = pastebin.pl/view/fcad4799
VBox.log.1 = pastebin.pl/view/4c3d93e4
VBox.log.2 = pastebin.pl/view/5c9a09de
VBox.log.3 = pastebin.pl/view/f9a30bad

Re: After updating to MacOS Monterey 12.5 VM Restarts Constantly

Posted: 16. Sep 2022, 03:54
by AndyCot
Hackintosh's are not supported.

Re: After updating to MacOS Monterey 12.5 VM Restarts Constantly

Posted: 16. Sep 2022, 15:19
by scottgus1
As Andy points out, a Mac guest is only allowed if the physical computer is real Apple hardware.
OSX guests on non-Apple hardware

I didn't look at your logs, because zipped logs fit using Upload Attachment.

If you are using an Apple computer, please start a new topic in the Mac Guests forum, with a zipped guest vbox.log, posted using the forum's Upload Attachment tab.

Re: After updating to MacOS Monterey 12.5 VM Restarts Constantly

Posted: 16. Sep 2022, 16:23
by mpack
I did look at his logs before locking the topic. He has a Microstar (MSI) motherboard and an AMD Ryzen processor, so definitely not Apple hardware.

p.s. The log in a couple of places identifies the CPU as an Intel i7-6700K, but that is clearly not correct. First because that MSI motherboard takes AMD Ryzens, and second because the log also says that AMD-v is being used.

Local copy of his first log: