No Ethernet Connection VMware Fusion 12 macOS Big Sur Beta 6

[Geoffrey84]

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

[mkang]

We have isolated the problem to a regression in Big Sur Beta 6 and that we reported the problem to Apple.

[Geoffrey84]

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

[codeBuilder2011]

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.

[ColoradoMarmot]

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.

[jordan50198]

Big Sur isn't compatible though, so why is it claimed to be?

Issue still not resolved on macOS 11.0.1 (not beta) - so I think all the customers who bought this on the premise that this was compatible with Big Sur need to be refunded. 

 

Yes, VMware are not responsible for regressions in macOS - but they are responsible for correctly advertising their products, which they haven't done. 

[killee]

Just had my first call with VMware tech support (after waiting several weeks to get started). It appears to be a known issue/bug and has been escalated to engineering to resolve, the support tech tried a bunch of things with no luck so they're collecting the logs and will need more time to fix the issue. 

To be clear, I'm talking about the inability to connect Ethernet0 when the VM starts or when it's running.

Tech was initially focused on any VPN client I have on my machine since there are known issues with Fusion 12 while using a VPN. I was not using a VPN but had clients installed, we uninstalled them but it did not help. Folks having the same issue can try uninstalling all VPN clients to see if their issue is resolved. Note: I also uninstalled my Bitdefender antivirus since it has a built-in VPN client (which sucks, but that's another story).

In case it's helpful to others, there are a few commands we ran on the command line which the tech thought might resolve these issues. They didn't but I'll share them here in case others want to try it:

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --configure

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start

 

Tech also tried switching the adapter from NAT to bridged mode, then connect the adapter (failed), then switched back to NAT mode and connect the adapter (failed).

Seems like we need to wait for the product developers to fix this bug...  

[jjaimon]

I agree that we need to be refunded.  Only reason some of us upgraded to Fusion 12 is becuase to their claim that 12.x is BigSur compatible.  I raised a support ticket, and they want me to work with my VPN providers and others to fix their software issue.  No software vendor is going to entertain a support ticket because something else is not working.  I'm asking for a refund from VMWare and now they refuse to respond.  VMware might listen if many of us raise this issue or go for a legal path.  

[killee]

I learned a lesson by not taking advantage of the free trial, it would have been obvious Fusion 12.1 networking is broken on Big Sur. My support case is still open, very nice support technician who helped me but they said there is a known bug in the product affecting others too, something related to VPN causing issues with Fusion 12. Not sure if it's a high priority fix for them though, weeks have passed. None of my VMs have any networking capabilities, the adapters won't connect. I bought Parallels since I couldn't wait any longer and it works fine. There are free alternatives too.

Doubt anyone will get a refund because they do offer a free trial. 

Since the very first release of Fusion I always bought the upgrade without thinking. Silly me. I suspect it will get fixed one day

[codeBuilder2011]

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.

[Geoffrey84]

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. 

[herrugatto]

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.

[Kimoboy26]

Fails with Dev Beta 7. 2020 13" MBP 32 GB.

[rvanderveer]

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...  :-)

[Beardo701]

Beta 7 is now out, still the same issue.

[albatros99]

BBig Sur beta 7 is avalaible!

[TheGeekFreek]

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.

[clendenj]

Just adding the regression also affects my iMac (27", 2017)

[rvisscher]

Same problem:

MBP 15" i7 2016

VMware Fusion Pro 12

MacOS Big Sur Beta build 20A5364e

[Geoffrey84]

Sadly, I'm experiencing the same issue with macOS Big Sur Beta 8.

[agfasaud]

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)

[Edlar]

Same here

Macbook air 2017

BigSur beta 8

Vmware Player latest version

New created Windows 10 pro 64

BR

Edvard

[sbigras]

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 ...

[Geoffrey84]

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

[sbigras]

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 !

[albatros99]

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!

[DaveHanner]

Worked great for me too Geoffrey!  Thanks for sharing!

[dminter]

Worked for me too!  Good detective work finding the solution over at Parallels!

2019 Imac

Fusion 12

Windows 10

[agfasaud]

Great, It works :smileyhappy:

[jmdomini]

Worked for me as well, and I did not have to run it again after rebooting. Great detective work!!

[codeBuilder2011]

Excellent - thanks for sharing!  Works great for me too!

[haimeh]

This appears to have fixed my issues as well, thanks for taking the time to post this. (MacOS Big Sure Beta 8, VMware Fusion 12)

[squirrelbones]

Perfect, Thank You!  Boom!

[spankym]

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 :smileywink:

[dev4vm]

Just updated to the final version of macOS Big Sur. The tip no longer works for me.

[hwanjo1]

