With the newly released version of VMware Fusion 12.0 I'm having the same problem I did with the Technical Preview in macOS Big Sur Beta 6.
When starting a Windows 10 x64 virtual machine, I receive the following error message:
Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'.
More information can be found in the vmware.log file.
Virtual device 'Ethernet0' will start disconnected.
Has anyone found a solution to restoring internet availability in the guest virtual machine?
OMG !!! That fixed the issue !!!! You are a life saver .... Now the question remains ... do we have to do this at every reboot but even if that's the case we at least have a workaround in the meantime !
Thx a mil !
it is allways better before installing new software as fusion e-x-p or fusion 11 to remove the previous installation with special programs as appcleaner or ccleaner.
This is the way i had choice and so i had never this problem!
appcleaner is open source and detect all components!
this for information!
Yea! It worked!
Wonder if the "diff" between original, after deleting and killing configd, and then after running Fusion gives any hints to apple or VMware on the problem.
I upgraded to 11.0.1 Beta (20B5012d) from Catalina and initially saw no networking issue as I had when I upgraded to a previous Big Sur beta.
However, after a day and maybe a reboot I saw the same problem and solved it with the previously shared solution:
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd
In other news, sidecar stopped working and I had never had any issue with it previously. Of course, this is all on a spare machine used for testing betas
This is not working with the last macOs BigSur and VMware Fusion 12 player. The nat.conf and dhcp.conf are simply ignored, the windows 10 guest OS created a new network and use a default dhcp.
No way to make my networking configuration working with my guests... Hope a fix will come soon... Macbook Pro 15 inch 2019
I also ran into this problem today.
My VMs all use NAT but they use static configurations rather than DHCP. (The application which runs in these VMs is over 30 years old, predates DHCP, and requires static IP addresses.)
What I discovered is that the gateway and DNS server addresses have changed when using Big Sur's hypervisor framework. Previously, both the gateway and DNS server were at x.x.x.2. Under Big Sur, they are now at x.x.x.1.
I changed the VM configuration to use the updated gateway and DNS addresses and networking works!
The issue is still available, we really need a solution my machine on: