Hyper-V VM heartbeat keeps losing communication

Question

I have a Hyper-V hypervisor running Server 2019. It has 2 VMs, also running Server 2019. One of them keeps losing communication and I have to do a hard shutdown. The other one runs perfectly fine.

What can I do to find out what's causing this 1 VM to be such a pain? Logs/commands/etc.

Thanks!

Answer 1

Event Viewer: Start by checking the Event Viewer on the Hyper-V host for any related errors. Look under Applications and Services Logs > Microsoft > Hyper-V-VMMS and Hyper-V-Worker for any events that may indicate problems with the virtual machine.

Event Viewer: Also check the Event Viewer inside the problematic VM (if you can access it when it's still running), specifically under System and Application logs for network-related issues or service failures. Also, check for any Hyper-V Integration Services-related events.

1. Network Adapter Settings: Ensure that the virtual network adapters on the problematic VM are configured correctly. Sometimes, misconfigurations (such as improper VLAN settings or misassigned virtual switches) can cause intermittent connectivity issues.
2. You can also try changing the virtual network adapter from "Dynamic" to "Static" IP to see if that resolves the issue.

Get-VMNetworkAdapter -VMName "YourVMName" | Select-Object VMName, Name, SwitchName, MacAddress, StaticMacAddress

Hyper-V uses integration services to improve communication between the host and the guest OS. Make sure the integration services are installed and up to date on the problematic VM.

• If you're running an older version of the integration services, try updating them:
• From the Hyper-V Manager, right-click the VM and choose Insert Integration Services Setup Disk.
  • Inside the VM, install the updates.
• Test-Connection -ComputerName <VM_IP_Address> -Count 10 Resource Allocation: Ensure that your Hyper-V host isn’t under heavy load. Check the resource allocation for CPU, RAM, and disk usage on both the hypervisor and the VM. The VM could be losing communication due to resource contention.
  • Get-VM | Select-Object Name, CPUUsage, MemoryAssigned