Turning off Internet Sharing solved the problem for me (of course as long as you don't need the Internet sharing)

[sjinsjca]

Turning off Internet Sharing worked for me too!!

This was a long, long day of trying to figure out how I'd borked my VMs, or Fusion itself, or macOS.  I reinstalled macOS, uninstalled/reinstalled Fusion multiple times, deleted all my networking and recreated it, and of course tried the magic command that helped so many earlier posters.  Nothing worked.

Then I saw this post... instant cure!  Thanks thanks thanks thanks thanks!

[GregB84]

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

[om3rx]

Hi, updated to macOS Big Sur and I have Fusion 12 Pro installed. My network is set to NAT but internet is not working.. 

[palter]

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!

 

[nakca]

Just I changed the DNS to 8.8.8.8 all virtual machines now NAT works fine. This is really miserable BUG for VMWARE.

[whitby1]

I have made comments at other points in this thread but wanted to point out that, for me,  VMware 12 with the Big Sur 11.0.1 release does not work with or without this fix for 4 VMs. I either get the missing ethernet0 message or networking fails (most likely a NAT problem). My network interface is set to Bridge, Auto.

[vikrampb]

I still seem to have this problem. Any ideas on what the issue might be? I have the version of Big Sur as released by Apple on Nov 12.

[reddy512]

Thanks for your solution, and additionally rebooted MAC and VM to fix the issue.

[vikrampb]

Are you now able to get past the "No Ethernet Connection" Issue? I've tried re-installing VMWare, deleting and recreating my VMs, rebooting my Mac several times, creating a new vmnet2 network as mentioned by someone else on this thread, and none of them have fixed the issue. I'm really stuck, and short of reverting back to Catalina and VMWare Fusion 11, I'm not sure what I can do to continue my work.

[whitby1]

I have not been able to get past this issue and ended up reverting to Catalina and WMWare 11 (I cannot get VMWare 12 to work on Catalina with a large number of 'broken pipes' messages that I cannot repair). The process was painful, even with a full Time Machine backup available. I ended up going to back bare metal (so to speak) and reinstalling Catalina (you have to do the Option, Command, Shift, R reboot otherwise it puts back Big Sur) as Time Machine was going to take 96 hours to restore. Apple do not want you to be able to revery to the original installation.

All rather unsatisfactory as I have not seen a VMWare comment (I do not expect Apple to respond or care, frankly - I filed a bug with Apple) on this apart from an odd note earlier on in one of the message streams that is was an 'Apple regression error' as this problem had been seen during beta releases of Big Sur and Apple apparently either fixed it and broke it or never fixed it. Anyway I have resigned myself to staying on Catalina and ignoring those persistent messages from Apple about an upgrade for a while and hope that at sometime it is fixed. I have no pressing need to upgrade to Big Sur as it provides no useful improvements to the Mac experience and seems to break more than it repairs.

[italiandutch75]

how is that supposed to resolve the nat issue?

that will only wipe out your network connections until they are automatically recreated.

anyways, I did a lot of tests, icnluding this, same issue inside the guest, internet yes, vpn from host not.

[italiandutch75]

how is that supposed to resolve the nat issue? that will only wipe out your network connections until they are automatically recreated. anyways, I did a lot of tests, icnluding this, same issue inside the guest, internet yes, vpn from host not.

[TheMuffnMan]

Commenting to both thank you for sharing that as well as to retain it in my profile. This appears to have resolved most of the network wonkiness with Fusion 12.

[Malte1511]

This did not work for me with:

BigSur 11.1
Fusion 12.1
Previous Win10 64 machine

Worked fine on 10.15 with Fusion 11 VPN NAT was no issue - Now the thing is a mess on my 2020 13 MacBook Pro. I even upgraded Fusion as 11 was not working on 11.1.

Hope there is a solution for this....

[jordan50198]

All these issues, yet VMware still claim Fusion 12 is compatible with macOS Big Sur.

I’m not THAT bothered that I have to mess around with my network setup to get things working - I am annoyed that VMware are continuing to make profit by mis-selling a product. 

[fabioz23]

i've still problem with MacOS 11.1 and 11.2RC with Fusion 12.1 when a Windows 10 VM has an interface in a bridge with integrated Macbook wifi interface.

The problem is a lossy data transfer, for example loading a web page misses some .js dependencies, with other protocols like WS-SOAP simply doesn't works.

If attach a usb-c gigabit ethernet  and move w10vm interface in bridge with the gigabit ethernet all works as normal.

 

 

[Blenheimpalace]

This solution worked like a champ. First time, no less!

[hd2659]

There are Many solutions in this thread, some for player, some on pro - but only with one interface in guest. Please clarify ?

[rscoville]

THANK YOU!

[venon6ix]

Hey 

Did this work? The bridge mode is not working for me on a Linux VM I am running. 

I didnt want to try this solution I see it is deleting something im not sure what it is ? And if i need it? 

 

Thank you 

[Edlar]

Hey

It works perfect for me. :smileyhappy:

When I start Vmware  I get the same error, but if I select Bridged Network, autodetect it works perfect.

Thanks a lot.

Edvard

[andrescr94]

Same issue

Ubuntu 20

Macbook air 2017,

Command above fixed it, thank you.

[brakes]

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.

[mtkrity2014]

The issue is still available, we really need a solution my machine on:

•  macOS Big Sur 11.0.1 (20B29) 
• MacBook Pro (13-inch, 2016, Four Thunderbolt 3 Ports)
• Vmware fusion Professional Version 12.0.0 (16880131)

issue: 

• Could not connect 'Ethernet0' to virtual network 'vmnet3.

[killee]

I am having these problems too, but on the first public release of macos Big Sur 11.0.1 that just came out and Fusion 12.0 on a 2015 Macbook Pro. No beta versions, I'm using the released versions of the OS and Fusion.

The network adapter Ethernet0 will not connect to virtual network.

The VMs then start up with no network adapter. I have tried the solution suggested in this thread but it does not work. I have also tried removing the adapter and adding it again, does not help. Also the mode of the adapter (NAT or bridged) does not make any difference. The issue happens in both Linux and Windows. I regret upgrading from Fusion 11 so far, these VMs worked fine with Fusion 11 but when I upgraded to Big Sur, Fusion 11 stopped working correctly so I bought 12 and it's worse, no networking at all.

[no_ethernet0]

Error: Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'. Failed to connect virtual device 'Ethernet0'.
Meta data: Macbook pro 2016 13 inch MacOS Big Sur 11.01, VMware fusion 12
Description: When a machine tries to connect through NAT with the network adapter, an error arises. Tried to solve this with the earlier given fix by deleting the NetworkInterfaces.plist file. Removing VMware (including .kext) and reinstalling also did not help. Maybe the right settings for the earlier named plist file could solve the problem.

When looking at 'Manage Virtual Interfaces' within Network settings, Ethernet (en0) is not present. The Thunderbolt Bridge services in the network settings are moving up and down when the machine tries to establish a connection with the network adapter.

See the screenshots below for the received error and Manage Virtual Interfaces settings.

 

 

 

 

 

[jjaimon]

Same problem here with newly released VMWare Fusion 12.0 Pro and BigSur 11.0.1.  Virtual Machine starts with the error "could not connect to ethernet0".  This is a NATed interface.  We really need a solution for this.   This is on a Macbook Pro 15".

I tried the solution listed in this thread. It didn't work for me and currently left with no solution to use my VMs.  VMs are virtually unusable without network support.   we need a solution for this. 

I also created another network interface (Pro feature) and associated with the VM.  That didnt work either.  I raised a ticket with VMWare about this issue, but yet to hear from them.  

[whitby1]

I have exactly the same problem on the released build of Big Sur (11.0.1) and VMWare 12.0.0. However this only occurs on 1 of the VMs. As a result this VM will not connect to the internet. All VMs are various builds of Windows 10 Pro (1809 and 1903 I believe).

I also have 3 other VMs that will connect to the internet but will not talk to the MS update server, my email client in any browser (Chrome/Firefox/Edge) and the Barracuda VPN will not initialize. This looks like a NAT problem. I am operating the network interface in bridged mode.

I have reverted to Catalina and VMWare 11 and everything works as expected.

Note that I could not get VMWare 12 to work on Catalina, since I kept getting missing pipes messages. I am not sure what is causing this, but it makes VMWare 12 useless on Catalina and it does not work on Big Sur either, but for different reasons. I was trying it out with the free license version prior to purchasing a full commercial license. I won't be purchasing VMWare 12 at this time. There seems to be a lot of reported issues with VMWare 12 at this time and are probably caused by VMWare switching to the Apple APIs (DEXTs) instead of using Kernel Extensions (KEXTs) however I have real evidence of this and it is supposition on my part. Whatever the reason, it is unreliable and unusable at present.

[virtualpboy]

Fusion 12 Pro absolutely works fine with NAT/bridging on Catalina. I am probably going to downgrade back to Catalina as well, unless VMware has identified the problems and found a workable solution.

[whitby1]

Do think my issues with VMWare 12 on Catalina is due to Pro versus standard version? 

I have read of a number of people who have made a comment about broken pipes warning when trying to get 12 to work on Catalina. I cannot get any VM to work on 12 in Catalina. I wish I had noted down the issue exactly, but having to make a copy of the  VM and then install 12 and try to run it, is a pain (after spending hours wrestling with Big Sur) so just noted that I was getting a series of 'broken' pipes messages and the VMs (I have 4 I use regularly) failed to start. 

I tried leaving security settings unlocked (I had  issues with OWCs Softraid which would not install unless you unlocked the security settings prior to install, rather than it prompt you to unblock to install the extensions it needs when installing) but it made no difference, so I am looking for some guidance here.

What am I doing incorrectly? My normal process is install the VMWare upgrade, run the VMs using the new install of the latest update to VMWare, respond to the question whether you want to upgrade the VM and then let it do its thing, which usually means it converts the VM, runs the client and then prompts for the install of the latest version of VMware Tools. I have done it for every version of VMWare from version 1 and had relatively few issues with the upgrades, but this is the first time I have had the converted VM refuse to run. So I am assuming I am not doing something and would seek guidance.

[virtualpboy]

Yes, Virtual network is a Pro feature. Pages like Add a NAT Configuration specifies:

With Fusion Pro, you can add additional NAT configurations for scenarios in which a virtual machine shares the IP address and MAC address of your Mac.

And this little bit from VMware Fusion product page:

Fusion Pro can additionally manage Virtual Network configurations, with a UI to create new networks, modify subnet settings, change MTU size, configure NAT port forwarding and more. View the traffic of each virtual network by using a standard PCAP reader, like Wireshark, to capture it with the built-in ‘vmnet-sniffer’ utility.  Finally, Fusion can even simulate things like packet loss, bandwidth limitations and latency to help test the resiliency of your app or service.

Activate 30-day Pro trial and see if your problem goes away.

IMO, if Fusion 11 works for you, I would continue using it until VMware fixes networking issues with Big Sur.

[whitby1]

Thanks for the help. I will try Pro (I used to have Pro versions on earlier versions but never used the extra features at the time, so saved money and bought the standard versions) and see if it makes a difference. However it might not be worth the effort as Big Sur will still probably not work. However I am curious so will have a go and let the forum know. Much appreciate the feedback.

[wd123]

There seems to be two problems mentioned in this thread.  One on a network-adapter level, and another on a DNS-server level. 

For those having trouble with only DNS with their VMs (which can be mitigated by manually configuring the DNS server used by a guest VM), see my notes here:
https://communities.vmware.com/t5/VMware-Fusion-Discussions/DNS-Forwarder-Does-Not-Seem-to-Exist-in-VMware-Fusion-12-on-Big/m-p/2810191/highlight/true#M170165

Starting with Big Sur, VMware Fusion will use mDNSResponder as a DNS server for virtual networks, and if anything is already listening on port 53 on your host, your VMs will not have working DNS by default.

For those having networking trouble because the host OS is using a VPN, see the workaround listed here:
https://communities.vmware.com/t5/VMware-Fusion-Discussions/Share-host-VPN-with-guest/m-p/2810095/highlight/true#M170151

 

[martinkntk]

I solved this by creating a new virtual network, vmnet2, which is not NAT, I connected both my machines into this network, set both to static IP, they can communicate, VPN and everything works, at least for now

[killee]

As mentioned by wd123 above, there are two distinct issues in this thread. There is no solution yet for being unable to connect a network adapter to Linux or Windows VMs. I just tested adding a second NIC to a VM to see if it made any difference but it does not, the NIC still starts disconnected and refuses to connect properly when the VM is running as well - regardless of whether it's NAT or bridge mode. None of the network adapters will connect leaving all my VMs without network access.

I opened a support ticket recently on this issue and will work through to resolution. Cannot connect Ethernet0 or Ethernet1 for all VMs (Linux or Windows) on Fusion 12 with Macos Big Sur 11.0.1. Seems like a bug since numerous others in this thread have the exact same issue.

[kam]

this issue is not resolved in macOS 11.0.1. 

[mtkrity2014]

still, we have no solution !!! any workarround? 

[whitby1]

Apparently VMWare Fusion 12.1.0 addresses the issues. I have yet to check this out. But I am aware that V12.1 provides a Fusion Health check to cure the Pipes issue on Catalina and a separate fix to address the Ethernet0 issue on Big Sur. Whether this solves the other networking issues I am not sure. However it looks as if VMWare have been listening (see their current Fusion Blog) and released a version to correct the problems reported. 

[killee]

Fusion 12.1 didn't fix it for me. That Health Check option sounds useful but I cannot find it in the GUI, does anyone know how to launch it? There is no built-in documentation about this feature, and no "single click" that I can find anywhere when the error occurs.

The link to the Fusion 12.1 release notes is also broken as I write this, but likely will be back soon. I'm hoping there are instructions inside on how to use that new feature that is mysteriously hard to find. I'm ok with command line too we just need some documentation.

My support case with VMware has been open for 2 weeks now but the support hasn't even started yet, the techs are extremely slow to respond and when they do, they ask simple questions that were answered in the notes I provided already. I would give them a -85 on the NPS (net promoter score) if asked today... ugh. I still have no network capability on *any* of my VMs since upgrading to Fusion 12 and then 12.1.

 

 

[whitby1]

VMWare do not seem to contribute to these conversations and the release of 12.1 went completely unannounced (note the blog note on this appears before the announcement of V12 which is therefore in the wrong date order. It seems they do not want you to know about 12.1). 

I appreciate your feedback and I will sit tight until we find out how the Health Check option works and someone verifies that 12.1 fixes the ethernet0 issue. I need the VMs to work.

[mtkrity2014]

Hi All,

I had discovered a very interesting thing when I change the subnet of my network from the old 11.11.10.0/24 to a new subnet 192.168.2.0/24 the issue resolve! and when I return back the old subnet and reboot the VM the issue comes back. 

the problem I need to be on the old subnet and I can't change it to any new network. Anyone has a solution to refresh the old VMware data so I can keep my old network?

 

I am using the latest version of Big Sur and Vmware

 

Thanks in advance 

[dgenton1]

version 12.1.0 doesn't fix it for me, I no longer get the pop up stating it cannot connect to the vmNetX connection, no errors at all actually but despite the interfaces showing up in the vm nothing connects.   I have many vm's and some work, some dont.. none did at first but I was able to get freebsd, windows, and apple based vm's working again by replacing the vmxnet3 driver specified in the .vmx file for the guest vm with e1000 again regressing back from 10gb to 1gb, but at least those vm's are back to working.  My linux based vm's that don't specify a driver file I have worked endless days without ability to get them working.   Again had many linux vm's for Cisco, Aruba/HPE, etc and most of them started working again after going e1000 (nothing else works) and the "other linux/64-bit" vm's without the driver showing never complain but can never talk no matter what physical NIC I connect to them to, no matter the combination.   None of these use NAT or VPN, just simple NIC configs all working prior to upgrade to Big Sur and VMware 12 Pro.

[JoshCastro]

Have posted this in a couple threads, and not sure if it works for everybody, but it did for me. I have been working on this issue for a while and could not get it figured out. Then with one click I was back on my VPN. In the Mac settings go to Security and Privacy and go to Firewall and turn on Firewall options. Then turn off Stealth mode. With that one click I was back up and using the VPN.

[GrayPenguin]

Thanks !!

Worked !

(this was a respose to 'Turn off stealth mode' in MacOS firewall)

[HarishBailwad14]

Hi 

i am facing the same issue not able to connect VMware Fusion's VMs on vmnet5

i have used below command but it doesn't help and still issue is the same.

sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd

i have MacOS and Just few days back updated the OS with BigSur 11.1 was the last update but still can connect on Private network vmnet5.

regards

Harish

[andyturk]

Still broken.

All of my VMs are without network access under Big Sur and Fusion 12.x. Strangely, networking seemed to work just fine for a day or two after upgrading to Big Sur. But sometime today, it changed and none of my VMs work any more. This is a real problem because one of the Windows apps I need phones home to a licensing server at every launch. It's mission critical and now useless.

• macOS 11.1 (20C69)
• VMWare Fusion Professional Version 12.1.0 (17195230)

 

$ sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd
Password:
$
$ sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --configure
Stopped NAT service on vmnet8
Stopped all configured services on all networks
Backed up existing network settings to backup file "/tmp/vmware.SpI1rT"
Restored network settings
$ sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop
Stopped all configured services on all networks
$ sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start
Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
Started all configured services on all networks

 

Unfortunately, even after all that...

 

Here's what shows up in vmware.log when I try to connect the network adapter:

2021-01-02T23:19:13.541-08:00| vmx| I005: TOOLS received request in VMX to set option 'synctime' -> '1'
2021-01-02T23:19:13.541-08:00| vmx| A000: ConfigDB: Setting tools.syncTime = "TRUE"
2021-01-02T23:19:13.548-08:00| vmx| I005: VMXVmdb_SetCfgState: cfgReqPath=/vm/#_VMX/vmx/cfgState/req/#24c/, remDevPath=/vm/#_VMX/vmx/vigor/setCfgStateReq/#1a8/in/
2021-01-02T23:19:13.557-08:00| vmx| I005: TOOLS received request in VMX to set option 'synctime' -> '1'
2021-01-02T23:19:13.557-08:00| vmx| A000: ConfigDB: Setting tools.syncTime = "TRUE"
2021-01-02T23:19:13.567-08:00| vmx| A000: ConfigDB: Setting tools.upgrade.policy = "upgradeAtPowerCycle"
2021-01-02T23:19:13.583-08:00| vmx| A000: ConfigDB: Setting ethernet0.connectionType = "nat"
2021-01-02T23:19:13.590-08:00| vmx| A000: ConfigDB: Setting ethernet0.addressType = "generated"
2021-01-02T23:19:13.590-08:00| vmx| A000: ConfigDB: Setting ethernet0.generatedAddress = "00:0C:29:EA:12:C7"
2021-01-02T23:19:13.621-08:00| vmx| A000: ConfigDB: Setting ethernet0.virtualDev = "e1000e"
2021-01-02T23:19:13.660-08:00| vmx| I005: Vigor_EthernetScheduleReconnect: reconnect delay = 7 seconds, reconnectEthVector = 0x1
2021-01-02T23:19:20.686-08:00| vmx| I005: VNET: 'ethernet0' enable link state propagation, lsp.state = 5
2021-01-02T23:19:20.686-08:00| vmx| I005: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2021-01-02T23:19:20.686-08:00| vmx| I005: VNET: MACVNetMacosGetRealAdapterType: network type for adapter 0: 8
2021-01-02T23:19:20.686-08:00| vmx| I005: VNET: MACVNetMacosGetVnetProperties: vnet properties: vnet=vmnet8, nat=yes, dhcp=yes (ignored), subnet=192.168.67.0, mask=255.255.255.0, firstAddr=192.168.67.1, lastAddr=192.168.67.127, isIPv6=no, IPv6Prefix=fd15:4ba5:5a2b:1008::, IPv6PrefixLen=64
2021-01-02T23:19:20.686-08:00| vmx| I005: VNET: MACVNetPortVirtApiStartInterface: Waiting on semaphore for adapter: 0
2021-01-02T23:19:20.689-08:00| host-51220| I005: VNET: MACVNetPortVirtApiStartHandler: starting interface for adapter: 0, status: 1009
2021-01-02T23:19:20.689-08:00| host-51220| W003: VNET: MACVNetPortVirtApiStartHandler: unable to create virtual intrface for device: 0, status: 1009
2021-01-02T23:19:20.689-08:00| vmx| I005: VNET: Semaphore signalled for adapter: 0, timeoutMs=5000, waitMs=3
2021-01-02T23:19:20.689-08:00| vmx| W003: VNET: MACVNetPortVirtApiStartInterface: Failed to create interface for adapter: 0, handlerStatus: 1009
2021-01-02T23:19:20.690-08:00| vmx| I005: VNET: MACVNetPort_Connect: Ethernet0: can't start virtual interface
2021-01-02T23:19:20.690-08:00| vmx| I005: Msg_Post: Warning
2021-01-02T23:19:20.690-08:00| vmx| I005: [msg.ethernet.connectionType.connectFail] Delayed connect of network adapter ethernet0 has failed. Please connect it manually by editing virtual machine settings.
2021-01-02T23:19:20.690-08:00| vmx| I005: ----------------------------------------
2021-01-02T23:19:20.703-08:00| vmx| I005: Msg_Post: Error
2021-01-02T23:19:20.703-08:00| vmx| I005: [msg.vnet.connectvnet] Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'. More information can be found in the vmware.log file.
2021-01-02T23:19:20.703-08:00| vmx| I005: [msg.device.badconnect] Failed to connect virtual device 'Ethernet0'.
2021-01-02T23:19:20.703-08:00| vmx| I005: ----------------------------------------
2021-01-02T23:19:20.924-08:00| mks| I005: SWBWindow: Number of MKSWindows changed: 2 rendering MKSWindow(s) of total 2.
2021-01-02T23:19:21.106-08:00| mks| I005: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 2.
2021-01-02T23:19:25.274-08:00| mks| I005: SWBWindow: Number of MKSWindows changed: 2 rendering MKSWindow(s) of total 2.
2021-01-02T23:19:25.674-08:00| mks| I005: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 2.

[killee]

I would open a support case to add more priority to this issue. My case on this exact issue has been open since November and no progress. They told me it's a known issue but they have no timeline on when it will be resolved. It appears it's not very important to VMware to fix this known bug. How times at VMW have changed...

[swinder0161]

Is there any update from VMWare on this long pending mission critical issue?

[srobadelic]

Same issue as reported here. Getting ready to open a ticket and hope that my purchase a few months back includes more than one support call, as I always seem to need more for the bugs. Has VMWare support had people enable diagnostic logging? It always seemed to provide support with useful info (not to say it allowed them to fix the issue).

[wd123]

  

Last I checked, VMware has filed this under "It's a macOS bug."  As such, they may be in the boat of waiting for Apple to fix it.  Which would be a tough situation to be in, as who's to say when it may get fixed by them?  Or even if they consider it to be a bug at all?

I'd hope that they're looking for workarounds to hedge their bets...

[GregB84]

Hello, Simply use Viscosity (https://www.sparklabs.com/blog/) : "Version 1.9 also introduces driverless TAP (bridged) connection support on macOS. This is something we are particularly enthusiastic about: if you use TAP (bridged) OpenVPN connections you'll no longer need to manually approve a kernel extension to load before you're able to connect. This will also make deployment much easier in enterprise environments. And best of all, our approach fully supports macOS 11." Without changing anything in Big Sure (11.1) configuration and Fusion Pro 12, my guest had access to a service behind the Host open vpn connection via Viscosity.This is ashamed that nobody from Vmware support could tell us this...Hope this will help.Greg

[Tobias007]

Had the same issue today when upgrading to BigSur official release. Solution for me was very easy: I went into the network settings of the VM and deactivated the network adapter, ticked Bridged Wifi, and attached it again. BigSur was then asking for permission. After that it worked fine...

[swinder0161]

Ofcourse bridge mode is working, discussion is on NAT.

 

[HarishBailwad14]

i am trying to connect with private to my mac but not able to connect 

 

 

 

[whitby1]

Does anyone know if the new release of Big Sur, 11.2 released 1 Feb, addresses this issue.

I still cannot connect to the network with Big Sur 11.1 and VMWare Fusion 12.1 (ethernet0 adapter issue) and VMWare Fusion 12.1 on Catalina (10.15.7) gives me broken pipe error messages, so sticking with Catalina 10.15.7 and VMWare Fusion 11.5.7 until this is all fixed. I need my VMs and I cannot afford to be without them or risk them being damaged due to the mess that VMWare and Apple have created with these new releases.

[fred55]

Just installed the new release of Big Sur (11.2) vmware fusion is update (12.1.0) and still have issue with NAT

Only workaround : set all VM in bridged mode

[fabioz23]

very strange situation, i've exactly the opposite problem. Win10 VM in NAT is OK, in bridge with my wifi has wrong data transfer, in bridge with a usb-c Ethernet interface is OK.

[immixJeff]

This is a pretty awful bug... how the hell did this get past QA?

[hd2659]

 

 

Just adding the regression also affects my iMac (27", 2017) and workaround does not work, running Big Sur 11.2.0

[whitby1]

After much experimenting and trying most of the solutions suggested here, I eventually found one that worked (ish) and subsequently noted that someone else had suggested the same approach.

Setup is: Big Sur 11.2.1 and VMware 12.1

VM is Windows 10 Pro 20H2 with 16 GB memory and 2 Processors allocated.

Host 13" MBPro connected via WiFi to network.

Standard option with Network Adaptor set to Autodetect (Bridged Networking) failed with Ethernet0 adaptor not detected and startup with no internet connection. I have not verified this operation on a machine that has an Ethernet connection to my network.

Setup changed to Bridged Mode WiFi and VM started up with no error and internet connection shown as working and connected. However download from internet was very intermittent and flaky. Speedtest showed 0 download speed even though I was able to access web pages, however anything with security failed. My Barracuda VPN would not connect. Strangly upload worked flawlessly.

Setup changed to Connect Network Adaptor, Share with my Mac (NAT) and VM started up correctly and showed an internet connection. Interconnection was stable and I could run the Barracuda VPN with no issues. 

Based on this all bridged connections fail and I could only get the NAT connection (Share with MAC) to function.

I am upgrading my 16" MBPro now to Big Sur and going to verify operation on that machine.

[kaavik523]

I have this exact same problem on 2020 MBP 16" running macOS Big Sur 11.2.2 and VMware Fusion 12.1.0 (17195230). When VM running Windows 20H2 is connected to bridge mode wifi, can browse non-secure websites but anything with SSL doesn't work and doing speed tests shows 0Mbps for download but normal upload (presumably because the speed test sites also use https). Interestingly, the problem does not happen in NAT mode (but not an acceptable solution for me) or in bridge mode when using hard-wired ethernet to the exact same home router (Asus RT-AC68U). 

I cannot for the life of me figure out why it doesn't work but the exact same VM works fine on my 2014 iMac 5K with bridge wifi mode so it is something specific to VMware + MBP configuration. The problem also happens on my 2018 MBP 15 running same versions of macOS and Fusion.

[whitby1]

It appears that the bridge autodetect option no longer works and bridge to wifi no longer works. I can use NAT when the host is connected to the network via wifi and bridge via ethernet  when the host is connected via an ethernet connection. I have not tried adding a new adapter to allow bridge via wifi. I am using a 2020 iMac, 2019 16" MBPro and 2020 13" MBPro and all exhibit the same behavior.

At the moment I can get things to work, but the lack of comments by VMWare appear to confirm that they have no clue or at least are not sharing what they know. Fundamentally part of the networking interface is broken and VMWare have left their customers to sort it out. I suspect this tells us that VMWare is no longer interested and we may all end up in the Parallels world or maybe they think it is all over when we move to Apple Silicon. I have fired up my Windows Desktop in preparation and have just purchased a new Windows based laptop. I think the days of virtual machines on Macs are drawing to a close, sadly. It was a nice run.

[hd2659]

Hi

My clients require 2 networks, so I made an workaround by adding an "Apple USB Ethernet Adapter" to use with Interface 1 and using Ethernet for the other

Where are VMware's focus on this

[JavierIBM]

The following changes resolved this issue for me. Please note that your mileage may vary and there is no guarantee that it will work for you on your particular workstation or configuration.  

Note 1: There may be some file and directory permission changes needed in order to make the changes to this file. 

On your Mac, edit the packet filter config (/etc/pf.conf) to add the comment and last two lines shown below near the top of the config file along with the rest of the NAT anchors. Note 2: They must follow the Apple anchors already in the file as shown below. Save the file after making the changes.

#
# com.apple anchor point
#
scrub-anchor "cisco.anyconnect.vpn"
scrub-anchor "com.apple/*"
nat-anchor "com.apple/*"
rdr-anchor "com.apple/*"
#ADDED the next 2 lines for VMWare Fusion NAT issue
nat-anchor "com.apple.internet-sharing/*"
rdr-anchor "com.apple.internet-sharing/*"

Then reload PF (disable & enable back) with the following two commands:

sudo pfctl -d
sudo pfctl -e -f /etc/pf.conf

The above should resolve NAT sharing to VM, except for DNS resolution. To resolve the DNS issue, in the VM, add a DNS entry for your local internal host connections (intranet at your company). Add a second DNS entry of 1.1.1.1 or your home router’s DNS (for external hosts) using static IP configuration. Note 3: The configuration interface depends on the OS in the VM; for RHEL NetworkManager applet or nmcli will do.

[hd2659]

Thanks,

It is not the packet filtering, I made a VM with 2 interfaces connecting to vmnet 2 and vmret 3 and only vmnet 3 gets connected, for vmnet 2 I get the well known "Could not connect 'Ethernet0' to virtual network 'vmnet2'", so before any NATing and DNS issues take place

Thanks for you input

My workaround with an additional UBS Ethernet Interface works for now

[JavierIBM]

Yeah, I can't say I'm a network guru or anything like that. It seems different approaches to this issue work for different types of configurations(?). I'm just glad mine is working again. 

[gringley]

I got curious about this again.  Back at the start of Fusion 12.0 I had problems so I went through my VMs and made sure they were all on Autodetect for networking.  Today I took a Windows 10 VM and set it to WiFi.  I got prompted as attached, and WiFi now works with the VM.  I am on an iMac Pro.

[gringley]

...well after a while HTTPS quit working on the VM so looks like Fusion 12 and WiFi is hosed for me too...  I have also noted that with Mac VMs the Mac VMs think they are connected to WiFi even though the VM does not have a WiFi adapter.  

[haggans]

Hi VMware and the community.

Quick background, we've moved over from Parallels to VMware Fusion couple of years ago and has successfully been using version 11.5 in combination with macOS 10.14.6. The VM is running Win 7 Pro.

For many reasons we now need to upgrade to macOS 11 Big Sur, which also require us to upgrade Fusion.

First machine has been updated, and i installed Fusion as demo just to try it out. Immediately get the problem as described in this thread, i have IP address, but NAT simply does not seem to work well. I have no internet, and I can not connect to file share. I tried the offered solution with deleting network settings via terminal, but did not work for me.

My next test was to install a vanilla Win 7 Pro, but i end up getting same problem. I tested setting bridged network, I was then able to reach msn.com I believe, but other websites would just time out.

Last test i did was to convert vmimage into Parallells and run their demo - it work.

Now - I would prefer to stay with VMware, that make everything easier for me. But can I? When i contacted support I was told that I can't get support until i purchase the software, i was encouraged to go on this forum instead. Anyone found a solution? Cheers /Matt

[hollistonma]

Same issues and same attempts at a solution.  The only thing that worked for me was to use "Shared with Mac".  See the saga here:  https://communities.vmware.com/t5/VMware-Fusion-Discussions/macOS-Big-Sur-Fusion-12-NAT-no-internet-connection/m-p/2842916/highlight/false#M173757

 

[haggan]

Interesting that you got NAT working.  I set network settings to  bridged now, I can access my server now, but most websites can not be visited, just times out.

Another thing i noticed is that VMware tools can not be installed via menu, i have to manually install by mounting the image. VMware tools installs, but with some errors, and it seem like shared folders AND drag n drop via Host/VM does not work.

I can't belive this is happening. Why is this product even being sold when it clearly has multiple severe issues.....

[hollistonma]

have you tried the "Shared with My Mac" option?  I had the same issue as you did with the bridged options.

As for VMware Tools, they were working for me.  Because I thought a new install might fix the internet issues, I uninstalled them in Windows using Windows Settings.  I then reinstalled them using the Install VMware Tools option.  (That didn't address the internet issues by the way.)

I agree that this is crazy.  Fortunately for me I'm running the unpaid version of Fusion 12 because I use it for my personal computer.  Until I tried the "Shared with my Mac" option and it worked I was ready to pay for Parallels.

Do you know any downside to using the "Shared with My Mac" approach?

[haggan]

 

When you using Share with my mac you are basically sitting behind an extra router/firewall right. This is the default option and preferred since it does work for most functions. Bridged mode make you appear as it's own device on the network with an appropriate IP address rather than masked.

When i do "Shared with my Mac" not much is working at all to be honest.

To add to the confusion - I now went back to my original VMware image with Win 7 that we use, it's an old image, approx 200GB that has been with us for a long long time and survived many versions of the actual VMware application - went back to it, changed the settings from "Shared.." to Bridged, waited at least one minute for network interface to re-appear and BOOM, it just works....

This being said, this is pure luck and I'm not presenting a solution here.

I will continue with upgrading machine number 2, and see if that also work. I'm desperately looking for a temporary solution until VMware fixed this flawed software.

[haggan]

I'm lucky in the sense that all my upgrades are working, but only working if using Bridged network and in combination with my old vm-images. Not if I create a new image.

Since we have now purchased latest version, I will go ahead and create a support ticket. It seem that we will not get any reply from VMware in this forum....

[hd2659]

Hello

With the release of MacOS 11.3 interfaces now appear in MacOS / Settings / Network and virtualise that configured interfaces never turn green , It's still faulty and VMware need to step in here.

I'm using a fresh install of VMware Fusion Pro 12.1.1 and defined 2 custom networks vmnet2 and vmnet3 in Fusion / Preferences / Network - these are now shown in "MacOS / Settings / Network" as seen here

So I created a new CentOS client using only vmnet2

Booting client shows that it try use the standard VM network interface and not VM network interface 2 as configured

Adding another network to the Client vmnet3, brings back the never ending story about "Could not connect 'Ethernet?" to virtual...."

 

I'm back to use the 2 physical interfaces I use as workaround (Ethernet and Apple USB interface)

[Ccalifan]

Fusion 12.1.2 released:

https://docs.vmware.com/en/VMware-Fusion/12.1.2/rn/VMware-Fusion-1212-Release-Notes.html

[spankym]

I am finding this issue with MacOs 11.4 and VMWare Fusion 12.1.2. The only workaround I have found is to reboot Mac, run sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd and then launch VMWare.  If I close Vmware Fusion I need to fully reboot again to get the network interface back.

[hd2659]

That didn’t work for me, also it’s un-acceptable as a work a round. Adding the apple USB adapter with a loopback plug, works fine for me as a network without routing. 

[atlauren]

+1 on this ongoing issue with bridged* networking.

Bridging over Thunderbolt** worked fine for a week, then died.  It seems to work OK with a USB-C/Ethernet adapter.

Big Sur 11.4
Fusion 12.1.2
MacBook Pro 16" (2019)
Windows 10

* NAT sharing from the Mac's connection(s) seems to work.
** Thunderbolt 3-to-2 adapter, OWC Thunderbolt 2 dock.

 

 

[realbg]

I think I found the issue after about 8 months of tinkering. I had ethernet enabled in System Preferences >> Sharing >> Internet Sharing. When messing around with that setting again, I can recreate the issue. Ensure that the feature is turned off completely or ethernet is not active. 

Hope this helps you as it did me in version 12 player for MaOS

[hd2659]

It's not that - Internet sharing is off on my Mac, also I'm using VMware Fusion Pro

[dynamoX]

help  ！ VMware  tech  staff 

[dynamoX]

now there is no way to fix it

[doanhtien]

I tried to run the command "

sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd"

But still the same. 

[hd2659]

Hi doanhtien

removing NetworkInterfaces.plist did work nor for me either, this instruction came from a parallels forum. it's a bid unclear for whom it worked and wether they used pro or player. Most success is connection to a bridged networking interface like Ethernet, I needed 2 interfaces per VM, so I added a Apple USB Ethernet Adapter there also is bridged

[Victoria9]

I don't know if this will help anyone, but from the top menu, I went to Virtual Machine to settings to network adapter and saw that "Share With My Mac" was not selected. After selecting that, I have internet connection once again after months of not having it. Also, I have the non-Pro version of VMware 12 and am running current Big Sur.

[atlauren]

If the afflicted also use Cisco AnyConnect, the release notes for AnyConnect version 4.10.02086 indicate this may be fixed.

-Andrew

 

[hd2659]

The problem I had with virtual networks "Could not connect 'Ethernet?" if more then 1 network was defined in Fusion Pro is solved after upgrade to 12.2.0.

From release notes, other issues mentioned in this thread seems to be resolved too.

- Unable to access port forwarding on a NAT virtual machine if the traffic is routed through the host IP stack on Big Sur hosts
- Jumbo Frame can't be enabled for NAT virtual machines and Host-only virtual networks on Big Sur hosts
- The virtual machine (VM) cannot access the same network as the host while macOS Big Sur host is connected to the virtual private network (VPN)

[gyrex_au]

I also have this issue with bridged network connections not working on Fusion 12.2. NAT connections work fine.

Are VMware aware of this issue? Are there any reliable fixes?

[hd2659]

I tested Bridged Networking / Ethernet and have no issues, I get an ip, mask, GW and dns servers from my DHCP running on my router

Fusion Pro = 12.2 MacOS=11.6

[JNY516]

VMware Fusion Professional Version e.x.p 18656771 with M1 BigSur 11.6

 

Windows 11 x64 ARM version does not show any network interfaces. I tried Sharing network with Mac, NAT, bridged but no luck.

 

Anything I can try/check? Install Vmware tools is grayed out. Perhaps not necessary for this version?

[Technogeezer]

 Questions about the tech Preview will get more attention if you post them in Fusion Tech Preview for Apple Silicon Discussions

You don’t say if you are running the Windows Insider preview or not, but the following discussion located there has a post that may get networking working for you https://communities.vmware.com/t5/Fusion-for-Apple-Silicon-Tech/Vmware-Fusion-Apple-Silicon-Support-Windows/td-p/2868054 

There are no VMware Tools available for Windows 10/11 on ARM  because Windows for ARM is not supported by Microsoft on Apple Silicon and VMware has decided not to support it until Microsoft does. Any guidance on it is via user to user interaction, not anything official from VMware.

[JNY516]

thanks!

The solution in the link worked and network is up.... Yes, running windows 11 preview x64 arm.