banner
ZetoHkr

ZetoHkr

摸🐟从未停止,努力从未开始
github

VMware Fusion Pro startup virtual machine prompts Could not connect 'Ethernet0' to virtual network '/dev/vmnet1'.

Environment#

Operating System: MacOS Sequoia Version 15.3

Virtual Machine: VMware Fusion Pro 13

Virtual Machine System: Kail 2024.04

CPU: Intel i9-9980HK (16) @ 2.40GHz

GPU: Intel UHD Graphics 630, AMD Radeon Pro 5500M

Memory: 64GB

Solution#

There is a problem with the virtual network adapter, so we should start from the virtual network adapter. First, try restarting the virtual network adapter.

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

Output

Database file is not present.

Hmm? The database file does not exist? Let's continue to look for the problem and try to configure the virtual network adapter.

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

Output

Configuring Bridged network vmnet0
Configuring hostonly network vmnet1, probing for unused subnet ...
Failed to assign subnet address to hostonly network: vmnet1
Stopped all configured services on all networks

The error message 'Failed to assign subnet address to hostonly network: vmnet1' indicates that the automatic assignment of subnet address failed when configuring vmnet1 (host-only network). From this, we can guess that there might be an issue with the virtual machine network configuration. Let's continue checking the network configuration (/Library/Preferences/VMware\ Fusion/networking).

If there is no networking file, create a new one.

sudo nano /Library/Preferences/VMware\ Fusion/networking

If it is empty, write the following content:

VERSION=1,0
answer VNET_1_DHCP no
answer VNET_1_HOSTONLY_NETMASK 255.255.255.0
answer VNET_1_HOSTONLY_SUBNET 192.168.1.0
answer VNET_1_HOSTONLY_UUID 31E17A97-6F3C-41DB-932E-9D493E6FE614
answer VNET_1_VIRTUAL_ADAPTER yes
answer VNET_8_DHCP yes
answer VNET_8_DHCP_CFG_HASH 1781F166B1771BCF6EA9E45C44B81F5BDCA7175D
answer VNET_8_HOSTONLY_NETMASK 255.255.255.0
answer VNET_8_HOSTONLY_SUBNET 172.16.54.0
answer VNET_8_HOSTONLY_UUID 65DAB13D-9556-4300-9B2C-10B67BEB779F
answer VNET_8_NAT yes
answer VNET_8_VIRTUAL_ADAPTER yes

Explanation:

VERSION=1,0: Version of the virtual network adapter
answer VNET_1_DHCP no: VNET_1 virtual network adapter does not use DHCP
answer VNET_1_HOSTONLY_NETMASK 255.255.255.0: Subnet mask of VNET_1 virtual network adapter
answer VNET_1_HOSTONLY_SUBNET 192.168.1.0: This indicates the subnet of VNET_1 virtual network adapter
answer VNET_1_HOSTONLY_UUID 31E17A97-6F3C-41DB-932E-9D493E6FE614: Unique identifier for VNET_1 virtual network adapter (you can generate one yourself)
answer VNET_1_VIRTUAL_ADAPTER yes: VNET_1 virtual network adapter is virtual
answer VNET_8_DHCP yes: VNET_8 virtual network adapter uses DHCP
answer VNET_8_DHCP_CFG_HASH 1781F166B1771BCF6EA9E45C44B81F5BDCA7175D: This is the DHCP configuration hash for VNET_8 virtual network adapter (ensures uniqueness and integrity of DHCP configuration)
answer VNET_8_HOSTONLY_NETMASK 255.255.255.0: Subnet mask of VNET_8 virtual network adapter
answer VNET_8_HOSTONLY_SUBNET 172.16.54.0: Subnet of VNET_8 virtual network adapter
answer VNET_8_HOSTONLY_UUID 65DAB13D-9556-4300-9B2C-10B67BEB779F: Unique identifier for VNET_8 virtual network adapter (can be generated yourself)
answer VNET_8_NAT yes: VNET_8 virtual network adapter is NAT
answer VNET_8_VIRTUAL_ADAPTER yes: VNET_8 virtual network adapter is virtual

Try configuring the virtual network adapter again.

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

Output

Stopped all configured services on all networks
Backed up existing network settings to backup file "/tmp/vmware.UKyouv"
Restored network settings

At this point, we can see that the configuration was successful. Then, to ensure that the configuration takes effect, restart the computer. After the restart, try starting the virtual network adapter again.

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

Output

Enabled hostonly virtual adapter 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

Now we can see that the virtual network adapter started successfully.

Loading...
Ownership of this post data is guaranteed by blockchain and smart contracts to the creator alone.