The network interface in your Ubuntu Hyper-V virtual machine fails to acquire an IP address after a host system upgrade due to driver incompatibilities or corrupted network configuration files. This issue typically stems from changes in the Linux kernel modules used by Hyper-V synthetic NICs, specifically the
hv_netvsc module, which may not initialize correctly with newer host versions. Resolving this requires verifying the module status, clearing stale network configurations, and ensuring the correct virtual switch settings are applied within the Hyper-V Manager.
Verify Network Module Status
The primary suspect for connectivity loss in Ubuntu on Hyper-V is the
hv_netvsc driver, which handles communication between the guest OS and the virtual network adapter. After a host upgrade, this module might fail to load or bind correctly. Start by checking if the module is present and loaded in the kernel. Open a terminal in your Ubuntu VM and run the following command:
lsmod | grep hv_netvsc
If the output is empty, the module is not loaded. You can attempt to load it manually using:
sudo modprobe hv_netvsc
Next, check the system logs for any errors related to this module during boot. Use the
dmesg command to filter for network-related messages:
dmesg | grep -i netvsc
Look for lines indicating "link up" or error codes such as "timeout" or "failed to send packet." If you see repeated failure messages, the driver is struggling to communicate with the hypervisor. In many cases, simply updating the Ubuntu packages can resolve driver mismatches. Run the standard update commands to ensure all kernel headers and Hyper-V specific packages are current:
sudo apt update
sudo apt upgrade
After upgrading, reboot the virtual machine to allow the new kernel modules to initialize properly.
Check Virtual Switch Configuration
Sometimes the issue lies not in the guest OS but in how the Hyper-V host presents the network to the VM. An upgrade might have reset or altered the virtual switch settings. Open Hyper-V Manager on your host machine and select your Ubuntu VM. Right-click and choose Settings. Navigate to the Network Adapter section. Ensure that the "Virtual switch" dropdown is set to the correct external or internal switch that provides internet access.
If you recently changed your physical network card or router, the binding of the Hyper-V virtual switch might have been disrupted. Go to the Host's Network Connections panel (ncpa.cpl) and verify that the Hyper-V Virtual Ethernet Adapter is enabled and has an IP configuration if required. Additionally, check if "MAC Address Spoofing" is enabled if you are using a custom MAC address or if the network requires specific MAC filtering. Disabling and re-adding the network adapter in the VM settings can also force Hyper-V to re-negotiate the connection parameters.
For more details on managing multiple network interfaces in Ubuntu Hyper-V setups, refer to our guide on
Understanding Two Network Interfaces in Ubuntu 22.04 with Hyper-V Virtual Machines.
Clear Stale Network Configurations
Ubuntu uses Netplan for network configuration in modern versions. After an upgrade, cached lease files or incorrect Netplan YAML structures can prevent DHCP from working. Check the contents of
/etc/netplan/. Look for files ending in
.yaml. A typical minimal configuration for a DHCP-enabled interface looks like this:
network:
version: 2
ethernets:
ens3:
dhcp4: true
Replace
ens3 with your actual interface name, which you can find using
ip link. If the file contains static IP settings that no longer match your network, change them to
dhcp4: true. Apply the changes with:
sudo netplan apply
If the command returns no errors but the interface still lacks an IP, try restarting the networking service or the NetworkManager service:
sudo systemctl restart NetworkManager
You can also delete the DHCP lease cache to force a fresh request. The leases are often stored in
/var/lib/dhcp/ or managed by NetworkManager in
/run/NetworkManager/dhcp/. Clearing these directories and rebooting can help.
Disable Secure Boot and Check Firmware
In some rare cases, especially after major host BIOS or firmware updates, Secure Boot can interfere with third-party or out-of-tree kernel modules like those used by Hyper-V. While Ubuntu usually handles this well, it is worth checking. Enter the VM's BIOS settings (usually F2 or Del during boot) and ensure Secure Boot is disabled. Additionally, ensure that the VM generation type (Gen 1 vs Gen 2) matches your hardware capabilities. Gen 2 VMs require UEFI and Secure Boot support, while Gen 1 uses legacy BIOS. Mismatched generations can cause hardware abstraction layer failures.
If you are experiencing broader connectivity issues between the host and the VM, such as being unable to ping the host, check our article on
Unable to Ping Hyper-V Host from Ubuntu VM for additional troubleshooting steps regarding firewall rules and routing tables.
Frequently Asked Questions
Why does my Ubuntu VM lose IP after a Windows update?
Windows updates often replace Hyper-V components or kernel drivers on the host, which can break compatibility with older Linux kernel modules inside the VM. Updating the Ubuntu kernel and Hyper-V integration services on the guest side usually restores compatibility with the new host drivers.
How do I find the correct interface name in Ubuntu?
Use the
ip addr show or
ip link command in the terminal. The interface names typically start with
ens,
enp, or
eth. Avoid hardcoding
eth0 as modern Linux systems use predictable naming conventions based on hardware topology.
Can I use a static IP instead of DHCP to fix this?
Yes, configuring a static IP via Netplan can bypass DHCP issues. However, this requires manual management of IP addresses, subnet masks, and gateways. It is generally recommended to stick with DHCP unless you have specific network requirements that necessitate static addressing.
What if the hv_netvsc module loads but there is no link?
This indicates a lower-level physical or virtual switch issue. Check the Hyper-V Manager settings to ensure the VM is connected to the correct virtual switch. Also, verify that the host's physical network adapter is functioning and that the virtual switch is bound to a working physical NIC.
Does disabling IPv6 help resolve this issue?
Sometimes, IPv6 misconfiguration can block IPv4 traffic or cause delays in network initialization. You can disable IPv6 in Netplan by setting
dhcp6: false and
accept-ra: false for the interface. Test if connectivity improves immediately after applying this change.