Mac OS install on AMD Ryzen/INTEL (VMWare) Opencore - Improved Performance - Works with Sequoia / Sonoma / etc

I've found a solution to slow upload internet in the vm

Run the below command in macOS guests to turn off TSO

sudo sysctl -w net.inet.tcp.tso=0

To have any sysctl setting stick between restarts:

create a file /etc/sysctl.conf and add a below entry
net.inet.tcp.tso=0
 
codehubhq said:
I've found a solution to slow upload internet in the vm

Run the below command in macOS guests to turn off TSO

sudo sysctl -w net.inet.tcp.tso=0

To have any sysctl setting stick between restarts:

create a file /etc/sysctl.conf and add a below entry
net.inet.tcp.tso=0
Click to expand...

yes, great. I suggested exactly that in this post earlier:

Mac OS install on AMD Ryzen (VMWare) Opencore - Improved Performance - Works with Sequoia / Sonoma / etc

In the tests I've done with hyper-v active, it runs, but a list of numerous errors appears for about 2 or 3 minutes, then these errors stop and the machine continues to load the system. You can even install and run macOS. But it's even slower. Hyper-v off fixes all this. You then need to...
forum.amd-osx.com forum.amd-osx.com

It worked for me too.

And I put in the tutorial how to solve it.
 
  • Like
Reactions: codehubhq
Alexander10 said:
View attachment 14493
Click to expand...
1) Config vmware to 1 processor 4 cores (primary cause for the stuck right at the beginning as shown in your screenshot)
2) Disable hiper-v on windows
3) Patch vmware with unlock tool.
This patch releases the Apple Mac OS X version configuration option in VMWare under Virtual Machine Settings, Options, Apple Mac OS X:
use "macOS 14" when configuring your virtual machine.
4) Set Hard Disk (Sata): macOS_Opencore_1.0_4_cores.vmdk (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.

All these procedures are described in more detail in the tutorial.
 
Last edited:
Is it possible to expand the hard-disk after installation without loosing my data.
My disk is running very low, and I want to expand the hard-disk without loosing anydata on the vm.
Can this be done?
 
codehubhq said:
Is it possible to expand the hard-disk after installation without loosing my data.
My disk is running very low, and I want to expand the hard-disk without loosing anydata on the vm.
Can this be done?
Click to expand...
check this https://docs.vmware.com/en/VMware-W...UID-73BEB4E6-A1B9-41F4-BA37-364C4B067AA8.html

1720276136904.png

After increasing the volume in vmware, you also need to increase the size of the partition inside macos:

check this => https://www.lifewire.com/resize-mac...> Disk,divisions or deleting existing volumes.
 
Last edited:
  • Like
Reactions: codehubhq
After I changed the volume size, when I restarted the mac I noticed that the opencore boot changed to the other drive of opencore itself instead of the drive where macOS is installed.

To change and re-decorate the macOS drive just select the drive and press control + enter at the same time.
 
I have a Ryzen9 5950x and I'm getting the following error after many hours of installation
"A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. The shutdown state can be reached by incorrectly configuring the virtual machine, a bug in the guest operating system, or a problem in VMware Player."

1720346415539.png
 
Last edited:
iosDev said:
I have a Ryzen9 5950x and I'm getting the following error after many hours of installation
"A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. The shutdown state can be reached by incorrectly configuring the virtual machine, a bug in the guest operating system, or a problem in VMware Player."

View attachment 14503
Click to expand...
1) Config vmware to 1 processor 4 cores (primary cause for the stuck right at the beginning as shown in your screenshot)
2) Disable hiper-v on windows
3) Patch vmware with unlock tool.
This patch releases the Apple Mac OS X version configuration option in VMWare under Virtual Machine Settings, Options, Apple Mac OS X:
use "macOS 14" when configuring your virtual machine.
4) Set Hard Disk (Sata): macOS_Opencore_1.0_4_cores.vmdk (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.
All these procedures are described in more detail in the tutorial.

The installation process takes less than an hour depending on the configuration of your machine and the type of SSD installed.

There really is a problem with your vmware configuration or with windows itself as hyper-v is enabled.

Read the whole tutorial again and check what you haven't done correctly.

I recommend using sonoma 14.5 because there are still some bugs with Sequoia which is in beta.I
 
Last edited:
tucano2000 said:
1) Config vmware to 1 processor 4 cores (primary cause for the stuck right at the beginning as shown in your screenshot)
2) Disable hiper-v on windows
3) Patch vmware with unlock tool.
This patch releases the Apple Mac OS X version configuration option in VMWare under Virtual Machine Settings, Options, Apple Mac OS X:
use "macOS 14" when configuring your virtual machine.
4) Set Hard Disk (Sata): macOS_Opencore_1.0_4_cores.vmdk (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.
All these procedures are described in more detail in the tutorial.

The installation process takes less than an hour depending on the configuration of your machine and the type of SSD installed.

There really is a problem with your vmware configuration or with windows itself as hyper-v is enabled.

Read the whole tutorial again and check what you haven't done correctly.

I recommend using sonoma 14.5 because there are still some bugs with Sequoia which is in beta.I
Click to expand...
1720435542606.png
I can confirm that I have config set to
1) 1 processor 4 cores
2) Hyper-V disabled
3) Patched vmware
4) Set Hard Disk (Sata): macOS_Opencore_1.0_4_cores.vmdk (SATA 0:0)

