T15:27:15.339Z| vmx| I125: MigrateVMXdrToSpec: type 2 unsharedSwap 1 memMinToTransfer 0 cpuMinToTransfer 0 numDisks 2 numStreamIps 0 numFtStreamIps 0 T15:27:15.339Z| vmx| I125: MigrateVMXdrToSpec: type: 2 srcIp= dstIp= mid=8976a899ed87f3c uuid=494f4907-2a69-4f71-b5cf-21b97d144098 priority=no checksumMemory=no maxDowntime=0 encrypted=0 resumeDuringPageIn=no latencyAware=yes diskOpFile= srcLogIp=> dstLogIp=> ftPrimaryIp=> ftSecondaryIp=> T15:27:15.339Z| vmx| I125: VigorTransportProcessClientPayload: opID=kfk64jly-8h07s-h5:d1f seq=3288: Receiving Migrate.PrepareSource request.

The vmkernel.log directed me to the vmware.log for the VM, but I still canвЂ™t figure this out вЂ“ any ideas why svMotion is failing? I can see the files being created in the target datastore etc. Ensure that the vMotion IPs are configured on source and destination hosts, the hosts are accessible, and so on.

Action: Check the reason in the event message to find the cause of the failure. This condition can occur if vMotion IPs are not configured, the source and destination hosts are not accessible, and so on. Possible Causes: The virtual machine did not migrate. There isnвЂ™t much in vCenter events that is relevant or helpful:Д®vent Type Description: Failed to migrate the virtual machine for reasons described in the event message We bought a new NFS array and I am in the process of moving our VMs: svMotion worked fine for some VMs but some VMs are failing svMotion with вЂњFailed to initialize the swap fileвЂќ and I canвЂ™t see why. This is an existing cluster and vMotion between hosts is working fine.

Vmware fusion mac vm screen flickers