Page 1 of 1
Forum

Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!

Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.

Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!



VMWare on Windows -...
 
Share:
Notifications
Clear all

[Solved] VMWare on Windows - How to create a macOS virtual machine on VMWare Workstation Player 17

15 Posts
6 Users
0 Reactions
10.5 K Views
 Hans
(@hans)
Famed Member Admin
Joined: 11 years ago
Posts: 2717
Topic starter  

I occasionally need to test a few things for macOS, for which I usually use one of my Mac's.
However when needing a virtual machine to test an older macOS, I find a macOS Virtual Machine to run really slow on a Mac. Even a Mac Pro.

Since I have a nice gaming laptop at my disposal (Asus ROG G713, AMD 6900HZ CPU and Nvidia 3080 GPU), I just wanted to give it a try to install a macOS VM on my Windows computer.

This worked for me, even with an AMD CPU:

1. Install VMWare WorkStation Player (I used v17) - it's free for non-commercial use.

2. Get a macOS ISO file. I used the method described here - since downloading ISO files from others can be questionable.

3. Download and run Auto-Unlocker which add “macOS” as an option when creating a new Virtual machines.

4. Open VMWare Workstation Player, and create a new virtual machine - you can select macOS now, and select the macOS ISO file.

 

A few things you should pay attention to:

Customize Virtual Machine specs

I usually customize the setting for my VM's, and in this case:

Memory to at least 8192 Kb, and
CPU cores to 8 (depending on your CPU).

 

AMD CPU's

AMD CPU's are NOT supported by macOS, and during initial boot you'll get a message

The CPU has been disabled by the guest operating system. power off or reset the virtual machine.

In short: AMD is not supported. Close the virtual machine and locate the VMX file of this new virtual machine.

Find the line that looks like this:

virtualHW.version = "16"

Add this right behind that line:

smc.version = "0"
cpuid.0.eax = "0000:0000:0000:0000:0000:0000:0000:1011"
cpuid.0.ebx = "0111:0101:0110:1110:0110:0101:0100:0111"
cpuid.0.ecx = "0110:1100:0110:0101:0111:0100:0110:1110"
cpuid.0.edx = "0100:1001:0110:0101:0110:1110:0110:1001"
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001"
cpuid.1.ebx = "0000:0010:0000:0001:0000:1000:0000:0000"
cpuid.1.ecx = "1000:0010:1001:1000:0010:0010:0000:0011"
cpuid.1.edx = "0000:0111:1000:1011:1111:1011:1111:1111"
smbios.reflectHost = "TRUE"
hw.model = "MacBookPro14,3"
board-id = "Mac-551B86E5744E2388”

 

Intel CPU's

Untested, but it seem that you will need to apply a patch to the VMX file as well, telling it that you're running on a Mac.

Find the line that looks like this:

virtualHW.version = "16"

Add this right behind that line:

smc.version = "0"
smbios.reflectHost = "TRUE"
hw.model = "MacBookPro14,3"
board-id = "Mac-551B86E5744E2388"

 

5. Run the Apple install - takes about 15-25 minutes depending on your hardware.

At initial setup: Select "Disk Utility" first to select and erase the VMWare disk - mine was the first one listed under "Internal", called "VMware Virtual SATA Hard Drive Media". Select that disk, click "Erase", give it a name, but keep the other default values (APFS/GUID Partition map). 

Once erased (use default values), close "Disk utility" and select "Install macOS Monterey" (or which ever version you are installing).

The initial image is very laggy during setup, which can be due to the number of cores or memory, but more likely because of the video driver (or lack thereof).

6. Install the VMWare Tools for your macOS VM (requires VM reboot)

Now by default, VMware Workstation Player will NOT come with the macOS VMware tools. So you will need to go find your own.
If you have VMWare Fusion on a Mac, then you can find the ISO file here (recommended):

/Applications/VMware Fusion.app/Contents/Library/isoimages/x86_x64/darwin.iso

Or grab this copy (which may be very outdated by the time you read this)

In VMware Workstation Player, open the "Player" - "Manage" - "Virtual Machine Settings"  (CTRL+D).

Go tot he CD/DVD settings, and browse for the "darwin.iso".

Go back to your macOS VM, and if the "VMware tools" disk icon does not appear, from the menu "Player" - "Removable devices" - "CD/DVD" - "Connect".
This should now show the VMware Tools - which you can now install.


   
ReplyQuote
(@Anonymous)
Joined: 1 second ago
Posts: 0
 

