The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Cannot vMotion a virtual machine from an ESX/ESXi 4.1 host to an ESXi 5.0 host on NFS datastores (2009718)
- Performing a vMotion on a virtual machine from an ESX/ESXi 4.1 to ESXi 5.0 host fails on NFS datastores.
- The vMotion operation times out.
Note: The percentage of progress at which the operation times out varies, but is seen to occur at 9% in some cases.
- In the ESXi 5.0 VMkernel logs, you see the error:
WARNING: NFSLock: NFSLockGetServerLock:2123: File is being locked by a consumer on host qastoragebj-15.eng.vmware.com with exclusive lock.
NFSLock: NFSLock_Acquire:2769: failed to get lock on file rhel4-6348faee.vswp 0x41000ba3e740 on 10.112.125.99 (10.112.125.99): Busy
WARNING: Swap: vm 337820: OpenSwapFile:5664: Failed to open swap file '/vmfs/volumes/73857835-ab1391c7/workingdir/rhel4-6348faee.vswp': Busy
WARNING: VMotionRecv: ResolveSwapType:1366: 1291081286682539 D: failed to find a valid swapfile.
VMotionRecv: HelperProcessMessages:2848: 1291081286682539 D: Error handling message: Busy
WARNING: VMotionUtil: VMotionStreamCheckForStreamKeepalives:727: 1291081286682539 D: failed to read stream keepalive: Connection closed by remote host, possibly due to timeout
- You see NFS lock warnings similar to:
WARNING: NFSLock: 2407: Cannot remove lockfile .lck-ee08000000000000 : I/O error
WARNING: NFS: 1990: Failed to get attributes (I/O error)
This behavior is seen on NFS datastores if a Working Directory is defined or if the Swap file is not located in the home directory. It occurs due to the way in which ESX/ESXi 4.1 handles swap lock files.
For more information, see:
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.