VMWare ESX problem booting VM's

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hi all,

Our esx server wont power on any vm's, I get an error of:

and in the server event log iI get this error after the fialed startup of a VM:

Very odd as I only upgraded to the latest version of ESX lastweek.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hi si

When you upgraded, are you sure you did the licensing part correctly? That error seems certain to be related either to licensing or (less likely) ntp problems.

 

Everything was working fine until today thats the odd part.

anyway I found the answer it seems to be a bug, rolled back the date on esx and the vm's start fine.

http://communities.vmware.com/thread/162377?tstart=0&start=0

 

If you did a major version upgrade (2.5 - 3 or 3 - 3.5) then your license file will need to be upgraded as well, as far as i recall

 

No just a build update, see link above for answer. Turned out its a bug in esx.

 

I was about to say had anyone else seen this issue, I came across it over on the edugeek forums.

 

Apologies for earlier Si - seems like I was on the right track as to what the issue was, but didn't know there was a major problem with u2. Just been browsing various posts on the VMWare forums - a lot of unhappy peeps out there running production systems that have been hosed by it.

VMWare are starting to experience a few 'issues' like this - I guess related to them now no longer being the equivalent of Barcelona playing in the Unibond league . The more companies with decent virtualisation products that they have to compete with, the more likely it is that QA will slip as a result - pound to a penny this is just an instance of some idiot manager at EMC screaming at VMWare techies to release code that just hasn't been quality checked.

Although, with all that said, I have to wonder at why someone would slap an update on a production system less than a week after its been released - unless they were experiencing major instability issues with an older version (something I haven't come across with u1) painful experience tells me that the risk of upgrading for the sake of it just aint worth it.

 

As far as I've read it seems to relate to update 2 and mostly to a specific date, namely 12th August. It could possibly be the expiration date of the beta for update 2 that is causing the problems.

In any case, if you change the date to sometime before the 12th of August it should start functioning properly.