F5F Stay Refreshed Software Operating Systems ERROR encountered during installation of Mac OS in VirtualBox.

ERROR encountered during installation of Mac OS in VirtualBox.

ERROR encountered during installation of Mac OS in VirtualBox.

8
8Noah8
Junior Member
14
06-12-2022, 04:22 PM
#1
The error code you're getting is the same one (minus the date code) that I get when trying to install the macOS Monterey Beta on my Hackintosh. I'm booting bare metal via OpenCore w/ a Ryzen 5 3600 and GTX 690, and it works fine with Big Sur, just not Monterey (I was using the dev build when I tried, then gave up). Just an FYI, the only NVidia graphics cards macOS has hardware acceleration for are Kepler cards (GTX 6xx/7xx, with the exception of the 750 Ti), and cards with the GK106 core have a weird VRAM leakage bug (experienced firsthand). This is being phased out in macOS Monterey but may be added back with a patch when Monterey is released. Additionally, unless you're finding a way to get it to use hardware acceleration, the experience is gonna suuuuuck. macOS uses hardware acceleration to speed up the GUI and unless you have it patched in in some way I do NOT recommend using macOS in a VM. Also, the thing about AMD CPUs being trickier is pretty much a lie now as long as you're using Ryzen. FX/Phenom/Athlon is its own thing and compatibility is spotty, but there's amazing work that's been done with running AMD CPUs.
8
8Noah8
06-12-2022, 04:22 PM #1

The error code you're getting is the same one (minus the date code) that I get when trying to install the macOS Monterey Beta on my Hackintosh. I'm booting bare metal via OpenCore w/ a Ryzen 5 3600 and GTX 690, and it works fine with Big Sur, just not Monterey (I was using the dev build when I tried, then gave up). Just an FYI, the only NVidia graphics cards macOS has hardware acceleration for are Kepler cards (GTX 6xx/7xx, with the exception of the 750 Ti), and cards with the GK106 core have a weird VRAM leakage bug (experienced firsthand). This is being phased out in macOS Monterey but may be added back with a patch when Monterey is released. Additionally, unless you're finding a way to get it to use hardware acceleration, the experience is gonna suuuuuck. macOS uses hardware acceleration to speed up the GUI and unless you have it patched in in some way I do NOT recommend using macOS in a VM. Also, the thing about AMD CPUs being trickier is pretty much a lie now as long as you're using Ryzen. FX/Phenom/Athlon is its own thing and compatibility is spotty, but there's amazing work that's been done with running AMD CPUs.

K
KrewDaplan
Junior Member
12
06-12-2022, 04:22 PM
#2
It sounds like you're exploring options for a hackintosh setup and have some hardware in mind. You're curious about dual booting Windows and whether an older AMD R7 260X GPU would impact performance.
K
KrewDaplan
06-12-2022, 04:22 PM #2

It sounds like you're exploring options for a hackintosh setup and have some hardware in mind. You're curious about dual booting Windows and whether an older AMD R7 260X GPU would impact performance.

O
OreoPro124420
Member
199
06-12-2022, 04:22 PM
#3
The R7 260X is supported, and it would accelerate stuff yes. However, unless something's changed, you'd need to switch which GPU you're plugged into (or just run separate cables between the 2060 and 260X to your monitor(s)). I've never done this personally, but this guide seems to know what it's doing: https://dortania.github.io/OpenCore-Inst...spoof.html Hackintoshing is possible with dual booting - I have Windows 10 and macOS Big Sur 11.4 running on the same system, though unless you like headaches please, PLEASE install macOS on a separate drive. I have Windows Boot Manager is on my Windows SSD, and OpenCore on my macOS SSD. It's currently set to use Windows Boot Manager though when I switch back and forth frequently I use OpenCore since that can boot Windows or macOS.
O
OreoPro124420
06-12-2022, 04:22 PM #3

The R7 260X is supported, and it would accelerate stuff yes. However, unless something's changed, you'd need to switch which GPU you're plugged into (or just run separate cables between the 2060 and 260X to your monitor(s)). I've never done this personally, but this guide seems to know what it's doing: https://dortania.github.io/OpenCore-Inst...spoof.html Hackintoshing is possible with dual booting - I have Windows 10 and macOS Big Sur 11.4 running on the same system, though unless you like headaches please, PLEASE install macOS on a separate drive. I have Windows Boot Manager is on my Windows SSD, and OpenCore on my macOS SSD. It's currently set to use Windows Boot Manager though when I switch back and forth frequently I use OpenCore since that can boot Windows or macOS.

O
OddAlec
Junior Member
44
06-12-2022, 04:22 PM
#4
Have you checked for fixes? I'm still facing the same issue despite testing all other Intel settings. No success so far! It's frustrating. My system is using a Ryzen 9 3900x.
O
OddAlec
06-12-2022, 04:22 PM #4

Have you checked for fixes? I'm still facing the same issue despite testing all other Intel settings. No success so far! It's frustrating. My system is using a Ryzen 9 3900x.

S
shadowbacca
Member
226
06-12-2022, 04:22 PM
#5
Open CD in the specified path and adjust VM settings using VBoxManage. Update CPUID, extradata, and CPU profile as needed. Apply changes and confirm success in the command prompt.
S
shadowbacca
06-12-2022, 04:22 PM #5

Open CD in the specified path and adjust VM settings using VBoxManage. Update CPUID, extradata, and CPU profile as needed. Apply changes and confirm success in the command prompt.

C
Captin_sponge
Member
175
06-12-2022, 04:22 PM
#6
The issue was resolved after fixing the CPU profile for Intel. Thank you!
C
Captin_sponge
06-12-2022, 04:22 PM #6

The issue was resolved after fixing the CPU profile for Intel. Thank you!