In the vmware.log there is nothing useful, only I can see: Failed to load ~/.vmware/config
But nothing clear.
Could you attach the vmkernel.log and vmkwarning.log from the ESXi who hosts the VM?
Also, seems that your REDO log wasn't saved (because the power outage).
Before saying anything attach the logs in order to see what's going on.
I would suggest to modify the vm config file but you will lose some data there.
This may be a symptom of another problem.
If the host has a hardware RAID controller, see if the batteries are still good. Otherwise, a power failure often corrupts it and has to rebuild.
UPDATE: The VM actually did eventually complete power on, it took 45 minutes for the open of the vmdk that was stalling the power on, see the time gap between the first log entry below and subsequent entries:
2018-11-03T03:29:42.578Z| Worker#0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(2) fid = 134349, extentType = 0
2018-11-03T04:15:01.709Z| Worker#0| I120: DISKLIB-LIB : Opened "/vmfs/volumes/5646881e-ffd5861e-2a92-001999675f0e/Test CentOS 6.5/Test CentOS 6.5-000003.vmdk" (flags 0xa, type vmfs).
2018-11-03T04:15:01.709Z| Worker#0| I120: DISK: Disk '/vmfs/volumes/5646881e-ffd5861e-2a92-001999675f0e/Test CentOS 6.5/Test CentOS 6.5-000003.vmdk' has UUID '60 00 c2 9c 5c 96 e8 88-c8 be b0 fd 51 89 54 15'
2018-11-03T04:15:01.709Z| Worker#0| I120: DISK: OPEN '/vmfs/volumes/5646881e-ffd5861e-2a92-001999675f0e/Test CentOS 6.5/Test CentOS 6.5-000003.vmdk' Geo (133674/255/63) BIOS Geo (0/0/0)
2018-11-03T04:15:01.710Z| vmx| I120: DISK: Opening disks took 2719182 ms.
I performed a reboot of the VM and it gets through the power up normally now without getting stuck. The VM seems to operating just fine. Apparently it just fixed itself?
FYI the hardware RAID controller is showing normal status although it did report loss of cached data on the loss of power, it does not have battery backup. Requested logs are attached in case you want to take a look. Thanks guys for looking into this.