These were the settings since the beginning and still caused that error.
I will try it again by using the macOS iso link you provided. (Do i need to use the VM Workstation Pro 17.5.2 link you provided specifically?)
I also noticed that you haven't mentioned anything about changing the vmware config like in this link. Could you confirm if this step isn't needed?
 
iosDev said:
View attachment 14511
I can confirm that I have config set to
1) 1 processor 4 cores
2) Hyper-V disabled
3) Patched vmware
4) Set Hard Disk (Sata): macOS_Opencore_1.0_4_cores.vmdk (SATA 0:0)

These were the settings since the beginning and still caused that error.
I will try it again by using the macOS iso link you provided. (Do i need to use the VM Workstation Pro 17.5.2 link you provided specifically?)
I also noticed that you haven't mentioned anything about changing the vmware config like in this link. Could you confirm if this step isn't needed?
Click to expand...

Try to create another virtual machine default. Vmware saves the state of some settings in the files of the folder where you chose to create the virtual machine and depending on what was done previously, this can be bad.

You shouldn't change the settings in the vmx file at all as mentioned in the link you provided because they only work on older versions of macOS that don't have Opencore loaded on boot.
 
tucano2000 said:
Try to create another virtual machine default. Vmware saves the state of some settings in the files of the folder where you chose to create the virtual machine and depending on what was done previously, this can be bad.

You shouldn't change the settings in the vmx file at all as mentioned in the link you provided because they only work on older versions of macOS that don't have Opencore loaded on boot.
Click to expand...
When I select this drive, It gets stuck on a loading screen for several hours and the progress bar doesn't move forward. The timer value keeps reducing and gets stuck on less than a minute remaining. As you can see I have disabled Hyper-V too. Anyi dea why this happens?

1720519624092.png1720519871578.png
 
iosDev said:
When I select this drive, It gets stuck on a loading screen for several hours and the progress bar doesn't move forward. The timer value keeps reducing and gets stuck on less than a minute remaining. As you can see I have disabled Hyper-V too. Anyi dea why this happens?

View attachment 14523View attachment 14524
Click to expand...

Try using VMware Workstantion Pro provided in a link in this tutorial and not VMware Player.

After patching vmware, close the application and reopen it to create the virtual machine from scratch using the settings in the tutorial.

This patch releases the Apple Mac OS X version configuration option in VMWare under Virtual Machine Settings, Options, Apple Mac OS X:

use "macOS 14" when configuring your virtual machine.

1720539425508.png
 
isquattopee said:
were you able to login to icloud on beta2? when I try I get 'Verification Failed', same for when I upgraded beta2 to beta3
Click to expand...
I also couldn't log in to iCloud, Apple Store and I get the same error in all beta versions of Sequoia.

I don't know exactly what Apple has changed in this version of macOS.

It seems that this occurs in macOS on virtualized systems only such as VMWare.

It could also be a problem with the network driver that VMware uses, vmxnet3.

Maybe it only happens with the beta version. Just a guess!

If you or anyone else finds out how to solve it, please let us know.

check this:
https://www.reddit.com/r/MacOS/comments/1e0xgah/macos_sequoia_sign_into_apple_account_in_vm
 
Last edited:
  • Like
Reactions: isquattopee
isquattopee said:
were you able to login to icloud on beta2? when I try I get 'Verification Failed', same for when I upgraded beta2 to beta3
Click to expand...
It seems that Apple really is limiting access in Virtual Machines and it would be a case of asking for this feature to be included even when the host is Windows:

forum.parallels.com

Sequoia Beta 3: Apple account login?

I have Mac Sequoia Beta 3 (24A5289g) running in a Parallels VM. I tried to sign in my Apple ID in the VM's Mac App Store and still get an "unknown...
forum.parallels.com forum.parallels.com

eclecticlight.co

Sequoia, virtualisation and Apple ID

How to create and configure a Sequoia beta to run in a virtual machine on an Apple silicon Mac, either in Sequoia or Sonoma, and a surprise in its features.
eclecticlight.co eclecticlight.co
 
tucano2000 said:
I also couldn't log in to iCloud, Apple Store and I get the same error in all beta versions of Sequoia.

I don't know exactly what Apple has changed in this version of macOS.

It seems that this occurs in macOS on virtualized systems only such as VMWare.

It could also be a problem with the network driver that VMware uses, vmxnet3.

Maybe it only happens with the beta version. Just a guess!

If you or anyone else finds out how to solve it, please let us know.

check this:
https://www.reddit.com/r/MacOS/comments/1e0xgah/macos_sequoia_sign_into_apple_account_in_vm
Click to expand...
thanks again for the macos14 vm, it works great. the only thing i wanted out of sequoia was the remote iphone controls but from reading through the links it seems like fully function macos15 vm's arent likely anytime soon
 
You must log in or register to reply here.
Top Bottom
✖
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.