VMware Communities
danifunker
Contributor
Contributor
‎10-21-2021 11:43 AM

Could not connect 'Ethernet0' to virtual network '/dev/vmnet8' on macOS 11.6 since 12.2.0 upgrade

Greetings, Since I updated my VMware Fusion Pro to 12.2.0 on my macOS 11.6 Big Sur machine, NAT functionality is not working.

Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'

 

Bridge mode works fine.

 

I'm also noticing some errors in one of the logs:

2021-10-21T18:18:03.148Z In(05) VMware Fusion DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
 
 
Also, where can I find 'vmware.log' ?
8 Replies
erikread
Enthusiast
Enthusiast
‎10-21-2021 12:09 PM

I am also having the same problem. Multiple VM's that were working yesterday no longer can access the internet. I haven't tried bridged networking but otherwise same issue as OP

0 Kudos
t-t-p
Contributor
Contributor
‎10-21-2021 12:20 PM

I'm glad I'm not the only one seeing this. There should be some vmware.log file in your "Virtual Machines.localized" area. For example:

592 [TPHUNG-LVDQ]ubuntu-1804.vmwarevm$ pwd
/Users/tphung/Virtual Machines.localized/ubuntu-1804.vmwarevm
593 [TPHUNG-LVDQ]ubuntu-1804.vmwarevm$ 

 

0 Kudos
erikread
Enthusiast
Enthusiast
‎10-22-2021 04:48 AM

Relevant part of my log

VNET: 'ethernet0' enable link state propagation, lsp.state = 5
2021-10-22T11:00:51.117Z In(05) vcpu-0 VNET: MacosVmnetVirtApiStartIsolatedInterface: Ethernet0: Starting isolated virtual interface, vmnet=vmnet8
2021-10-22T11:00:51.119Z In(05) vcpu-0 DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2021-10-22T11:00:51.126Z In(05) vcpu-0 VNET: MacosVmnetVirtApiStartIsolatedInterface: Ethernet0: uuid=AE2C63BF-172E-44FC-9D4B-13F2AE2BACFB
2021-10-22T11:00:51.126Z In(05) vcpu-0 VNET: MacosVmnetVirtApiStartIsolatedInterface: Ethernet0: connect adapter to host: connect=yes
2021-10-22T11:00:51.126Z In(05) vcpu-0 VNET: MacosVmnetVirtApiStartIsolatedInterface: Ethernet0: host adapter address: ip=192.168.183.1
2021-10-22T11:00:51.126Z In(05) vcpu-0 VNET: MacosVmnetVirtApiStartIsolatedInterface: Ethernet0: host adapter subnet: subnet=255.255.255.0
2021-10-22T11:00:51.126Z In(05) vcpu-0 VNET: MacosVmnetVirtApiStartIsolatedInterface: Ethernet0: MTU size is not configured, vmnet=vmnet8
2021-10-22T11:00:51.325Z In(05) host-279773 VNET: MacosVmnetVirtApiStartHandler: Ethernet0: starting interface, status=1001
2021-10-22T11:00:51.325Z Wa(03) host-279773 VNET: MacosVmnetVirtApiStartHandler: Ethernet0: unable to start the virtual interface, status=1001
2021-10-22T11:00:51.325Z Er(02) vcpu-0 VNET: MacosVmnetVirtApiStartInterface: Ethernet0: Error in start handler, status=1001
2021-10-22T11:00:51.327Z In(05) host-279773 VNET: MacosVmnetVirtApiStopHandler: Ethernet0: stopping virtual interface, status=1000
2021-10-22T11:00:51.327Z In(05) vcpu-0 VNET: MACVNetPort_Connect: Ethernet0: can't start virtual interface
2021-10-22T11:00:51.327Z In(05) vcpu-0 Msg_Post: Warning
2021-10-22T11:00:51.327Z In(05) vcpu-0 [msg.vnet.connectvnet] Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'. More information can be found in the vmware.log file.
2021-10-22T11:00:51.327Z In(05) vcpu-0 [msg.device.startdisconnected] Virtual device 'Ethernet0' will start disconnected.

