5/7/2023 0 Comments Vmware fusion 12![]() I will wait a little longer (BTW I am using a MacBook Air M1 processor to post this information and it works beautifully, I love it, but do not try to run a VM, that really will not work ) I cannot get networking to run on a VMware 12 and Big Sur machine.Īt this point I cannot correct 1 and I am not prepare to risk going through the process to upgrade to Big Sur, install VMWare 12 and find it does not work and then revert to the original system as I have done twice already to test 2 above with VMWare 12.1.0 or 12.0.1.Īll a little frustrating but normal for such a big change in concepts. I cannot get VMware 12 to install and run on Catalina.Ģ. I have not tried to run Big Sur on a working Catalina/VMWare 11 machine as the trip back to a working system is time consuming if it does not work.Īs pointed out by another poster, I have two issues:ġ. I believe that there is a new release of 12 (12.1.0 ?) which fixes the Ethernet0 issue (this prevents a network connection device being mounted) so you should be able to get a network connection. ![]() If you use Big Sur as the host, then VMWare 12 is the only solution, only it does not work for me. ![]() However I suspect there are bugs on both sides (VMWare and Apple) here. VMWare 11 will not work on Big Sur, period (as far as I can tell) since Big Sur does not support Kernel Extensions and relies on Apple's Drive Kit which are a series of APIs that are supposed to give the same function as the Kernel Extensions in Catalina. I might as well keep it on VMWare 11 on Catalina.Īgain appreciate your suggestions and help. Since the machine I currently use for VMs is on Catalina, it is not really practical to upgrade to Big Sur and then try the process again, since, if it failed, I would have to go back to Catalina which takes several hours. My network settings are very standard, Bridge, Auto. Time to re-setup my desktop PC again I suspect.Ģ. I repeated the process as you suggested and nothing changed. I never saw the prompts to install the extensions and, as a result, the VMs would not run. I had the security option unlocked and open on my desktop and installed VMWare. I even hunted down the library entries for VMWare and deleted them before reinstalling. I assumed the broken pipes issue was due to incorrect installation, so I have already been through your suggested process (I noted that I had had the same issue with OWCs Softraid when it tried to install extensions and I had to unlock the security options in System Preferences in order to get it to prompt to install the extensions). Thanks in anticipation of some help and guidance.ġ. If someone can give me any guidance I would be grateful meanwhile I am sticking with Catalina and VMware 11 for the moment. I am assuming it is to do with the fact VMWare does not use KEXTs in Big Sur but uses Apples Drive Kit and there are bugs somewhere in the new code for the new APIs, although your blog indicates that, in Catalina, you still use kernel extensions, so that does not explain the Catalina/VMware 12 failure I am observing, but might explain the Big Sur issues where Apple's Drivekit APIs have to be used. There is obviously a fundamental problem here. I reverted to Catalina (with much pain), put back VMWare 11.5.6 and used backups of the VMs and all is well. At least I did not get the broken pipes message but the VMs were not much use to me. With these 3 VMs the MS Update server could not be reached, my email client in the browser would not load, the Baraccuda VPN adapter did not work etc. I run all my VMs in Bridge Auto mode, so each VMW has its own IP address. The other 3 VMs came up and ran with networking apparently connecting but I discovered that NAT was not working. The VM ran fine, but with no network connection. 1 of them came up with the 'Ethernet0 could not be loaded so networking was disabled' type message so there was no virtual network adapter. I upgraded to Big Sur on one of my Macs and, of course, you need to install VMWare 12 in order to get the VMs to have any chance of running. Has anyone else had these issues and if so what can be done to make it work.Ģ. So it looks as if VMWare 12 would not work for me on Catalina. The VMs were upgraded and then would not start due to 'broken pipes'. Checked everything was working and did the upgrade to VMWare 12 again. I assumed that an issue I had with OWC's Softraid where I had to unlock the security options prior to doing the upgrade (to allow extensions to be installed), may be the problem, so I put backup copies of VMs back and reinstalled VMWare 11.5.6. ![]() I upgraded to VM12 (Player edition) and immediately had issues with 'broken pipes' messages and the VMs refused to start after VMWare 'upgraded' the VMs. I have 4 VMs all working well on VMWare 11.5.6 (standard edition) and OS X 10.15.7. I have been on the trail of several issue and have posted in the general forum but thought I would post here and see what the team has to say.ġ.
0 Comments
Leave a Reply. |