VMware VM won't power on

We recently upgraded our VMware host from ESXi 4.0 to 5.0.0 Build 914586.  Following that, I defined a Windows Server 2012 virtual machine that I subsequently tried, unsuccessfully, to boot.  I edited the settings to force the boot into BIOS mode so I could track the progress.  However, after I open a console window and then did a power on, nothing is seen; all I stare at is a black window.  The vSphere GUI says the VM has started and looking at the ESXi logs, it says the VM has moved from a state of VM_STATE_POWERING_ON to VM_STATE_ON.  What’s also weird is that the performance of the VM shows that it’s consuming 10% of the processor.

I’ve done this many times before so this is very strange.  I’ve attached the CD/DVD drive to the VM so that it should boot from my DVD drive to start the load of Windows 2012.  Has anyone else seen this or have any suggestions on how this can be resolved?
ejefferson213Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
0
ejefferson213Author Commented:
Thanks so much for your assistance!  Being a novice at VMware, please bare with me.  To answer your questions, we haven't installed the VMware tools yet because we can't even get the OS to load but pinging the ESXi host is possible and of course I'm accessing the ESXi host through vSphere.  

Looking at the articles you sent, they refer to a patch, 2007680, which looks like it's build 515841 (release date 12/15/11).  My current build is 914586.  Aren't the patch numbers constructed in such a way as to lead you to understand how far along in the life/patch cycle you are?  Therefore, shouldn't my level already have this patch applied?  Looking at what the article says, I'm tempted to apply Update 3 which should then (hopefully) resolve this issue.
0
Vaseem MohammedCommented:
Have you completed the initial setup of VM i.e., Operating System Installation? (not ESXi host)
Are you connecting to ESXi Host directly using vSphere Client?
After upgrading ESXi host from 4.0 to 5 have to tried using updated vSphere Client?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

ejefferson213Author Commented:
Not yet; after I defined the virtual machine via the vSphere client, I then tried using that GUI to power up and load Windows Server 2012 (to no avail).  So yes, I'm connecting to the ESXi host through the vSphere Client. And here's the funny thing, I updated my vSphere Client months ago when I upgraded another ESXi host to 5.0.  And on that machine I'm able to vSphere into and define/load a Windows Server 2012 machine just fine.  I was finally getting around to upgrading a, supposedly, identical server (Dell PowerEdge 1900).  (we're a small non-profit with NO money so we make the best of what we got for servers/PCs) So having done this previously, I thought this would be a walk-in-the-park.  Should I upgrade my vSphere Client again??

Maybe I need to upgrade my vSphere Client.  Earlier when I looked in the ESXi logs, I saw something odd that stated:

    SSL-Accept failed with BIO Error
    SSL handshake timeout for stream xxx.xxx.xxx.xxx, black listing it for 3000ms.

and xxx.xxx.xxx.xxx was the IP address of my PC from where I was running vSphere Client.  (I don't remember doing anything special with certificates...)
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Okay, lets' go back to basics, create a new VM, any OS (except Windows 2012), do you see the VM POST ?

This could be the dreaded vSphere Client BUG!!!!!

what is the Desktop OS , where you have installed the vSphere Client ?

You are not using WIndows 8 ?

I would download the latest vSphere Client for 5.0, which is U3
0
ejefferson213Author Commented:
Heading home but behind the scenes, having read your articles, I deleted the 2012 VM and recreated a VM based on Windows Server 2008 R2 and guess what,   same thing.  (no POST) and I'm doing this from a Windows 7 Pro machine.  When I get in tomorrow, I'll upgrade my vSphere client to see how that works and I'll let you know!   Thanks!!
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Okay, so it's not that the VMs, will not power on , it's you cannot connect.

The Console, is displayed via modified VNC, via Port 902.

telnet <ip address> 902

where IP Address is the ESXi server ?

do you get a connection?

also try restarting networking management agents?

It could be a bad upgrade! (4.0 to 5.0)

check and connect via IP Address.

also check you can resolve the Hostname via DNS, or create a hosts file entry.

This was a common issue of no console display to client.

Also disable firewall
0
ejefferson213Author Commented:
Please forgive me if I’m throwing you off with my terminology.  Using the vSphere client, I can get into my ESXi 5.0 host.  I can see the VMs that are defined including the new one I call DC2012-2 which is a Windows Server 2012 machine NOT powered on.  It’s when I open a console for DC2012-2 and try to power it on that nothing happens.  I don’t even see the POST steps.  I just updated my vSphere client with U3 and it still does the same thing (powered on the VM and no POST).  

I tried opening a console for a VM on that ESXi host that's running. A black window displays but nothing appears.  I can remote into the VM (which happens to be a Windows server), via Windows-RDP and it's fine.  It's just vSphere or ESXi not letting me manage the VMs.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, I understand exactly what's happening, or not happening....

see my post... to work through and debug this console output issue.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ejefferson213Author Commented:
Brilliant!  That's all it was. Soon as I stopped the firewall, I was off and running!  Thank you very much!!
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Glad you got it working - Simple Things!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.