I'm using the non commercial vmware player 17 but I cannot get Ventura to work.  I am on an AMD 5750X as well.  

The player will not process these two of the four lines above

smbios.reflectHost = "TRUE

board-id = "Mac-551B86E5744E2388”

It does allow for the other two.  If keep those lines it says vmx file is corrupt.

I have tried literally everything I can find to get Ventura working on VMware Player 17 on AMD on Windows 11.  I have Monterey working but I need xcode which requires Ventura/OS13.  

When I do an upgrade inside a monterey machine, after reboot, it crashes almost immediately.  "there is a problem with..." And it just boot loops until it gives the apple.com/support/startup (or something like that).  If I do an install off of a downloaded from apple iso, it also crashes.  Holding down shift just makes it freeze at the Apple logo and as soon as I lift up, it crashes.

Do you have any advice for this problem?  I'm really stuck and I can't find any other tips.

Thank you!

jp

 

This post was modified 1 year ago by Anonymous

   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 11 years ago
Posts: 2717
Topic starter  

I'm using the same VMWare Workstation version and installed Monterey this way (like you did).

I did some testing and ran into the same issue with Ventura - seems a known issue. See also Ventura related open issues for Auto-unlocker - even though this should probably not be seen as a Auto-unlocker issue, after all, Auto-unlocker after all only "unlocks" certain macOS versions as a target, but isn't made to work around hardware limitations like an AMD CPU.

 

Note: If I look at the code you pasted:

smbios.reflectHost = "TRUE

board-id = "Mac-551B86E5744E2388”

Then I see that the "smbios" line misses a closing double quote. Maybe a copy/paste mistake, or maybe the reason why it says the file is corrupt?

 

I did find this description, suggesting the VMX text below would work, but that fail when upgrading from Monterey to Ventura.
Haven't had time yet to create an ISO image to do a clean install ... downloading Ventura as we speak, and will try later today to install from scratch.

