Hi, interesting problem. I have an NFS datastore which I am able to live storage vmotion VM's to, however when I try to Vmotion anything off it I get the error: "A general system error ocurred: Source detected that destination failed to resume."
I've looked around and found the KB article on increasing the fsr.maxswitchover settings, however this is happening on all VM's, and that seems unlikely. As well, I can't power every VM off to make the change recommended by that KB article. FWIW, I am able to migrate data off the NFS datastore when VM's are powered off.
THe vmware.log from a recent attempt is pasted below with data from the relevant time frame.
Dec 08 20:00:14.822: vmx| VMXVmdbCbVmVmxMigrate: Got SET callback for /vm/#_VMX/vmx/migrateState/cmd/##11_3da1f/op/=to
Dec 08 20:00:14.824: vmx| VmxMigrateGetParam: type: 1 srcIp=<10.10.50.11> dstIp=<10.10.50.11> mid=47a42e382fdb5 uuid=44454c4c-0000-1020-8020-80c04f202020 priority=none checksumMemory=no maxDowntime=0 encrypted=0 resumeDuringPageIn=no
Dec 08 20:00:14.827: vmx| VmxMigrateGetParam: type 1 unsharedSwap 1 memMinToTransfer 0 cpuMinToTransfer 0 numDisks 0
Dec 08 20:00:14.828: vmx| Received migrate 'to' request for mid id 1260327610285493, src ip <10.10.50.11>, dst ip <10.10.50.11>.
Dec 08 20:00:14.939: vmx| MigrateSetInfo: state=1 srcIp=<10.10.50.11> dstIp=<10.10.50.11> mid=1260327610285493 uuid=44454c4c-0000-1020-8020-80c04f202020 priority=low
Dec 08 20:00:14.939: vmx| MigrateStateUpdate: Transitioning from state 0 to 1.
Dec 08 20:00:17.535: vmx| VMXVmdbCbVmVmxMigrate: Got SET callback for /vm/#_VMX/vmx/migrateState/cmd/##11_3da29/op/=start
Dec 08 20:00:17.538: vmx| VmxMigrateGetStartParam: mid=47a42e382fdb5 dstwid=13603
Dec 08 20:00:17.540: vmx| Received migrate 'start' request for mig id 1260327610285493, dest world id 13603.
Dec 08 20:00:17.543: vmx| MigrateStateUpdate: Transitioning from state 1 to 2.
Dec 08 20:00:21.033: vcpu-0| MigrateStateUpdate: Transitioning from state 2 to 3.
Dec 08 20:00:21.043: vcpu-0| Migrate: Preparing to suspend.
Dec 08 20:00:21.060: vcpu-0| CPT current = 0, requesting 1
Dec 08 20:00:21.061: vcpu-0| Migrate: VM stun started, waiting 100 seconds for go/no-go message.
Dec 08 20:00:21.075: vcpu-0| Sync monModules(1).
Dec 08 20:00:21.076: vcpu-0| Done Sync monModules(1).
Dec 08 20:00:21.076: vmx| CPT: monitor ACKing mode 1
Dec 08 20:00:21.077: vmx| Destroying virtual dev for scsi0:0 vscsi=8244
Dec 08 20:00:21.081: vmx| VMMon_VSCSIStopVports: No such target on adapter
Dec 08 20:00:21.146: vmx| DISKLIB-VMFS : "/vmfs/volumes/725d7b94-b09d0694/DC01/DC01-flat.vmdk" : closed.
Dec 08 20:00:21.154: vmx| CPT current = 1, requesting 2
Dec 08 20:00:21.154: vmx| CPT: monitor ACKing mode 2
Dec 08 20:00:21.155: vmx| CPT current = 2, requesting 3
Dec 08 20:00:21.155: vcpu-0| Cpt monModules(3).
Dec 08 20:00:21.156: vcpu-0| Done Cpt monModules(3).
Dec 08 20:00:21.156: vmx| CPT: monitor ACKing mode 3
Dec 08 20:00:21.157: vmx| Migrate_Open: Migrating to <10.10.50.11> with migration id 1260327610285493
Dec 08 20:00:21.157: vmx| Checkpointed in VMware ESX, 4.0.0 build-193498, build-193498, Linux Host
Dec 08 20:00:21.158: vmx| BusMemSample: checkpoint 3 initPercent 75 touched 5242
Dec 08 20:00:21.648: vmx| DISKLIB-VMFS : "/vmfs/volumes/725d7b94-b09d0694/DC01/DC01-flat.vmdk" : open successful (21) size = 21474836480, hd = 0. Type 3
Dec 08 20:00:21.650: vmx| DISKLIB-VMFS : "/vmfs/volumes/725d7b94-b09d0694/DC01/DC01-flat.vmdk" : closed.
Dec 08 20:00:21.690: vmx| GuestRpc: Reinitializing Channel 0(toolbox)
Dec 08 20:00:21.712: vmx| GuestMsg: Channel 0, Cannot unpost because the previous post is already completed
Dec 08 20:00:21.719: vmx| GuestRpc: Channel 0 reinitialized.
Dec 08 20:00:21.829: vmx| Migrate: VM successfully stunned.
Dec 08 20:00:21.834: vmx| MigrateStateUpdate: Transitioning from state 3 to 4.
Dec 08 20:00:22.431: vmx| MigrateSetStateFinished: type=1 new state=5
Dec 08 20:00:22.433: vmx| MigrateStateUpdate: Transitioning from state 4 to 5.
Dec 08 20:00:22.434: vmx| Migrate_SetFailure: switching to new log file.
Dec 08 20:00:22.979: vmx| Migrate_SetFailure: Now in new log file.
Dec 08 20:00:22.987: vmx| Migrate_SetFailure: Source detected that destination failed to resume.
Dec 08 20:00:23.003: vmx| Migrate: Attempting to continue running on the source.
Dec 08 20:00:23.022: vmx| CPT current = 3, requesting 6
Dec 08 20:00:23.022: vmx| Checkpoint_Unstun: vm stopped for 1962106 us
Dec 08 20:00:23.024: vcpu-0| Sync monModules(6).
Dec 08 20:00:23.025: vcpu-0| LSI:Telling vmk to set async to 1(CONT_SYNC)
Dec 08 20:00:23.025: vcpu-0| Done Sync monModules(6).
Dec 08 20:00:23.026: vmx| CPT: monitor ACKing mode 6
Dec 08 20:00:23.028: vmx| DISK: OPEN scsi0:0 '/vmfs/volumes/725d7b94-b09d0694/DC01/DC01.vmdk' persistent R[]
Dec 08 20:00:23.410: vmx| DISKLIB-VMFS : "/vmfs/volumes/725d7b94-b09d0694/DC01/DC01-flat.vmdk" : open successful (10) size = 21474836480, hd = 16482656. Type 3
Dec 08 20:00:23.410: vmx| DISKLIB-DSCPTR: Opened : "DC01-flat.vmdk" (0xa)
Dec 08 20:00:23.411: vmx| DISKLIB-LINK : Opened '/vmfs/volumes/725d7b94-b09d0694/DC01/DC01.vmdk' (0xa): vmfs, 41943040 sectors / 20 GB.
Dec 08 20:00:23.414: vmx| DISKLIB-LIB : Opened "/vmfs/volumes/725d7b94-b09d0694/DC01/DC01.vmdk" (flags 0xa).
Dec 08 20:00:23.415: vmx| DISK: OPEN '/vmfs/volumes/725d7b94-b09d0694/DC01/DC01.vmdk' Geo (2610/255/63) BIOS Geo (0/0/0)
Dec 08 20:00:23.416: vmx| Creating virtual dev for scsi0:0
Dec 08 20:00:23.417: vmx| DumpDiskInfo: scsi0:0 createType=11, capacity = 41943040, numLinks = 1, allocationType = 0
Dec 08 20:00:23.419: vmx| SCSIDiskESXPopulateVDevDesc: Using FS backend
Dec 08 20:00:23.965: vmx| Migrate: cleaning up migration state.
Dec 08 20:00:23.965: vmx| MigrateStateUpdate: Transitioning from state 5 to 0.
Dec 08 20:00:23.984: vcpu-0| GuestRpc: Channel 0, guest application toolbox.
Dec 08 20:00:23.984: vcpu-0| TOOLS Reducing idleLoopSpinUS to 500us
Dec 08 20:00:24.067: vcpu-0| TOOLS autoupgrade protocol version 2
Dec 08 20:00:24.074: vcpu-0| TOOLS ToolsCapabilityGuestTempDirectory received 1 C:\WINDOWS\TEMP
Dec 08 20:00:24.083: vcpu-0| TOOLS ToolsCapabilityGuestConfDirectory received C:\Documents and Settings\All Users\Application Data\VMware\VMware Tools
Dec 08 20:00:24.098: vcpu-0| ToolsSetVersionWork did nothing; new tools version (8193) matches old Tools version
Dec 08 20:00:24.106: vcpu-0| Guest: toolbox: Version: build-164009
Dec 08 20:00:24.107: vcpu-0| TOOLS unified loop capability requested by 'toolbox'; now sending options via TCLO
Dec 08 20:00:24.343: vcpu-0| HBACommon: First write on scsi0:0.fileName='/vmfs/volumes/725d7b94-b09d0694/DC01/DC01.vmdk'
Dec 08 20:00:24.368: vcpu-0| DISKLIB-CHAIN : UpdateContentID: old = 0x60636a5e, new = 0x1453b1e0
Dec 08 20:00:24.369: vcpu-0| DISKLIB-DDB : "longContentID" = "0896653fb3770222fcfc38791453b1e0" (was "410b9bcac5ad964208b242c060636a5e")
Dec 08 20:00:24.432: vcpu-0| DISKLIB-CHAIN : UpdateContentID: updated long content id
Dec 08 20:00:46.508: vcpu-0| DecoderIsInvalidInstruction:691 0x77e65520 #UD fc43ffff sz=2 ct=0
Any advice would be appreciated. Thanks.