vMotion for a particular VM errors out as:-
The VM failed to resume on the destination during early power on.
Could not create '/vmfs/volumes/54e1923e-f3f96bc8-07b6-ecf4bbceb228/USDC1UXAVMPRDV1/USDC1UXAVMPRDV1.nvram': msg.fileio.lock
Machine's vmware.log shows as :-
2015-02-22T01:00:25.694Z| vmx| W110: CONFIGDB: Ignoring request to write config file
2015-02-22T01:00:25.706Z| vmx| I120: GuestLib Generated SessionId 3503106828287461647
2015-02-22T01:00:25.706Z| vmx| I120: WORKER: Creating new group with numThreads=1 (4)
2015-02-22T01:00:25.706Z| vmx| I120: DISKUTIL: scsi1:2 : max toolsVersion = 2147483647
2015-02-22T01:00:25.706Z| vmx| I120: TOOLS setting legacy tools version to '2147483647', manifest status is 9
2015-02-22T01:00:25.706Z| vmx| I120: VMXVmdb_SetToolsVersionStatus: status value set to 'unmanaged', 'unmanaged', install possible
2015-02-22T01:00:25.706Z| vmx| I120: VMXVmdb_SetToolsVersionStatus: status value set to 'unmanaged', 'unmanaged', install possible
2015-02-22T01:00:25.727Z| vmx| I120: MsgHint: msg.tools.toolsReminder
2015-02-22T01:00:25.727Z| vmx| I120+ Install the VMware Tools package inside this virtual machine. After the guest operating system starts, select VM > Install VMware Tools⦠and follow the instructions.
2015-02-22T01:00:25.727Z| vmx| I120+ ---------------------------------------
2015-02-22T01:00:25.727Z| vmx| I120: Migrate: Automatically handling hint.
2015-02-22T01:00:25.727Z| vmx| I120: TOOLS INSTALL initializing state to IDLE on power on.
2015-02-22T01:00:33.736Z| vmx| W110: NVRAMMGR: No valid NVRAM file found, will create default NVRAM.
2015-02-22T01:00:37.751Z| vmx| I120: Msg_Post: Error
2015-02-22T01:00:37.751Z| vmx| I120: [msg.nvram.wback1] Could not create '/vmfs/volumes/54e1923e-f3f96bc8-07b6-ecf4bbceb228/Avamar-Proxy/Avamar-Proxy.nvram': Failed to lock the file
2015-02-22T01:00:37.751Z| vmx| I120: ----------------------------------------
2015-02-22T01:00:37.783Z| vmx| W110: NVRAMMGR: Failed to create default NVRAM file (Avamar-Proxy.nvram)
2015-02-22T01:00:37.783Z| vmx| I120: Module Nvman power on failed.
2015-02-22T01:00:37.783Z| vmx| I120: VMX_PowerOn: ModuleTable_PowerOn = 0
2015-02-22T01:00:37.783Z| vmx| I120: MigrateSetStateFinished: type=2 new state=11
2015-02-22T01:00:37.783Z| vmx| I120: MigrateSetState: Transitioning from state 10 to 11.
2015-02-22T01:00:37.783Z| vmx| I120: [msg.migrate.resume.fail] The VM failed to resume on the destination during early power on.
2015-02-22T01:00:37.784Z| vmx| I120: Msg_Post: Error
2015-02-22T01:00:37.784Z| vmx| I120: [msg.migrate.resume.fail] The VM failed to resume on the destination during early power on.
2015-02-22T01:00:37.784Z| vmx| I120: ----------------------------------------
2015-02-22T01:00:37.789Z| vmx| I120: SVMotion_PowerOff: Not running Storage vMotion. Nothing to do
2015-02-22T01:00:37.790Z| svga| I120: SVGA thread is exiting
2015-02-22T01:00:37.790Z| vmx| I120: Destroying virtual dev for scsi1:2 vscsi=8365
2015-02-22T01:00:37.790Z| vmx| I120: VMMon_VSCSIStopVports: No such target on adapter
2015-02-22T01:00:37.790Z| vmx| I120: Destroying virtual dev for scsi0:0 vscsi=8364
2015-02-22T01:00:37.790Z| vmx| I120: VMMon_VSCSIStopVports: No such target on adapter
2015-02-22T01:00:37.791Z| mks| I120: MKS PowerOff
2015-02-22T01:00:37.791Z| mks| I120: MKS thread is exiting
2015-02-22T01:00:37.792Z| vmx| I120: scsi1:2: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)
2015-02-22T01:00:37.792Z| vmx| I120: Closing disk scsi1:2
2015-02-22T01:00:37.792Z| vmx| I120: DISKLIB-CBT : Shutting down change tracking for untracked fid 17636129.
2015-02-22T01:00:37.792Z| vmx| I120: DISKLIB-CBT : Successfully disconnected CBT node.
2015-02-22T01:00:37.795Z| vmx| I120: DISKLIB-VMFS : "/vmfs/volumes/54e1923e-f3f96bc8-07b6-ecf4bbceb228/Avamar-Proxy/Avamar-Proxy_1-flat.vmdk" : closed.
Sam30, I have the same problem, did you ever find a solution? I'm able to vMotion the VMs in the powered off state...
have you looked through this kb?
Unfortunately nope, raised a case with VMware Tech Support even they couldn't find it. All they kept saying seems its locked somewhere but can't find where so rebooting the host only fixed the issue for me.
Any luck from vmware support?
I shut down the vm, ssh into one of the esx hosts that had access, and deleted the nvram file for that VM. When the vm booted back up, vmotion worked
So its a little better than shutting down the host.
Try Storage vMotion without host change .
for me helps only storage vmotion of configuration files and first HDD.
VM was:
1hdd - 60 GB
2HDD - 1.7 TB
3HDD - 800GB
Storage vmotion fixed the issue.