Unable to configure IP address for VM connected to custom virtual network on Big Sur hosts
book
Article ID: 315275
calendar_today
Updated On:
Products
VMware Desktop Hypervisor
Issue/Introduction
Symptoms: It is not possible to stop the built-in DHCP server of a virtual network on Big Sur hosts.
Environment
VMware Fusion 12.x
Cause
On Big Sur hosts, it is not possible to stop the built-in DHCP server of a virtual network. For each virtual network, it allocates the first half of a subnet for the DHCP server and leaves the second half for static IP assignment.
Resolution
To resolve this issue:
Use DHCP configuration for a VM connected to virtual network
Select VMware Fusion > Preferences and click Network.
Click the lock icon, enter the administrator password, and click OK.
Click the plus sign (+) under the list of networks.
Connect the VM to the new network through Setting > Network Adapter > NewNetworkName
In guest operation system, make sure it is configured to use DHCP configuration via network adapter settings
Use Static IP for a VM connected to virtual network
Select VMware Fusion > Preferences and click Network.
Click the lock icon, enter the administrator password, and click OK.
Click the plus sign (+) under the list of networks.
Connect VM to the new network via Setting > Network Adapter > NewNetworkName
In guest operation system, make sure it is configured to use static IP address via network adapter settings
In guest operation system, configure VM with static IP address within the subnet of virtual network.
For example: If the network is 192.168.1.0/255.255.255.0, then the first available address for static IP is 192.168.1.128, the IP address and subnet mask could be IP address: 192.168.1.128 Subnet mask: 255.255.255.0 Default gateway:192.168.1.1; If the network is 192.168.1.0/255.255.255.128, then the first available address for static IP is 192.168.1.64, the IP address and subnet mask could be IP address: 192.168.1.64 Subnet mask: 255.255.255.128 Default gateway:192.168.1.1