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?
Cheers
I tried this suggestion from the Parallels Community and it seems to have solved this issue for me in VMware Fusion 12
Enter the following command in terminal before starting VMWare Fusion:
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd
Cheers
Geoffrey
We have isolated the problem to a regression in Big Sur Beta 6 and that we reported the problem to Apple.
Thanks for the quick reply!
I would recommend you add this caveat to the Release Notes, since I didn't find it there and suspect until this problem is solved by Apple others will be checking in here looking for help.
Geoffrey
I'm on the same Big Sur Beta 6 and initially experienced the same issues as you but rebooting my Mac fixed the issue for me.
I think given this issue was widely reported in the Tech Preview forum and was pretty clearly an issue with beta 6, its more than surprising you've launched this touting Big Sur compatibility before this has been resolved by Apple. I suspect a lot of people will purchase over the next few days and be incredibly disappointed/frustrated that this doesn't resolve the issue.
Big Sur is beta software, so while Fusion 12 is compatible, VMWare can't be responsible for regressions in MacOS (just like the catalina regression in 10.15.6). Big Sur shouldn't be on a production machine, so frustrations should be minimal.
Fails with Dev Beta 7. 2020 13" MBP 32 GB.
Welp, I wish I checked here first.
After struggling for an hour (rebooting, deleting & reinstalling Fusion, using EasyFind to delete every vmware-related preference and support file), I finally came here to look for help only to find it's a known issue.
This is a test machine, so I'll just patiently wait for the regression to be fixed... 🙂
Beta 7 is now out, still the same issue.
BBig Sur beta 7 is avalaible!
Hi
Is it related to just certain Macs? I have the problem on my 16-inch MacBook Pro, but a colleague of mine with an older 15-inch MacBook Pro is working fine with Beta 7 of Big Sur and Fusion 12.
Thanks,
Mike.
That is correct. Not all systems are affected. So far I've noted owners of MacBook Pro 16" and 13" (2020) models reporting issues, which is why I suspect the problem may not only be attributable to "a regression error" with Apple. I don't have any idea what VMware means by this. I understand that this is Beta software and that Parallels also had embarrassing kernel panic reports with their first version of Parallels Desktop 16.0, but they quickly released a fix and I hope to be able to return to VMware Fusion as soon as possible in macOS Big Sur.
Just posting for adding info:
2018 15" MBP w/ i7
Running Big Sur beta v11 20A5364e
running VMW FPro12
Ethernet connection broken since the mid September update, was working fine before.
Just adding the regression also affects my iMac (27", 2017)
Same problem:
MBP 15" i7 2016
VMware Fusion Pro 12
MacOS Big Sur Beta build 20A5364e
Sadly, I'm experiencing the same issue with macOS Big Sur Beta 8.
Same issue here, Macbook Pro Retina 15 mid 2014, I think issue related to Apple, Because I am facing network issue in Parallel also.
I am on Beta 8 (20A5374i)
Same here
Macbook air 2017
BigSur beta 8
Vmware Player latest version
New created Windows 10 pro 64
BR
Edvard
Same Here ... Macbook Pro 15 inch 2019 - Dual i9
Big Sur Beta 8
Fusion 12.0.0
All VMs, new or existing give No Ethernet Connection error ...
I tried this suggestion from the Parallels Community and it seems to have solved this issue for me in VMware Fusion 12
Enter the following command in terminal before starting VMWare Fusion:
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd
Cheers
Geoffrey