vmware esxi booting issue

[rajeshrk]

I have installed esxi 6 in vmware workstation 12 .But after booting ,when i press f2 key for customise system it got stuck.I tried by restarting guest operating system,but i still getting the same .When i am pressing f2 key the boot page goes black.Please assist me on this issue .Please find the screenshot of the error page

[BenLiebowitz]

What OS is selected for the VM in settings? 

I see this KB article, it's for vSphere 5 but should still be the same process.

Installing ESXi 5.x in VMware Workstation (2034803) | VMware KB

[rajeshrk]

I have installed esxi 6.During booting process we have to enter f2 key.But when I press f2 there is no response,the page turning with black background.After that it remains in the same status

[a_p_]

Please check whether any of the console screens shows errors, when you press ALT-F11, and ALT-F12.

André

[BenLiebowitz]

When trying to press F2, did you click into the window first?  Try pressing space bar or a different key.  Does the window light up?  It should look similar to this:

The screenshot you provided looks like you're not clicked in...

[rajeshrk]

Yes I got the same page that you mentioned below. After that when I press f2 also  i tried to press space bar key .After some time the same page turned with black backgroud,without any change .Please help me out with this .Please view the error page again

[bluefirestorm]

What if you press Ctrl+G (to bring focus to the VM) and press Enter after that? Does it become Gray and Yellow again?

Based on the last JPG you attached, it looks your host screen resolution is 1366x768 and that you are running Workstation in Maximize (not Full Screen). Maybe that explains why there is a vertical scroll bar on it as well as the ESXi VM itself is 1024 x 768.

Have you tried not running Workstation without Maximize (at least with the ESXi VM) and see if it resolves it? Otherwise, change the Display Settings of the ESXi VM to 800x600 instead of "Use host settings for Monitor".

If that still doesn't resolve it, if you don't mind, attach the vmx and/or vmware.log of ESXi VM.