Errors: "Failed waiting for data. Error 195887137. Timeout" and/or "Failed to queue disk I/O for unshared storage vMotion: Timeout" when attempting to vMotion a VM

Products

• VMware vSphere ESXi

Issue/Introduction

• In the vSphere Client and/or via the /var/log/hostd.log of the source host, one or more of the following errors appear:

Failed waiting for data. Error 195887137. Timeout.

Failed to queue disk I/O for unshared storage vMotion: Timeout

Failed to start migration pre-copy. Error: Connection closed by remote host, possibly due to timeout.

Failed to receive ###/### bytes from remote host <##.##.##.##>: Connection reset by peer

Failed to receive ###/### bytes from remote host <##.##.##.##>: Timeout

Migration transfer failed during receive operation to socket ###: received ### bytes: Connection reset by peer

Failed to read stream keepalive: Connection reset by peer Migration to host <##.##.##> failed with error Connection reset by peer (195887179)

vMotion migration ### failed to send buffer to remote host. ### failed writing stream completion: Timeout 

 

 

 

 

• /var/log/vmkernel.log on the source or destination host displays:

Tcpip_Vmk: 97: arp: ##:##:##:##:##:## is using my IP address ##.###.##.##.### on vmk#!

Cause

This issue occurs if there is a network connectivity issue and/or network misconfiguration between the source and destination host participating in the vMotion.

Resolution

Check the health and configuration of the vMotion network between the source and destination host participating in the vMotion.

 

Preparing Tasks

1. Identify the configured MTU used on the participating vMotion VMkernel ports (= vmks) by following KB Testing jumbo frame pings from ESXi over the network
2. Identify the vmnics (= network cards) used by the participating vMotion VMKernel ports by following the steps 1 & 2 in KB Testing VMkernel network connectivity with the vmkping command.

Checks

• Check for IP address conflicts. Each host should have a vMotion VMKernel port (= vmk) assigned a unique IP address
• Check for packet loss on the participating vmnics (= network cards) during and/or after the vMotion by following the troubleshooting steps of KB Troubleshooting vMotion fails with network errors
• Check the involved vmnics (= network cards) of the source and destination hosts for errors/dropped packets by following KB Troubleshooting NIC errors and other network traffic faults in ESXi
• Ensure that each participating vMotion VMKernel port group has the same security settings. A security mismatch can cause a vMotion operation to fail.
  
  For example, a failure occurs if the source VMKernel port group is set to allow promiscuous mode and the destination VMKernel port group is set to disallow promiscuous mode.
  • See the following KBs for more info:
    • KB How promiscuous mode works at the virtual switch and portgroup levels
    • KB Configuring promiscuous mode on a virtual switch or on specific port group

Additional Information

Understanding and troubleshooting vMotion