0 Kudos
danifunker
Contributor
Contributor
‎10-22-2021 06:11 AM

Thanks for the direction on that!

 

Here is a sample of my log messages. I'm thinking this is a VMware Fusion 12.2.0 issue. Hopefully the devs will see this and get onto it soon.

Here's a snip of my logs

2021-10-22T12:54:58.175Z No(00) vmx ConfigDB: Setting guestInfo.detailed.data = <not printed>
2021-10-22T12:55:18.060Z In(05) vcpu-3 Guest: Mesa: SVGA3D; build: RELEASE; LLVM;
2021-10-22T12:55:18.061Z In(05) vcpu-3 Guest: Mesa: 21.0.3
2021-10-22T12:56:02.130Z In(05) vmx SOCKET creating new socket, connecting to /var/run/vmware/usbarb-socket
2021-10-22T12:56:02.131Z In(05) vmx SOCKET connect failed, error 2: No such file or directory
2021-10-22T12:56:02.131Z Wa(03) vmx USBArbLib: Failed to connect to USB Arbitrator, arbSocketname(/var/run/vmware/usbarb-socket). Error(0x6): Connection error.
2021-10-22T12:58:02.135Z In(05) vmx SOCKET creating new socket, connecting to /var/run/vmware/usbarb-socket
2021-10-22T12:58:02.136Z In(05) vmx SOCKET connect failed, error 2: No such file or directory
2021-10-22T12:58:02.136Z Wa(03) vmx USBArbLib: Failed to connect to USB Arbitrator, arbSocketname(/var/run/vmware/usbarb-socket). Error(0x6): Connection error.
2021-10-22T13:00:02.140Z In(05) vmx SOCKET creating new socket, connecting to /var/run/vmware/usbarb-socket
2021-10-22T13:00:02.141Z In(05) vmx SOCKET connect failed, error 2: No such file or directory
2021-10-22T13:00:02.142Z Wa(03) vmx USBArbLib: Failed to connect to USB Arbitrator, arbSocketname(/var/run/vmware/usbarb-socket). Error(0x6): Connection error.
2021-10-22T13:02:02.145Z In(05) vmx SOCKET creating new socket, connecting to /var/run/vmware/usbarb-socket
2021-10-22T13:02:02.146Z In(05) vmx SOCKET connect failed, error 2: No such file or directory
2021-10-22T13:02:02.146Z Wa(03) vmx USBArbLib: Failed to connect to USB Arbitrator, arbSocketname(/var/run/vmware/usbarb-socket). Error(0x6): Connection error.
2021-10-22T13:02:47.429Z In(05) vmx CPClipboard_SetItem: Set CPClipboard struct with data of size:19, format:1.
2021-10-22T13:02:51.015Z In(05) vcpu-1 Guest: Mesa: SVGA3D; build: RELEASE; LLVM;
2021-10-22T13:02:51.015Z In(05) vcpu-1 Guest: Mesa: 21.0.3
2021-10-22T13:03:56.844Z In(05) vmx TOOLS received request in VMX to set option 'synctime' -> '0'
2021-10-22T13:03:56.844Z No(00) vmx ConfigDB: Setting tools.syncTime = "FALSE"
2021-10-22T13:03:56.851Z In(05) vmx VMXVmdb_SetCfgState: cfgReqPath=/vm/#_VMX/vmx/cfgState/req/#a8/, remDevPath=/vm/#_VMX/vmx/vigor/setCfgStateReq/#4dd/in/
2021-10-22T13:03:56.878Z In(05) vmx TOOLS received request in VMX to set option 'synctime' -> '0'
2021-10-22T13:03:56.878Z No(00) vmx ConfigDB: Setting tools.syncTime = "FALSE"
2021-10-22T13:03:56.888Z No(00) vmx ConfigDB: Setting tools.upgrade.policy = "useGlobal"
2021-10-22T13:03:56.904Z No(00) vmx ConfigDB: Setting ethernet0.connectionType = "nat"
2021-10-22T13:03:56.913Z No(00) vmx ConfigDB: Setting ethernet0.addressType = "generated"
2021-10-22T13:03:56.913Z No(00) vmx ConfigDB: Setting ethernet0.generatedAddress = "00:0C:29:CF:15:9B"
2021-10-22T13:03:56.940Z No(00) vmx ConfigDB: Setting ethernet0.virtualDev = "e1000"
2021-10-22T13:03:56.976Z In(05) vmx VNET: 'ethernet0' enable link state propagation, lsp.state = 5
2021-10-22T13:03:56.976Z In(05) vmx VNET: MacosVmnetVirtApiStartIsolatedInterface: Ethernet0: Starting isolated virtual interface, vmnet=vmnet8
2021-10-22T13:03:56.979Z In(05) vmx DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2021-10-22T13:03:56.981Z In(05) vmx VNET: MacosVmnetVirtApiStartIsolatedInterface: Ethernet0: uuid=B31FFBEA-F70F-486B-AF38-278DCD2DB438
2021-10-22T13:03:56.981Z In(05) vmx VNET: MacosVmnetVirtApiStartIsolatedInterface: Ethernet0: connect adapter to host: connect=yes
2021-10-22T13:03:56.981Z In(05) vmx VNET: MacosVmnetVirtApiStartIsolatedInterface: Ethernet0: host adapter address: ip=10.0.0.1
2021-10-22T13:03:56.981Z In(05) vmx VNET: MacosVmnetVirtApiStartIsolatedInterface: Ethernet0: host adapter subnet: subnet=255.255.255.0
2021-10-22T13:03:56.981Z In(05) vmx VNET: MacosVmnetVirtApiStartIsolatedInterface: Ethernet0: MTU size is not configured, vmnet=vmnet8
2021-10-22T13:03:57.220Z In(05) host-1010189 VNET: MacosVmnetVirtApiStartHandler: Ethernet0: starting interface, status=1001
2021-10-22T13:03:57.221Z Wa(03) host-1010189 VNET: MacosVmnetVirtApiStartHandler: Ethernet0: unable to start the virtual interface, status=1001
2021-10-22T13:03:57.221Z Er(02) vmx VNET: MacosVmnetVirtApiStartInterface: Ethernet0: Error in start handler, status=1001
2021-10-22T13:03:57.227Z In(05) host-1010189 VNET: MacosVmnetVirtApiStopHandler: Ethernet0: stopping virtual interface, status=1000
2021-10-22T13:03:57.227Z In(05) vmx VNET: MACVNetPort_Connect: Ethernet0: can't start virtual interface
2021-10-22T13:03:57.228Z In(05) vmx Msg_Post: Error
2021-10-22T13:03:57.229Z In(05) vmx [msg.vnet.connectvnet] Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'. More information can be found in the vmware.log file.
2021-10-22T13:03:57.229Z In(05) vmx [msg.device.badconnect] Failed to connect virtual device 'Ethernet0'.
0 Kudos
erikread
Enthusiast
Enthusiast
‎10-22-2021 06:16 AM

Reverting to 12.1.x fixes the issue for me

colin519
Contributor
Contributor
‎10-22-2021 08:37 AM

This is definetly a bug in 12.2.0

Installing 12.1.2 fixes this issue.

Real question: does anyone actually test this stuff? 

 

Steps to Reproduce: 

-possess working VM of any kind, any OS with a Big Sur host.

-updates to 12.2.0

-try to go on the internet

 

How does that not get caught? 

Wonsil
Contributor
Contributor
‎11-07-2021 08:03 AM

Having same problem on Big Sur. Issue exists on new installs as well.

0 Kudos
jsbattig
Enthusiast
Enthusiast
‎11-11-2021 04:19 AM

vmware ruined multiple things related to networking with the 12.2.x update.

See my post: https://communities.vmware.com/t5/VMware-Fusion-Discussions/Fusion-12-2-breaks-otherwise-properly-wo...

0 Kudos