So I have been happily using VMWare Fusion 12.1 on Big Sur for about a month when today, I was asked if I had moved or copied my VM. It said to say 'Copied' if unknown, so I did... now I am getting this error:
Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'.
whenever I launch my VM and sure enough, no network access for the VM.
I tried to solution noted elsewhere of using the commands
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd
from the command line but that didn't fix it. Even after a reboot and a reinstallation of VMWare Fusion, I still can't get it to work. There is a references to a VMware.log I am supposed to check, but the Console doesn't show that and searching for vmnet8 in the Console doesn't reveal anything in any of the logs. Any ideas?
A few questions:
My experience is that the question about a VM being "moved or copied" isn't asked unless something has happened on the Mac. I find that simply moving the VM from one folder to another will cause the question to appear.
The usual place for the VMware logs is in the VM bundle itself, not Console. In the macOS Finder, right click on the VM bundle and select "Show bundle contents" and you will find some logs in there as well as the VM files themselves.
A few answers:
I actually did look in the package earlier (since I knew VMWare had some command line told hosted there) but I can't find the log files inside the package. In fact I just went back and double checked and an "ls -alR" from the command line reveals no log files hidden in the package.
SAME HERE !!
I upgraded to macOS Big Sur 11.1 and found this problem. I ran smoothly when using Catalina.
I am running virtual Windows 10 Professional by VMware Fusion Player version 12.1.0 on MacBook Air 2020.
I tried the commands mentioned above, re-install VMware and create new virtual machines, but all can't work.
I'm feeling that you're looking in the wrong place for the log. The log is found in the virtual machine's directory, not the directory holding Fusion executables.
There are two ways to get to this directory easily:
Found the log file (thank you Technogeezer from a fellow geezer). Looked for relevant lines in the log and found the text below. Any ideas as to what it means in terms of the source of failure. It says it can't create the virtual interface, but what would status 1009 mean?:
2021-01-27T12:33:14.039-06:00| vcpu-0| I005: VNET: MACVNetMacosGetRealAdapterType: network type for adapter 0: 8
2021-01-27T12:33:14.039-06:00| vcpu-0| I005: VNET: MACVNetMacosGetVnetProperties: vnet properties: vnet=vmnet8, nat=yes, dhcp=yes (ignored), subnet=172.16.47.0, mask=255.255.255.0, firstAddr=172.16.47.1, lastAddr=172.16.47.127, isIPv6=no, IPv6Prefix=fd15:4ba5:5a2b:1008::, IPv6PrefixLen=64
2021-01-27T12:33:14.039-06:00| vcpu-0| I005: VNET: MACVNetPortVirtApiStartInterface: Waiting on semaphore for adapter: 0
2021-01-27T12:33:14.060-06:00| host-274654| I005: VNET: MACVNetPortVirtApiStartHandler: starting interface for adapter: 0, status: 1009
2021-01-27T12:33:14.060-06:00| host-274654| W003: VNET: MACVNetPortVirtApiStartHandler: unable to create virtual intrface for device: 0, status: 1009
2021-01-27T12:33:14.061-06:00| vcpu-0| I005: VNET: Semaphore signalled for adapter: 0, timeoutMs=5000, waitMs=21
2021-01-27T12:33:14.061-06:00| vcpu-0| W003: VNET: MACVNetPortVirtApiStartInterface: Failed to create interface for adapter: 0, handlerStatus: 1009
2021-01-27T12:33:14.094-06:00| vcpu-0| I005: VNET: MACVNetPort_Connect: Ethernet0: can't start virtual interface
2021-01-27T12:33:14.094-06:00| vcpu-0| I005: Msg_Post: Warning
2021-01-27T12:33:14.094-06:00| vcpu-0| I005: [msg.vnet.connectvnet] Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'. More information can be found in the vmware.log file.
I do have the same problem. Suddenly, the NAT Network cannot be started any more. Any suggestions how to fix this?
2021-04-18T16:11:56.752+02:00| vcpu-0| I005: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2021-04-18T16:11:56.756+02:00| vcpu-0| I005: VNET: MACVNetMacosGetRealAdapterType: network type for adapter 0: 8
2021-04-18T16:11:56.756+02:00| vcpu-0| I005: VNET: MACVNetMacosGetVnetProperties: vnet properties: vnet=vmnet8, nat=yes, dhcp=yes (ignored), subnet=172.16.238.0, mask=255.255.255.0, firstAddr=172.16.238.1, lastAddr=172.16.238.127, isIPv6=no, IPv6Prefix=fd15:4ba5:5a2b:1008::, IPv6PrefixLen=64
2021-04-18T16:11:56.756+02:00| vcpu-0| I005: VNET: MACVNetPortVirtApiStartInterface: Waiting on semaphore for adapter: 0
2021-04-18T16:11:56.782+02:00| host-32871| I005: VNET: MACVNetPortVirtApiStartHandler: starting interface for adapter: 0, status: 1001
2021-04-18T16:11:56.782+02:00| host-32871| W003: VNET: MACVNetPortVirtApiStartHandler: unable to create virtual intrface for device: 0, status: 1001
2021-04-18T16:11:56.782+02:00| vcpu-0| I005: VNET: Semaphore signalled for adapter: 0, timeoutMs=5000, waitMs=26
2021-04-18T16:11:56.782+02:00| vcpu-0| W003: VNET: MACVNetPortVirtApiStartInterface: Failed to create interface for adapter: 0, handlerStatus: 1001
2021-04-18T16:11:56.783+02:00| vcpu-0| I005: VNET: MACVNetPort_Connect: Ethernet0: can't start virtual interface
2021-04-18T16:11:56.783+02:00| vcpu-0| I005: Msg_Post: Warning
2021-04-18T16:11:56.783+02:00| vcpu-0| I005: [msg.vnet.connectvnet] Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'. More information can be found in the vmware.log file.
2021-04-18T16:11:56.783+02:00| vcpu-0| I005: [msg.device.startdisconnected] Virtual device 'Ethernet0' will start disconnected.
I've suddenly started seeing that pop up message "vmware fusion could not connect 'ethernet0' to virtual network" since upgrading to Big Sur 11.3.1. I have Fusion 12.1.1. Using NAT by default. Biggest pain for me is that avahi-daemon no longer does its thing so I can't connect to "hostname.local" from the Mac side. I have to temporarily switch to Bridged mode, then I can ssh in but VPN access does not work so I have to switch back to NAT. I tried the "rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist" thing but that didn't work.
Did any found any solution. If I use bridge mode I am loosing internet.
Same Problem, any body got resolution.! Hope VMware resolves this bug soon!
For me NAT works fine but when I use BRIDGE MODE it doesn't work. So I started using PARALLELS Instead of fusion
Here's what worked for me to get NAT working again with Big Sur:
It was turned off for me and still it didn't work.