Naki Posted June 27, 2022 Share Posted June 27, 2022 (edited) Guys, nobody here using Windows 10/11, with VMware Workstation Pro 16.2.x? And using macOS VMs on top of that Host OS? I will now try to update from non-working 13 Ventura Beta 1 to the newer, latest Build/version. Wish me luck with networking! EDOT: Can I use custom kEXTs, and/or Clover or OpenCore on VMware Workstation? Edited June 27, 2022 by Naki grammar/clarity Link to comment Share on other sites More sharing options...
Naki Posted June 27, 2022 Author Share Posted June 27, 2022 (edited) Networking totally DEAD in latest Beta too! Any ideas if I am doing it wrong, or something to try to get some kind of networking back? Might NAT networking work better than Bridged, for example? Edited June 27, 2022 by Naki Link to comment Share on other sites More sharing options...
Naki Posted June 27, 2022 Author Share Posted June 27, 2022 (edited) Anyone use this successfully? I mean latest 22A5286j, Beta 2 Build, direct download link for that being here: https://mrmacintosh.com/macos-ventura-13-full-installer-database-download-directly-from-apple/ More exactly, I mean using VMware Workstation 16.2.x running on a Host OS of Windows 10, or Windows 11 64-bit, with at least 16 GB of RAM? And using the macOS Unlocker, so that the Mac VMs work. (I have 32 GB of DDR3 RAM here on both my VMware machines. In my case, both my VMware computers - Intel Haswell on a HP Workstation laptop, and older Intel Ivy Bridge desktop PC - both run Windows 11 OS.) A few issues here: 1) This new macOS Beta drops support for some too old, plus some too new Intel CPUs. I am nowhere near the new ones, so that is not any problem for me, but seem to be affected by the old ones dropped. Old ones include Intel Sandy Bridge (do not use) + Ivy Bridge CPUs (still use!). When I try it on my Core i5 Ivy Bridge, I get a constant Apple logo reboot loop i.e. no go. On this same desktop PC, I have VMware virtual machines ALL of macOS 10.8 Mountain Lion up to latest macOS Monterey 12.4, mostly all running fine. (YES, all TEN of them. ) But macOS Ventura Beta seems to be another matter. 2) On the newer Intel Haswell laptop, it sorts of works but Networking is "missing in action". Seems Apple dropped some Intel WiFi/LAN adapters that are too old, i.e. those from Haswell times. This means the VM is basically unusable, no way to download extra web browsers Chrome, Firefox, Opera, MS Edge/etc, no way to open any websites i.e. no Internet, no way to use Apple's App Store/etc. Any way to "inject" the missing network(ing) driver(s)/kext(s) to add Networking back? OR can I edit the VMware VM .vmx file to change the LAN adapter type/brand to something that works/could work? Please note changing VMware Workstation Networking from my usual Bridged to NAT does not help. (Which is logical, as this is a global issue due to old Intel LAN chips support removed.) Edited June 27, 2022 by Naki Add direct download link(s) 1 Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted June 27, 2022 Share Posted June 27, 2022 (edited) Ventura relies on AVX2, which the Ivy Bridge lacks (it only has AVX, not AVX2). It is theoretically still possible to install Ventura on it, but by the looks of it there won't be any support for hardware older than Haswell within Ventura anytime soon, if ever (Graphics mainly) As for your Haswell, in theory you could install OpenCore on your VM to boot macOS and inject the appropriate kexts for your networking card. However that all depends on what the model of your networking card is. Edited June 27, 2022 by ricoc90 Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted June 27, 2022 Share Posted June 27, 2022 bridge -> autodetect and ethernet0.virtualDev in your .vmx to "vmxnet3" If that doesn't work than I don't know sadly Link to comment Share on other sites More sharing options...
Naki Posted June 28, 2022 Author Share Posted June 28, 2022 (edited) 17 hours ago, ricoc90 said: bridge -> autodetect and ethernet0.virtualDev in your .vmx to "vmxnet3" If that doesn't work than I don't know sadly Great! Thanks so much for both of your replies. Very easy fix - the editing to .vmx file to change from the other value of ethernet0.virtualDev to "vmxnet3" has worked fine. Networking is now working! (Of course, I did that with VMware Workstation exited/not running.) I will try to install extra web browsers now, and setup the App Store. ( EDIT: Adding some extra browsers worked fine, see the Dock in the above screenshot. App Store up & running too.) Edited June 28, 2022 by Naki Link to comment Share on other sites More sharing options...
Naki Posted June 28, 2022 Author Share Posted June 28, 2022 (edited) On 6/27/2022 at 3:45 PM, Naki said: Networking totally DEAD in latest Beta too! Any ideas if I am doing it wrong, or something to try to get some kind of networking back? Might NAT networking work better than Bridged, for example? Works fine now! All I did was - suggested to me in another forum thread/section here: Bridged Networking set to "Autodetect" and ethernet0.virtualDev in the .vmx file changed to "vmxnet3". Networking works now! Screenshot - as you can see, a few extra web browsers added already (including Chrome, Firefox, Opera) --> Edited June 28, 2022 by Naki Add screenshot 1 Link to comment Share on other sites More sharing options...
naiclub Posted November 12, 2022 Share Posted November 12, 2022 Spoiler VMware hasn't played for a long time. Let's update a bit 1 Link to comment Share on other sites More sharing options...
Naki Posted November 12, 2022 Author Share Posted November 12, 2022 (edited) What Intel (??) CPU model/generation is this on, please? A while ago, I could not get macOS Ventura Beta to work/run on Intel Ivy Bridge CPU, it was doing the Apple logo "boot loop". It works on Intel Haswell though. Edited November 12, 2022 by Naki 1 Link to comment Share on other sites More sharing options...
naiclub Posted November 12, 2022 Share Posted November 12, 2022 (edited) Yes, it does it on my machine, in my signature. Edited November 13, 2022 by naiclub 1 Link to comment Share on other sites More sharing options...
Naki Posted November 13, 2022 Author Share Posted November 13, 2022 (edited) You have many machines in your sig, so which of those is that on, please? Did you do anything special to make it work? (besides having the VMware macOS Unlocker) When I tried first 2-3 Ventura Betas on my desktop PC with Intel Ivy Bridge Core i5 CPU (4 cores/4 threads), it would not work so I stopped trying. And it worked fine on Intel Haswell laptop too, so I was not out of usable Ventura VMs, I had one, which was enough in my case. Edited November 13, 2022 by Naki Link to comment Share on other sites More sharing options...
naiclub Posted November 13, 2022 Share Posted November 13, 2022 (edited) You have many machines in your sig, so which of those is that on, please? Did you do anything special to make it work? (besides having the VMware macOS Unlocker) According to my latest signature now i5 4670k, RX560 4g graphics card is just that, in your case that can't be used. I didn't do anything special. Just install as normal, with macOS 13.1 beta 1 beta, then update to beta 2 immediately, that's all. (Ivy Bridge) that should be from the lack of avx2, will it be? Edited November 13, 2022 by naiclub 1 Link to comment Share on other sites More sharing options...
Naki Posted November 13, 2022 Author Share Posted November 13, 2022 (edited) In that case, you clearly misunderstood the above question of mine. Please note your i5 4670k CPU is Intel Haswell, it is not the older Ivy Bridge generation - and I already know Haswell works! I was asking if you got Intel Ivy Bridge working specifically, seems you did not. So, your reply above is misleading. Yes, probably. Exact reason does not matter much, assuming no fix/workaround exists. Edited November 13, 2022 by Naki Link to comment Share on other sites More sharing options...
flakey Posted November 29, 2022 Share Posted November 29, 2022 (edited) I've had a working macOS VM for several years, but the upgrade from 12 to 13 has been repeatedly unsuccessful, previously in Workstation Pro 16, and now in Workstation Pro 17. The operating system fails to start up after applying the macOS 13 upgrade; it enters the familiar boot loop. Restoring the backed-up .vmdk with macOS 12 allows me to use the VM again but, unless I can find out what's causing the boot failures for macOS 13, I'll have to stick with 12. Workstation Pro is unlocked as usual (thank goodness for MK-Unlocker continuing to work after all this time). Any suggestions of things I can try, to get macOS 13 to apply successfully? The host has an i7-11850H CPU and 128GB RAM. The VM has 4 cores and 8GB RAM allocated to it. Edited November 29, 2022 by flakey Link to comment Share on other sites More sharing options...
flakey Posted November 29, 2022 Share Posted November 29, 2022 1 hour ago, flakey said: I've had a working macOS VM for several years, but the upgrade from 12 to 13 has been repeatedly unsuccessful, previously in Workstation Pro 16, and now in Workstation Pro 17. The operating system fails to start up after applying the macOS 13 upgrade; it enters the familiar boot loop. Restoring the backed-up .vmdk with macOS 12 allows me to use the VM again but, unless I can find out what's causing the boot failures for macOS 13, I'll have to stick with 12. Workstation Pro is unlocked as usual (thank goodness for MK-Unlocker continuing to work after all this time). Any suggestions of things I can try, to get macOS 13 to apply successfully? The host has an i7-11850H CPU and 128GB RAM. The VM has 4 cores and 8GB RAM allocated to it. Bumped the VM's RAM to 16GB and tried again. This time the macOS 13 upgrade appeared to stick without causing boot loops, although I couldn't get past the login screen; it would return to the login screen every time I entered my (very familiar) password. Some cursory Googling suggested Safe Mode or Single User mode might help. Trying them now... Link to comment Share on other sites More sharing options...
flakey Posted November 29, 2022 Share Posted November 29, 2022 16 minutes ago, flakey said: Bumped the VM's RAM to 16GB and tried again. This time the macOS 13 upgrade appeared to stick without causing boot loops, although I couldn't get past the login screen; it would return to the login screen every time I entered my (very familiar) password. Some cursory Googling suggested Safe Mode or Single User mode might help. Trying them now... Safe Mode seemed to do the trick. Post-upgrade optimisation finished, and subsequent login was possible. Bumped the VM further to 32GB and 8 cores. Host can handle it. Link to comment Share on other sites More sharing options...
flakey Posted November 30, 2022 Share Posted November 30, 2022 (edited) 18 hours ago, flakey said: Safe Mode seemed to do the trick. Post-upgrade optimisation finished, and subsequent login was possible. Bumped the VM further to 32GB and 8 cores. Host can handle it. As a test, after bumping the RAM to 32GB and the cores to 8, I restored the backed-up .vmdk with macOS 12, and attempted the upgrade again. This time the upgrade succeeded on the first try. I guess my original problem was probably due to starving the operating system of resources; I didn't think to allocate more resources to the VM with each successive release of the operating system. Edited November 30, 2022 by flakey Link to comment Share on other sites More sharing options...
becker666 Posted May 23 Share Posted May 23 (edited) I installed Ventura on win10 latest workststion 16 all worked very good...a week later My laptop lost power and now stuck on bootloop tried reinstalling the unlocker but no diff any suggestions?? Edited May 23 by becker666 Link to comment Share on other sites More sharing options...
Naki Posted June 11 Author Share Posted June 11 On 5/23/2024 at 4:43 PM, becker666 said: I installed Ventura on win10 latest workststion 16 all worked very good...a week later My laptop lost power and now stuck on bootloop tried reinstalling the unlocker but no diff any suggestions?? You are supposed to keep backups of all VMs, to solve data loss/VM breaking down this way. Link to comment Share on other sites More sharing options...
Recommended Posts