unable to power on a virtual machine what logs to look for

[Anupreet01]

unable to power on a virtual machine what logs to look for

[peetz]

Check the Tasks&Events tab in the vSphere client.

Check the VM's log file in the datastore directory where your VM is stored.

What error message do you get when trying the power on operation?

- Andreas

[Anupreet01]

Backup snapshot removal failed = vm shutdown - cannot restart due to "file locked" error

[Anupreet01]

I am Checking the Vmkernel and vmkwarning

vmkernel

Reason: Failed to lock the file.----------------------------------------

Mar 14 15:16:03.716: vmx| Module DiskEarly power on failed.

Mar 14 15:16:03.718: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0

Mar 14 15:16:03.719: vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

Mar 14 15:16:03.754: vmx| Vix: [171831 mainDispatch.c:3248]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1

Mar 14 15:16:03.757: vmx| Vix: [171831 mainDispatch.c:3248]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1

Mar 14 15:16:03.758: vmx| Transitioned vmx/execState/val to poweredOff

Mar 14 15:16:03.759: vmx| Vix: [171831 mainDispatch.c:3248]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0

Mar 14 15:16:03.759: vmx| VMX idle exit

Mar 14 15:16:03.761: vmx| Vix: [171831 mainDispatch.c:599]: VMAutomation_LateShutdown()

Mar 14 15:16:03.762: vmx| Vix: [171831 mainDispatch.c:549]: VMAutomationCloseListenerSocket. Closing listener socket.

Mar 14 15:16:03.770: vmx| Flushing VMX VMDB connections

Mar 14 15:16:03.809: vmx| IPC_exit: disconnecting all threads

Mar 14 15:16:03.809: vmx| VMX exit (0).

Mar 14 15:16:03.810: vmx| AIOMGR-S : stat o=2 r=3 w=0 i=0 br=49152 bw=0

Mar 14 15:16:03.811: vmx| VMX has left the building: 0.

Vmkwarning

ar 14 15:15:43 vm vmkernel: 170:03:18:27.740 cpu11:4117)Config: 289: "VMOverheadGrowthLimit" = -1, Old Value: -1, (Status: 0x0)

Mar 14 15:15:43 vm vmkernel: 170:03:18:27.859 cpu1:4097)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x41000704e940) to NMP device "mpx.vmhba2:C0:T0:L0" failed on physical path "vmhba2:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

Mar 14 15:15:43 vm vmkernel: 170:03:18:27.859 cpu1:4097)ScsiDeviceIO: 747: Command 0x12 to device "mpx.vmhba2:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

Mar 14 15:15:54 vm vmkernel: 170:03:18:39.120 cpu8:4117)Config: 289: "HostLocalSwapDirEnabled" = 0, Old Value: 0, (Status: 0x0)

Mar 14 15:16:02 vm vmkernel: 170:03:18:47.045 cpu9:4118)World: vm 71831: 1098: Starting world vmware-vmx with flags 4

Mar 14 15:16:03 vm vmkernel: 170:03:18:47.987 cpu9:71831)World: vm 71832: 1098: Starting world vmm0:CTKA-MQIC with flags 8

Mar 14 15:16:03 vm vmkernel: 170:03:18:47.987 cpu9:71831)Sched: vm 71832: 5404: adding 'vmm0:CTKA-MQIC': group 'host/user': cpu: shares=-1 min=-1 minLimit=-1 max=-1

Mar 14 15:16:03 vm vmkernel: 170:03:18:47.987 cpu9:71831)Sched: vm 71832: 5423: renamed group 49 to vm.71831

Mar 14 15:16:03 vm vmkernel: 170:03:18:47.988 cpu9:71831)Sched: vm 71832: 5440: group 49 is located under group 4

Mar 14 15:16:03 vm vmkernel: 170:03:18:47.998 cpu9:71831)Swap: vm 71832: 2358: extending swap to 4194304 KB

Mar 14 15:16:03 vm vmkernel: 170:03:18:48.194 cpu9:71831)Sched: vm 71832: 1043: name='vmm0:CTKA-MQIC'

Mar 14 15:16:03 vm vmkernel: 170:03:18:48.194 cpu9:71831)CpuSched: vm 71832: 9282: zombified unscheduled world: runState=NEW

Mar 14 15:16:03 vm vmkernel: 170:03:18:48.194 cpu9:71831)World: vm 71832: 3066: deathPending set; world not running, scheduling reap

Mar 14 15:18:14 vm vmkernel: 170:03:20:58.483 cpu3:4099)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x4100072d0900) to NMP device "mpx.vmhba2:C0:T0:L0" failed on physical path "vmhba2:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

Mar 14 15:18:14 vm vmkernel: 170:03:20:58.483 cpu3:4099)ScsiDeviceIO: 747: Command 0x12 to device "mpx.vmhba2:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

Mar 14 15:18:15 vm vmkernel: [ACPI Debug]  String 170:03:20:59.755 cpu0:4096)[0x0a] "COMA _STA "

Mar 14 15:18:15 vm vmkernel: [ACPI Debug]  String 170:03:20:59.755 cpu0:4096)[0x06] "LDN:  "

Mar 14 15:18:15 vm vmkernel: [ACPI Debug]  Integer 170:03:20:59.755 cpu0:4096)0x       00000004

Mar 14 15:18:15 vm vmkernel: [ACPI Debug]  Integer 170:03:20:59.755 cpu0:4096)0x       0000000f

Mar 14 15:18:15 vm vmkernel: [ACPI Debug]  String 170:03:20:59.755 cpu0:4096)[0x0a] "COMB _STA "

Mar 14 15:18:15 vm vmkernel: [ACPI Debug]  String 170:03:20:59.755 cpu0:4096)[0x06] "LDN:  "

Mar 14 15:18:15 vm vmkernel: [ACPI Debug]  Integer 170:03:20:59.755 cpu0:4096)0x       00000005

Mar 14 15:18:15 vm vmkernel: [ACPI Debug]  Integer 170:03:20:59.755 cpu0:4096)0x       0000000f

Mar 14 15:18:15 vm vmkernel: [ACPI Debug]  String 170:03:20:59.755 cpu0:4096)[0x0a] "KYBD _STA "

Mar 14 15:18:15 vm vmkernel: [ACPI Debug]  Integer 170:03:20:59.755 cpu0:4096)0x       00000000

Mar 14 15:18:15 vm vmkernel: [ACPI Debug]  String 170:03:20:59.755 cpu0:4096)[0x09] "MOU _STA "

Mar 14 15:18:15 vm vmkernel: [ACPI Debug]  Integer 170:03:20:59.756 cpu0:4096)0x       00000000

Mar 14 15:18:15 vm vmkernel: 170:03:20:59.756 cpu0:4096)VMKAcpi: 2538: Found a disabled TPM device

Mar 14 15:18:24 vm vmkernel: 170:03:21:08.707 cpu1:4097)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x41000713d740) to NMP device "mpx.vmhba2

What other logs should i check ????????

[peetz]

See these KB articles:

Virtual machine powers off while creating or deleting snapshots with the error: Failed to lock the f...

Investigating virtual machine file locks on ESXi/ESX (10051)

[Anupreet01]

because according to the logs I think

http://kb.vmware.com/kb/8858900 is also applicable