When migrating a VM to affected hosts, it gets stuck at 20 percent
search cancel

When migrating a VM to affected hosts, it gets stuck at 20 percent

book

Article ID: 412985

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • While performing vMotion from the affected host to another host in the cluster it works.
  • vMotion timing out from one host to all other hosts in the cluster with error on UI: Migration to host failed with error Timeout 
  • Migration progress is stuck (not progressing) at 20%
  • Errors observed on ESXi vmkernel.log on the vMotion source host:
    vMotion migration failed to read stream payload from network: Timeout.
    vMotion migration failed to send buffer to remote host: Timeout
    vMotion migration failed writing stream completion: Timeout
  • vmkping using vMotion vmk to destination host reports more than 0% packet loss (Testing VMkernel network connectivity with the vmkping command)
    example for vmk1 kernel used/tagged for vMotion, using vmotion netstack, destination host IP 172.16.1.10 and using 9000 MTU:
    vmkping -I vmk1 172.16.1.10 -s 8972 -S vmotion

Environment

VMware vSphere ESXi
VMware vCenter Server

 

Cause

Errors on network caused by a faulty cable on network card (vmnic)

Resolution

Cable replacement on the network card of the source host used for vMotion.

Additional Information

Powered by Wolken Software