vMotion failed with "Failed waiting for data. Error 195887105. Failure."

[chen3961]

We encounter a problem that the VM vMotion can not work due to "Failed waiting for data. Error 195887105. Failure.". We have try many times, the error is same. We have check the vMotion connectivity by ping, each host can ping successful with the vMotion vmknic's IP. It confused us that we did not know meaning of the error code.

By check the  vmkernel.log, we found in content in tartget host:

cpu50:370526)VMotionRecv: 658: 1479347396653782 😧 Estimated network bandwidth 992.014 MB/s during pre-copy

cpu4:370525)VMotionSend: 4953: 1479347396653782 😧 Failed to receive state for message type 1: Failure

cpu4:370525)WARNING: VMotionSend: 3979: 1479347396653782 😧 failed to asynchronously receive and apply state from the remote host: Failure.

cpu4:370525)WARNING: Migrate: 270: 1479347396653782 😧 Failed: Failure (0xbad0001) @0x418002f0a786

cpu4:370525)WARNING: VMotionUtil: 6267: 1479347396653782 😧 timed out waiting 0 ms to transmit data.

and in the source host:

cpu8:1145788)WARNING: Heap: 3721: Heap dvfilter (131936/138416992): Maximum allowed growth (138285056) too small for size (190152704)

cpu8:1145788)WARNING: Heap: 4214: Heap_Align(dvfilter, 190150150/190150150 bytes, 8 align) failed.  caller: 0x4180327f9f45

cpu8:1145788)vsip VSIPDVFSaveState:1785: Received vMotion aborted signal...

cpu8:1145788)vsip VSIPDVFSaveState:1785: Received vMotion aborted signal...

cpu8:1145788)vsip VSIPDVFSaveState:1785: Received vMotion aborted signal...

cpu8:1145788)vsip VSIPDVFSaveState:1785: Received vMotion aborted signal...

cpu8:1145788)vsip VSIPDVFSaveState:1785: Received vMotion aborted signal...

cpu8:1145788)vsip VSIPDVFSaveState:1785: Received vMotion aborted signal...

cpu8:1145788)vsip VSIPDVFSaveState:1785: Received vMotion aborted signal...

cpu8:1145788)vsip VSIPDVFSaveState:1785: Received vMotion aborted signal...

cpu8:1145788)vsip VSIPDVFSaveState:1785: Received vMotion aborted signal...

cpu8:1145788)vsip VSIPDVFSaveState:1785: Received vMotion aborted signal...

cpu8:1145788)VMotionRecv: 3306: 1479347396653782 S: Error handling message: Failure

cpu8:1145788)WARNING: Migrate: 270: 1479347396653782 S: Failed: Failure (0xbad0001) @0x418031c14a3e

cpu24:1145785)WARNING: VMotionUtil: 733: 1479347396653782 S: failed to read stream keepalive: Connection closed by remote host, possibly due to timeout

We have used vspehre 6.0.0, anyone know this issue? and how to fix it?

[cesprov]

Are both the source and destination host on the same subnet?  If so, are the subnet masks set right for both?  I just ran into a similar issue the other day.  In my case I had just added three new hosts and had this issue vMotioing VMs from one host to any of the three new hosts.  It turned out the subnet mask on the source host was incorrectly set to a /26 instead of a /25 and the new hosts were just outside the /26 so it was trying to route the vMotion traffic out the VLAN interface and presumably back in the same interface.

Also, are jumbo frames in play here?  If so, make sure it's set on all vmkernels, vswitches, etc.

[ITIAnalyst]

When vMotion failed for us with Error 195887105 it was because somehow one of the Hosts had more than one VMkernel adapter configured with vMotion. Once the vMotion was removed from the wrong VMkernel adapter it worked again.

[zhouxg]

I would like to ask how the problem was solved later. Now I have the same problem.VMotion error 195887105

[IRIX201110141]

Most likely errors

- enable vmotion on VMKs which arrent configurated (network wise) for the vmotion traffic

- VLANIDs doesnt match the pSwitch configuration

- MTU doesnt match the VMK, vSwtich, pSwitch configuration

You can check on host level with an "vmkping -d -s 8972 <ip>" and speficy allways the sending VMKs with -i(or-I , i cant remember) vmkx. This is mandatory in a multi nic vmotion setup.

Regards,

Joerg

[xavier047]

This worked for me. Thanks

[birend1988]

@what % migration gets fail.

Are you using NSX in your environment??

[bayupw]

Sorry for hijacking this thread. birend1988​ have you experienced similar vMotion error with NSX?

One of my customer have this error but still figuring out if this is related to NSX or not.

[starvinbenadict]

I faced the same issue while vmotion for the particular virtual machine, rest of the VMs were vmotioned well, when i check the particular VM found 2 NIC, one network adapter without connecting network, i removed the disconnected network while migrating, it was successfully migrated.