Quick & Easy Way to Install
Express Patch Released by VMware. check here
http://vmware.com/landing_pages/esxexpresspatches.html
General System Error occurred: Internal error when powering up a vm on ESX 3.5 Update 2and ESX 3i 3.5 Update 2.
From the logs( /var/log/vmware/hostd.log) , Message from <host>: This product has expired.
Use the patch above.
The temporary work around is to change the date to before 10th Aug & power the vm’s. while its booting, change to current date. this workked for me
Step 1. > From VI CLient, click on ESX Host > Configuration > Time Configuration > Properties and change the time to before 10 aug 2008.
This should Power the VM on. Or stop NTP
Step 2. > Once your VM’s are turned on, change to current date.
Will post here once official fix is released by vmware.
also keep an eye on http://kb.vmware.com/kb/1006716
Have you tried restarting your license server?
Our entire organization runs on VM and we are is serouse situation now. Please post as soon as a update is released.
Yes have restarted the VC. I will post here as soon as I hear about the patch. The company I work is a VIP Enterprise and VAC Partner.
http://communities.vmware.com/thread/162377?tstart=0
KB (temporary not available)
http://kb.vmware.com/kb/1006716
Yea saw the Kb. Once the vm’s are powerd on, can change it to current date
Chandran, you might consider choosing a more direct update, like a phone call or other update directly from the offending vendor, in this instance, VMware, as opposed to looking to a blog for an update. Since your “entire organization runs on VM and we are is serouse situation now”. Expecting a blog to reply to you because you’ve posted that it’s urgent is somewhere between foolish and incompetent. It’s urgent for tens of thousands of ESX users around the world, you tool. Sorry english my broken not good so, very much to be thanking you. Ugh. Get a clue.
[...] ESX 3.5 update 2 August 12 bug Work. This is the bug. It bit me hard. The workaround is lame. The bug is lame. Me spending half the night trying to [...]
@ chandran & rajheet. keep an eye on http://kb.vmware.com/kb/1006716.
temporary workaround is to put the date back of the host & power the vm’s on while it booting, change to current date
[...] on the street is that VMware Infrastructure 3.5 Update 2 and ESXi 3.5 Update 2 have been affected by a [...]