(found and ISO of Ventura here - but I really prefer an ISO extracted from an Apple install, so I know it's legit)

board-id.reflectHost = "FALSE"
board-id = "Mac-AA95B1DDAB278B95"

hw.model.reflectHost = "FALSE"
hw.model = "MacBookPro19,1"
serialNumber.reflectHost = "FALSE"
serialNumber = "C01234567890"

smc.version = "0"
cpuid.0.eax = "0000:0000:0000:0000:0000:0000:0000:1011"
cpuid.0.ebx = "0111:0101:0110:1110:0110:0101:0100:0111"
cpuid.0.ecx = "0110:1100:0110:0101:0111:0100:0110:1110"
cpuid.0.edx = "0100:1001:0110:0101:0110:1110:0110:1001"
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001"
cpuid.1.ebx = "0000:0010:0000:0001:0000:1000:0000:0000"
cpuid.1.ecx = "1000:0010:1001:1000:0010:0010:0000:0011"
cpuid.1.edx = "0000:0111:1000:1011:1111:1011:1111:1111"
smbios.reflectHost = "TRUE"

 


   
ReplyQuote
(@Anonymous)
Joined: 1 second ago
Posts: 0
 

@hans You can get an ISO from Apple.  Basically a recovery ISO that will then download directly from apple.

 

I've tried so many different variations of the vmx file mods and nothing works.  It's just the same thing.  Installation goes ok, then boot loop.  

I'm wondering if this is a specific to AMD issue?  Do other people with AMD procs get Ventura running?


   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 11 years ago
Posts: 2717
Topic starter  

I'm very sure this is an issue combo of AMD CPU and macOS Ventura, and from what I found is that others experience the same issue with AMD/Ventura. 😞 

As for getting an ISO file: I extract the ISO file from the app bundle Apple has in the App Store.
I thought Apple had dropped ISO files, except for very old macOS version?


   
ReplyQuote
(@Anonymous)
Joined: 1 second ago
Posts: 0
 

I found it! It worked for me!

i made it work on a amd ryzen 5 5600

to get it to work i had to put the

cpuid.0.eax = "0000:0000:0000:0000:0000:0000:0000:1011"
cpuid.0.ebx = "0111:0101:0110:1110:0110:0101:0100:0111"
cpuid.0.ecx = "0110:1100:0110:0101:0111:0100:0110:1110"
cpuid.0.edx = "0100:1001:0110:0101:0110:1110:0110:1001"
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001"
cpuid.1.ebx = "0000:0010:0000:0001:0000:1000:0000:0000"
cpuid.1.ecx = "1000:0010:1001:1000:0010:0010:0000:0011"
cpuid.1.edx = "0000:0111:1000:1011:1111:1011:1111:1111"

at the top and the  the smc.version = "0" underneath the floppy0.present = "FALSE"!

we will see if it installs

never mind dosent work just keeps crashing

 

 

This post was modified 1 year ago 4 times by Anonymous

   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 11 years ago
Posts: 2717
Topic starter  

Awesome!!!!! 👍 

Thanks for sharing - I'll give it a try in the next few days to see what happend on my Ryzen 6900!

Never mind - just now seeing your crashing comment haha ... bummer! 😢 


   
ReplyQuote
(@Anonymous)
Joined: 1 second ago
Posts: 0
 

Posted by: @hans

I'm using the same VMWare Workstation version and installed Monterey this way (like you did).

I did some testing and ran into the same issue with Ventura - seems a known issue. See also Ventura related open issues for Auto-unlocker - even though this should probably not be seen as a Auto-unlocker issue, after all, Auto-unlocker after all only "unlocks" certain macOS versions as a target, but isn't made to work around hardware limitations like an AMD CPU.

 

Note: If I look at the code you pasted:

smbios.reflectHost = "TRUE

board-id = "Mac-551B86E5744E2388”

Then I see that the "smbios" line misses a closing double quote. Maybe a copy/paste mistake, or maybe the reason why it says the file is corrupt?

I'm a bit late to the party but the reason the vmx file gets corrupt is because the last quotation mark in

board-id = "Mac-551B86E5744E2388”

Is not a normal " but some kind of weirdo cursive kind, they are not the same. Just change that to a normal one and the vmx file will no longer be corrupt.

Posting this 6 months later in case it might help someone 😉 

 


   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 11 years ago
Posts: 2717
Topic starter  

6 months later or not: still a good and contributing comment! 👍 

I've updated the double quote, thanks for letting me know!
Every now and the my computer decides to use "smart quotes", and not even consistently. Disabled that feature now 😊 


   
ReplyQuote
(@Anonymous)
Joined: 1 second ago
Posts: 0
 

Shame, I'm the one that posted about getting it to install. if a workaround happened probably would do it for Sonoma too..


   
ReplyQuote
(@Anonymous)
Joined: 1 second ago
Posts: 0
 

any more updates on this?

I have a Ryzen 9 computer and need to use garageband to finish a record after my macbook ssd fried, but the appstore says I need 13.5 or later to run it- I was able to get 11 running fine, but 13 and 14 crash.  

Apple won't let me have any older versions of Garageband- even if I replaced my SSD, it's an old intel mac and I don't think it will run anything past 10.15


   
ReplyQuote
(@Anonymous)
Joined: 1 second ago
Posts: 0
 

ok, I have Garageband working, I was able to install the OS my old MacBook was running (10.5) and go to my download history in the App Store and find the old version of Garageband


   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 11 years ago
Posts: 2717
Topic starter  

No updates on my end ... sorry 😞  
With Apple abandoning Intel hardware, this may get even more difficult in the future.
Myabe there is an option to achieve this with OpenCore (did find this article, but have not fully read it yet).

Good tip on finding old downloads! 👍 


   
ReplyQuote
(@juanfernandesp)
New Member
Joined: 4 weeks ago
Posts: 2
 

@hans Hey man, big thanks on this, it helped me out install it on my amd rig, but I'm running into a problem that when I attempt to install something it says my disk hasn't enough space

however I do know I still have plenty of space left and I checked it at my main disk folder


   
ReplyQuote
 Hans
(@hans)
Famed Member Admin
Joined: 11 years ago
Posts: 2717
Topic starter  

That is odd indeed.

There are the obvious things we could try like emptying the trashcan, optimize storage (I've never used this), fresh reboot, make sure ArchiCAD has full disk access (although this should not be needed), and oddly enough: remove all external drives (I've seen a bug in the past where a full external disk would trigger a "disk full" error incorrectly), etc.

Another thing that could play a role is if ArchiCAD has a bug determining disk space.
For that you'd have to check and see if this is a known issue. 


   
ReplyQuote
Share: