vMotion fails with the error: Error bad003F

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• If you move some new ESX/ESXi 4.1 Update 1 hosts into an existing cluster with ESX/ESXi 4.0 Update 2 hosts, migrating virtual machines onto the new host using vMotion fails.
• If you move some new ESXi 5.x hosts into an existing cluster with ESXi 5.x hosts, migrating virtual machines onto the new host using vMotion fails.
• vMotion fails between 9% and 28%.
• This issue occurs even when the vMotion network is set up correctly and vmkping between the hosts is successful.
• Issue may also occur for Storage vMotion.
• The virtual machine's vmware.log contains entries similar to:
  
  Mar 29 08:55:35.764: vmx| VMXAIOMGR: Using: simple=Generic unbuf=Generic
  Mar 29 08:55:35.778: vmx| MigratePlatformInitMigration: DiskOp file set to /vmfs/volumes/datastore/virtual_machine/virtual_machine.tmp
  Mar 29 08:55:35.785: vmx| MigrateWaitForData: waiting for data.
  Mar 29 08:55:35.786: vmx| MigrateSetState: Transitioning from state 7 to 8.
  Mar 29 08:56:55.360: vmx| MigrateSetStateFinished: type=2 new state=11
  Mar 29 08:56:55.361: vmx| MigrateSetState: Transitioning from state 8 to 11.
  Mar 29 08:56:55.362: vmx| Migrate_SetFailure: Failed waiting for data. Error bad003f. Connection closed by remote host, possibly due to timeout.
  Mar 29 08:56:55.362: vmx|
  Mar 29 08:56:55.363: vmx| Migrate: cleaning up migration state.
  Mar 29 08:56:55.363: vmx| MigrateSetState: Transitioning from state 11 to 0.
  Mar 29 08:56:55.364: vmx| Msg_Post: Error
  Mar 29 08:56:55.364: vmx| [vob.migrate.net.xfer.recvfailed.status] The migration transfer failed during the receive operation to socket 4100A43A7510: received 0/72 bytes: Timeout
  Mar 29 08:56:55.364b: vmx| [msg.moduletable.powerOnFailed] Module Migrate power on failed.
  Mar 29 08:56:55.365: vmx| ----------------------------------------
  Mar 29 08:56:55.372: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0
  Mar 29 08:56:55.429: vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
  Mar 29 08:56:56.460: vmx| Vix: [104976 mainDispatch.c:3571]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
  Mar 29 08:56:56.466: vmx| Vix: [104976 mainDispatch.c:3571]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
  Mar 29 08:56:56.467: vmx| Transitioned vmx/execState/val to poweredOff
  Mar 29 08:56:56.467: vmx| Vix: [104976 mainDispatch.c:3571]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0 additionalError=0
  Mar 29 08:56:56.468: vmx| Vix: [104976 mainDispatch.c:3597]: Error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): Unknown error
  Mar 29 08:56:56.468: vmx| VMX idle exit
  Mar 29 08:56:56.469: vmx| VMIOP: Exit
  Mar 29 08:56:56.470: vmx| Vix: [104976 mainDispatch.c:652]: VMAutomation_LateShutdown()
  Mar 29 08:56:56.471: vmx| Vix: [104976 mainDispatch.c:602]: VMAutomationCloseListenerSocket. Closing listener socket.
  Mar 29 08:56:56.478: vmx| Flushing VMX VMDB connections
  Mar 29 08:56:56.479: vmx| VmdbPipeStreamsOvlError: write failed, draining reads
  Mar 29 08:56:56.479: vmx| VmdbPipeStreamsOvlError: Couldn't initiate write
  Mar 29 08:56:56.482: vmx| VMX exit (0).
  Mar 29 08:56:56.482: vmx| VMX has left the building: 0.

Environment

VMware vCenter Server 5.5.x
VMware ESX 4.0.x
VMware vSphere ESXi 5.1
VMware ESXi 4.1.x Installable
VMware vSphere ESXi 5.0
VMware vCenter Server 5.0.x
VMware vCenter Server 4.1.x
VMware ESX 4.1.x
VMware vCenter Server 4.0.x
VMware vCenter Server 5.1.x
VMware ESXi 4.0.x Installable
VMware vSphere ESXi 5.5

Resolution

To resolve this issue, isolate the vMotion traffic by creating a separate vMotion network.

Additional Information

For related information, see Diagnosing VMware vMotion failure at 10% (1003734).
Understanding and troubleshooting vMotion
vMotion が次のエラーで失敗する：Error bad003F