Mac OS install on AMD Ryzen/INTEL (VMWare) Opencore - Improved Performance - Works with Sequoia / Sonoma / etc
- Thread starter tucano2000
- Start date
I tried several times with the instruction from 1st message of this thread.
1. install 14.5, sign in to iCloud account (all works fine), upgrade to 15.Ñ….Ñ… and iCloud account stop work imediatly.
2. install 14.5, sign in to iCloud account (all works fine), upgrade to latest 14.x (14.7.4 at the moment) version, after upgrade to 15.Ñ….Ñ… and iCloud account stop work imediatly.
What am I doing wrong and how it could be fixed?
p.s. VMWare Workstation 17.6.2 with VMWare tools, Opencore 1.0.2 4 cores
Last edited:
Hello together,
I'm also new here and I carried out this installation as described. After trying a few other instructions where I was never able to log in with the Apple ID.
My hardware is a PC with 32 GB RAM and an AMD Ryzen 7 (2700X).
VM settings:
8 CPUs, 8 GB RAM and HD 100 GB.
With this installation I had to "restart" the VM four or five times but then the installation went through. Then I had to adjust the config.plist with the OC Auxiliary Tools. Then I was able to log in with the Apple ID.
But I still have the following problems:
1) When shutting down MAX OSX a black screen appears and freezes!
2) The performance is very poor, does anyone have any ideas?
As I don't speak English, the text was created using a translation program.
I'm also new here and I carried out this installation as described. After trying a few other instructions where I was never able to log in with the Apple ID.
My hardware is a PC with 32 GB RAM and an AMD Ryzen 7 (2700X).
VM settings:
8 CPUs, 8 GB RAM and HD 100 GB.
With this installation I had to "restart" the VM four or five times but then the installation went through. Then I had to adjust the config.plist with the OC Auxiliary Tools. Then I was able to log in with the Apple ID.
But I still have the following problems:
1) When shutting down MAX OSX a black screen appears and freezes!
2) The performance is very poor, does anyone have any ideas?
As I don't speak English, the text was created using a translation program.
Hello,
Unfortunately, you can't see from the screenshot which files you want to start and whether you have the Unlocker installed. Can you take individual screenshots of your settings in VMWare?
Like this, for example:
I had the same problem. The reboot did not help, then I opened the MacOS 14.VMX file with a notebook and wrote at the very bottom - smc.version = "0" and now I have no hangs at this step
Thank you, but I somehow successfully installed it.
Last edited:
tucano2000
If you want to use Sequoia with login services, you need to install Sonoma 14.5 and do a system update to Sequoia.Hello,
I first installed Sonoma 14.5 as described and logged in with the Apple ID. Then I updated to Sequoia. But now I am no longer logged in correctly with the Apple ID and am being asked to log in again.
When I log out and log in again I get the following error:
Is there a solution to this?
Why?
The whole point of installing Sonoma 14.5, and setting up iCloud before upgrading to Sonoma is that you have the iCloud account activated on the system while upgrading to Sequoia. So it retains its active status in Sequoia. There is no reason to log-out of iCloud before, during or after the macOS update.
Logging out of iCloud will have caused the issue you are currently facing.
You may need to reinstall Sonoma 14.5, activate your iCloud account in Sonoma and update to Sequoia again to get over this issue.
If the Sequoia installer asks you to sign in to your iCloud account as part of the update, select the 'SKIP' option. Your iCloud account should still be active when you arrive on the Sequoia desktop, mine was.
The whole point of installing Sonoma 14.5, and setting up iCloud before upgrading to Sonoma is that you have the iCloud account activated on the system while upgrading to Sequoia. So it retains its active status in Sequoia. There is no reason to log-out of iCloud before, during or after the macOS update.
Logging out of iCloud will have caused the issue you are currently facing.
You may need to reinstall Sonoma 14.5, activate your iCloud account in Sonoma and update to Sequoia again to get over this issue.
If the Sequoia installer asks you to sign in to your iCloud account as part of the update, select the 'SKIP' option. Your iCloud account should still be active when you arrive on the Sequoia desktop, mine was.
hi, I'm using VMWare with sequoia OS on a ryzen 2600 with a 5700 xt.
when using both android studio and xcode i get a metal is not supported, do you know how to fix it?
when using both android studio and xcode i get a metal is not supported, do you know how to fix it?
This normal on a VM installation.
If you want metal support, install macOS to a spare drive but as a standalone OS, not as a VM.
If you want metal support, install macOS to a spare drive but as a standalone OS, not as a VM.
do you know if this happens only with vmware or with quemu and virtualbox also happens?
Or the only solution would be to install macOS on a free disk but as a standalone OS?
As far as I am aware, having only used Exsi, a bare metal installation of macOS is the only way to have Metal support and full graphics acceleration in macOS.
You would have to ask someone who has used the other two VM options as to whether they work any better and provide Metal support to their macOS VM’s.
You would have to ask someone who has used the other two VM options as to whether they work any better and provide Metal support to their macOS VM’s.
VMware 17.5 macOS Sequoia 15.3.1
Hi everyone, how can I set up vmware to make macOS think it is running on a real physical device instead of a vmware virtual machine? Because when I try to log in with my apple ID, it keeps saying 'An unknown error occurred', just like they said in the forum (https://developer.apple.com/forums/thread/756832).
Hi everyone, how can I set up vmware to make macOS think it is running on a real physical device instead of a vmware virtual machine? Because when I try to log in with my apple ID, it keeps saying 'An unknown error occurred', just like they said in the forum (https://developer.apple.com/forums/thread/756832).
