(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" downloading Ventura as we speak, and will try later today to install from scratch. Haven't had time yet to create an ISO image to do a clean install. I did find this description, suggesting the VMX text below would work, but that fail when upgrading from Monterey to Ventura. Maybe a copy/paste mistake, or maybe the reason why it says the file is corrupt? Then I see that the "smbios" line misses a closing double quote. Note: If I look at the code you pasted: smbios.reflectHost = "TRUE 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. I did some testing and ran into the same issue with Ventura - seems a known issue. I'm using the same VMWare Workstation version and installed Monterey this way (like you did). Or grab this copy (which may be very outdated by the time you read this) 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_圆4/darwin.iso Now by default, VMware Workstation Player will NOT come with the macOS VMware tools. Install the VMWare Tools for your macOS VM (requires VM reboot) 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).Ħ. Once erased (use default values), close " Disk utility" and select " Install macOS Monterey" (or which ever version you are installing). Select that disk, click " Erase", give it a name, but keep the other default values ( APFS/ GUID Partition map). Run the Apple install - takes about 15-25 minutes depending on your hardware.Īt 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". 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.ĥ. I usually customize the setting for my VM's, and in this case:ĪMD 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. Open VMWare Workstation Player, and create a new virtual machine - you can select macOS now, and select the macOS ISO file.Ī few things you should pay attention to: Download and run Auto-Unlocker which add “macOS” as an option when creating a new Virtual machines.Ĥ. I used the method described here - since downloading ISO files from others can be questionable.ģ. Install VMWare WorkStation Player (I used v17) - it's free for non-commercial use.Ģ. This worked for me, even with an AMD CPU:ġ. 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. However when needing a virtual machine to test an older macOS, I find a macOS Virtual Machine to run really slow on a Mac. I occasionally need to test a few things for macOS, for which I usually use one of my Mac's.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |