Big Sur, VMWare 12: One VM could not connect to the ethernet networking adapter.
If people have other observations or I have missed an obvious fix, happy to be corrected.Ĭlick to expand.Wish I could say the same. I also tried Parallels 16.0.1 and it has the same problems which leads me to think that Big Sur is the problem. At this point I have to mark VMWare Fusion 12 as a non working solution for Big Sur. It looks as if the NAT is not working, but I cannot verify this.īottom line is I have moved my 16" MBro back to Catalina (via Time Machine) and am back to using Catalina with V11 VMware and all VMs work. They connect to the network (usually via a bridged connection) but MS Windows update cannot find the update server, my browser (Edge, Chrome or Firefox) cannot reach my email server but I can get to Verge, MacRumors etc. One of the VMs would not connect to the network adaptor (Ethernet) and the standard terminal command fix (from the VMWare blog/forum comments) does not work to fix it. These VMs are various level of W 10 Pro (1809, 19) and all have network issues. I have/had Big Sur installed on 3 machines (2020 MBA, 2020 13" MBPro, 2019 16" MBPro) and 4 VMs which worked fine on VMWare 11 on Catalina. For Catalina it continues to use Kernal Extensios. VMWare moved to V12 so that it did not use Kernal Extensions and used Apple APIs in Big Sur only. Hi, I did a quick search here but wanted to make a comment about VMWare Fusion.
0 kommentar(er)
