Mac OS install on AMD Ryzen/INTEL (VMWare) Opencore - Improved Performance - Works with Sequoia / Sonoma / etc
- Thread starter tucano2000
- Start date
Try using OC Auxiliary Tools and update the kexts and use opencore 1.0.4. Then change the serial and synchronize and save.
That should work.
See this:
Excellent News !!!Hello Friend,
With the help of your customised OpenCore, my Windosh VMWare VM installation is a complete success! I am installing XCode from within macOS 14 VM.
Another question is -
Do you also use GenSMBIOS tool and OpenCore plist to configure your virtual iMac specification?
GitHub - corpnewt/GenSMBIOS: Py script that uses acidanthera's macserial to generate SMBIOS and optionally saves them to a plist.
Py script that uses acidanthera's macserial to generate SMBIOS and optionally saves them to a plist. - corpnewt/GenSMBIOSgithub.com
I use OC Auxiliary Tools to edit and configure the opencore config.plist file.
Releases · ic005k/OCAuxiliaryTools
Cross-platform GUI management tools for OpenCore（OCAT） - ic005k/OCAuxiliaryTools
github.com
You can use this tool to edit this file and configure new SIM Bios and use another one...
Last edited:
Thanks a lot !! tucano2000 for your nice tutorial, I followed it and successfully upgraded to Sequoia 15.4.1, it runs very smoothly on 8 cores and 16 GB RAM. The only issue is that sometimes when I shutdown the VM it gets stuck & I have to force power it off. But it is not a big deal if there's no workaround or a fix.
Just wondering if I can rename the Graphics "Display 128mb" under "About this Mac" to my liking just for cosmetic reason. I have tried different methods with no luck.
Last edited:
@tucano2000 Thanks so much for that tip! SN Changed successfully. Sadly, iMessage doesn't work. Facetime worked for a bit then it died for some reason? I used to be able to load imesasge, but messages would fail to deliver "not delivered" - after a while, iMessage stopped opening entirely. Login loop. Any ideas? I know I followed the opencore sn guide correctly. thanks.
I remember solving this on my old laptop by using horndis's android tether solution. I wonder if this will work here. Gonna test and let you guys know
I remember solving this on my old laptop by using horndis's android tether solution. I wonder if this will work here. Gonna test and let you guys know
iMessage works on a 15.2 ISO (it may not be the one linked here, I think it was the one from archive.org). I found some ISO online for 15.4 and iMessage didn't work on it (failed to login). I haven't tried the 15.4 Beta ISO in this thread but I am pretty sure people said iMessage works on it, have you tried that one?
Excellent News !!!
I use OC Auxiliary Tools to edit and configure the opencore config.plist file.
Releases · ic005k/OCAuxiliaryTools
Cross-platform GUI management tools for OpenCore（OCAT） - ic005k/OCAuxiliaryTools
You can use this tool to edit this file and configure new SIM Bios and use another one for your virtual machine:
View attachment 12145
Editing SMBIOS:
View attachment 12146
Before you can edit it, you need to mount the OPENCORE partition. This partition contains the EFI directory and, inside it, the OC directory, where the config.plist file is located, which must be opened with OC Auxiliary Tools:
View attachment 12147
Use ESP MOUNTER PRO or another application to mount the OPENCORE partition:
When opening and editing the config.plist file, be careful because an error can make the machine unbootable.
I create 2 virtual machines here and open the opencore vmdk file from another machine as a secondary drive to correct errors in config.plist in case it is no longer bootable:
View attachment 12144
You can edit OPENCORE from the virtual machine itself without having to use 2 machines. But you must make sure you know what you're doing. Editing SMBIOS, for example, and choosing a Mac that is not supported by macOS Sonoma can cause the system to stop booting.
As far as I know, Macs manufactured after 2019 support macOS Sonoma.
stuck here... says im not connected to internet once i press continue leaving all else blank*** First of all, don't make any changes to the vmware .vmx file. It is recommended that you create a new virtual machine from scratch so that it recreates this file by default and without any changes.
*** Use VMWare Workstation Pro version at the link provided in the tutorial. (If you install it, you will have to make a new Patch as described)
*** Enable AMD-V or INTEL VT (Virtualization Technology) in BIOS. (you should research how to do this on your machine)
1) First you need to download VMWare:
- VM Workstation Pro 17.6.3: (NOW IS FREE FOR ALL USERS)
- Download Unlocker to patch VMWare:
11.23 MB file on MEGA
mega.nz
- New version of unlocker tested on VMWare Worstation Pro
- After installing VMWare close it.
Extract all the unlocker files into a folder, open the command prompt (terminal) in administrator mode and run "win-install.cmd".
This patch releases the Apple Mac OS X version configuration option in VMWare under Virtual Machine Settings, Options, Apple Mac OS X:
use "macOS 15" when configuring your virtual machine:
View attachment 16726
2) Also download an ISO of macOS:
Sonoma 14.6.1
Link1: https://fastupload.io/b2b892fd799bc081
Sequoia 15.2
Link1: https://data.pyenb.network/macOS/isos/torrents/macOS Sequoia 15.2_24C101.iso.torrent
Use uTorrent app to download with this file.
macOS Sequoia 15.4 Beta
Link: https://fastupload.io/007270f6bd13ec49
Sequoia is now working with Apple's login services (iServices). WMHide.kext and Lilu.kext 1.7.0 have been incorporated into the VMDK image Opencore updates.
3) Download a small VMWare disk image file:
INTEL PROCESSORS ONLY
This version only works with INTEL processors with any numbers of cores avaliable in your machine (test to better performance):
Download New Version of VMWare disk image file Here: OPENCORE 1.0.4
https://fastupload.io/549ac2595cf2fae3 (FOR INTEL MACHINES ONLY)
This file contains Opencore 1.0.4 on an EFI partition and should be chosen as a disk image on the SATA 0:0 drive in the VMWare settings. It should always be used that way.
AMD PROCESSORS ONLY
This version only works with Ryzen processors with 4 cores or more
Download New Version of VMWare disk image file Here: OPENCORE 1.0.4 - 4 cores
https://fastupload.io/06597416c3ed3e50 (FOR AMD MACHINES ONLY)
This file contains Opencore 1.0.4 on an EFI partition and should be chosen as a disk image on the SATA 0:0 drive in the VMWare settings. It should always be used that way.
OR DOWNLOAD:
This version only works with Ryzen processors with 8 cores or more
Download New Version of VMWare disk image file Here: OPENCORE 1.0.4 - 8 cores
https://fastupload.io/e65c07a2bc6c88c2 (FOR AMD MACHINES ONLY)
This file contains Opencore 1.0.4 on an EFI partition and should be chosen as a disk image on the SATA 0:0 drive in the VMWare settings. It should always be used that way.
OR DOWNLOAD:
This version only works with Ryzen processors with 16 cores or more
Download New Version of VMWare disk image file Here: OPENCORE 1.0.4 - 16 cores
https://fastupload.io/4c52e6fb0eb1aaba (FOR AMD MACHINES ONLY)
This file contains Opencore 1.0.4 on an EFI partition and should be chosen as a disk image on the SATA 0:0 drive in the VMWare settings. It should always be used that way.
VMWare settings FOR AMD/INTEL:
a) Memory:
8GB (recommended 50% of your host machine)
b) Processors:
Intel: Usually 50% of your machine's Intel processor cores.
AMD 4 cores (if you are using the VMWare disk image file with 4 cores)
AMD 8 cores (if you are using the VMWare disk image file with 8 cores)
AMD 16 cores (if you are using the VMWare disk image file with 16 cores)
View attachment 16727
c) Hard Disk (Sata):
macOS_Opencore_1.0.4_4_cores.vmdk or
macOS_Opencore_1.0.4_8_cores.vmdk or
macOS_Opencore_1.0.4_16_cores.vmdk or
macOS_Opencore_1.0.4_intel_.vmdk
in (SATA 0:0) Should always be the first boot drive.
In newer versions of WMWare choose "Keep existing format" if you are asked when adding the image of this drive.
View attachment 14254
4) Hard Disk 2 (Sata): This drive is where macOS will be installed. Any size you see fit.
5) CD/DVD (SATA): Use ISO image file (Ex. Sonoma.iso, Sequoia.iso, etc.)
View attachment 12112
6) USB Controller 3.1.
View attachment 12113
7) Network Adapter: Bridged Automatic.
View attachment 16728
During installation, only erase or format the macOS installation drive you created using Disk Utility. Never do this on the OPENCORE drive (it must remain untouched):
View attachment 12114
View attachment 12115
View attachment 12116
View attachment 12117
EDIT:
****************************************************************************** A T T E N T I O N ********************************************************************************
8) (IT GREATLY IMPROVES PERFORMANCE AND CORRECTS ERRORS
In order to correct the “errors” during start-up, which in spite of everything works.... and also to correct the performance and reduce the “slowness” of the virtual machine, you should turn off the windows hypervisor. To do this, use the tip below:
- In Windows, click on Start and search for Command Prompt
- Right-click Command Prompt and then click Run as administrator
- If the User Account Control dialog box appears, confirm that the action shown is the one you want and click Continue
- Then type: bcdedit /set hypervisorlaunchtype off (and Hit enter)
- Then type: reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity” /v “Enabled” /t REG_DWORD /d 0 /f
- Press enter again.
- Restart the computer
- It is also recommended to disable the "Memory Integrity Checks" in Windows to improve performance.
- Install VMWare Tools to change the resolution. It comes with VMWare Workstation, I don't remember if VMWare Play has VMWare Tools.
- You can only change the resolution within MacOS. Ex: 1600x1100. To do this, type in the terminal :
sudo /Library/Application\ Support/VMware\ Tools/vmware-resolutionSet 1600 1100
Note: In VMWare's Display settings you need to set the resolutions higher than or equal to the ones you'll be using in macOS.
***********************************************************************************************************************************************************************************
=================================
Issues:
=================================
Crash, Stopped during installation or Repetitive errors when loading
If not then kindly mention the easiest guide to build a customized efi for the target machine with every basic, i don't know anything about efi except that its needed
Did you select the correct network option when installing the VM ware software? Section 7 of the guide.
Here is a link to the Dortania Ryzen guide
is it the solution about the metal support? i have opened but i think i'm unable to find some information about it
because i got an issue like this while running compose multiplatform, i got no idea about it
but while running swiftui apps on emulator, it's running smoothly
i'm on AMD Ryzen 7 8845hs rtx 4050 acer nitro v16 RAM16GB SSD Kingston 512GB Using VMWare Workstation Pro 17
oh anyway, is there any solution to use apple's wallpaper? i'm pretty confused a bit about it, it always goes blank black wallpaper
Have a read of this post see if the fix offered fixes the screensaver issue.
You will never get Metal support in your VM. You also can't install macOS as a bare metal install with the configuration of your system. Other than using some of the fixes offered in the early posts in this thread you are going to have to put up with the poor resolution etc.
When I first got macOS, I had this problem with a white background (wallpaper) in the system background. But you have to go into the macOS settings and click on Wallpaper and then deactivate the Show as screen saver option. Then choose a wallpaper you like.
You will never get Metal support in your VM. You also can't install macOS as a bare metal install with the configuration of your system. Other than using some of the fixes offered in the early posts in this thread you are going to have to put up with the poor resolution etc.
Hello,
First thanks you for everything it works !
I have the same problem impossible to access internet. I am in bridged (I have followed every steps) but yeah same as him I was ask to enter information for connecting to internet ... So I skipped. But now if I want to be able to use this VM I need internet. (build with XCode existing project etc)
So perhaps do you know how to help me?
For information I am on Sonoma 14.7.6 (an ISO a friend give me). My computer is connect via Ethernet (I have a WIFI adapter too but I'm not using it).
Last edited:
Not sure what could be the problem, if you set it correctly in Bridged mode.
Does the Ethernet work in the bare-metal OS?
Does the Ethernet work in the bare-metal OS?
In Windows, check if the vmware network adapter is enabled or if you have made any previous changes to its default configuration.
If you haven't, try uninstalling vmware and then removing this network configuration so that the next time you install it, it will return to the default configuration.
After that, follow the tutorial and check that your .vmx file is using the vmxnet3 driver in bridge mode.
My vmware network adapter is enabled and working.
I have tried to go with NAT and not bridged and now it's working ... So I will stay this way ahaha.
Thanks again
But I have a question (or more than one). I'm using the last version of the tuto so everything should be fine I guess but ..
I'm trying to have a MacOS VM because I need XCode to build for IOS etc. So I need to upgrade from Sonoma to Sequoia. Right now is there any problem with ICloud account etc after the upgrade ?
And lastly .. There is no new opencore version right now so it's fine but I have read the other page and I didn't found where you explain how exactly we are suppose to update our opencore version, we just have to replace the file use in the little hard disk by the new one? And the kexts files you often talk about, what is it and how to update/add if needed ?
Last edited:
Hi, I'm glad you've managed to enable the internet with NAT. It's also possible, but it's more complicated to configure and I don't know if you use a dynamic ip network or a proxy. The most important thing is that it worked.
If you need to upgrade, you just need to change the driver where opencore is stored in the vmdk files according to your machine.
If you don't do this, Sequoia will fail all Apple login services including iCloud.
The new version of the vmdk image file that I've provided already comes with the kexts needed to support Sequoia and the kexts that hide the virtual machine so that Apple's login services work.
If you have the space, I advise you to make a copy of the vmdk storage unit where Sequoia is located so that you can upgrade it in case something fails.
To make the copy, find the largest vmdk file where all your virtual machine files are and copy it.
To change the opencore vmdk I mentioned earlier, just edit the virtual machine and change this file, remembering that it must be set to SATA 0:0 (the first boot drive).
