Many customers are hitting a new bug in ESX preventing them from powering on virtual machines or VMotion them.Â There is a published knowledge base article on this which reads>>
Unable to Power On virtual machine with â€œA General System error occurred: Internal errorâ€
A virtual machine fails to power on, fails to leave suspend mode, or fails to migrate with VMotion and the following message is displayed in the vmware.log file for the virtual machine:
This product has expired. Be sure that your host machine’s date and time are set correctly.
There is a more recent version available at the VMware web site: https://www.vmware.com/info?id=4.
Module License Power on failed.
Currently running virtual machines will continue to run but will not be able to perform migration with VMotion, suspend or power on virtual machines.
An issue with ESX/ESXi 3.5 Update 2 causes the product license to expire on August 12, 2008. VMware engineering has isolated the root cause of this issue and will reissue the various upgrade media including the ESX 3.5 Update 2 ISO, ESXi 3.5 Update 2 ISO, ESX 3.5 Update 2 upgrade tar and zip files by noon, PST on August 13.Â These will be available from the page: https://www.vmware.com/download/vi.Â Until then, VMware advises against upgrading to ESX/ESXi 3.5 Update 2.
The Update patch bundles will be released separately later in the week.
This KB article will be updated as soon as more information is available, check back frequently for updates and additions.
A workaround to this ESX bug is to set the date back a day on your ESX hosts and you will be able to power on the VM’s again. If you use ntp, disable that for the time being and manually set your hosts back a day.Â Be careful, if you have your VMware tools configured to sync VM time to the host time then this will alter your VM times.
Here is the latest public news from VMware on this>>
An issue has been discovered by many VMware customers and partners with ESX/ESXi 3.5 Update 2 where Virtual Machines fail to power on or VMotion successfully.Â This problem began to occur on August 12, 2008 for customers that had upgraded to ESX 3.5 Update 2.Â The problem is caused by a build timeout that was mistakenly left enabled for the release build.
-Â Â Â VMware ESX 3.5 Update 2 & ESXi 3.5 Update 2 (pre-Update 2 releases are not impacted by this problem).
-Â Â Â Reports of problems with ESX 3.5 U1 with the following patches applied.
1.Â Â Â ESX350-200806201-UG
2.Â Â Â ESX350-200806202-UG
3.Â Â Â ESX350-200806217-UG
-Â Â Â No other VMware products are affected.
What has been done?:
-Â Â Â Product and Web teams pulled the ESX 3.5 Update 2 bits from the download pages last night so no more customers will be able to download the broken build.
-Â Â Â VMware Engineering teams have isolated the cause of the problem and are working around the clock to deliver updated builds and patches for impacted customers.
-Â Â Â A Knowledgebase article has been published (https://kb.vmware.com/kb/1006716), but traffic to the knowledgebase is causing time outs.Â A new static page has beenÂ published at https://www.vmware.com/support/esx35u2_supportalert.html that customers and partners will be able to view.
-Â Â Â The phone system has been updated to advise customers of the problem
-Â Â Â Vmware partners have been notified of the issue.
1)Â Â Â Do not install ESX 3.5 U2 if it has been downloaded from VMware’s website or elsewhere prior to August 12, 2008.
2)Â Â Â Set the host time to a date prior to August 12, 2008.Â This workaround has a number of very serious side affects that could impact product environments.Â Any Virtual Machines that sync time with the ESX host and serve time sensitive applications would be broken.Â These include, but are not limited to database servers, mail servers, & domain administration systems.
VMware to send an email to all customers who have downloaded this version. This effort is underway and should happen before 11 am today.
VMware Engineering has isolated the root cause and is working to produce an express patch for impacted customers today.Â The target timeframe is 6pm, August 12, 2008 PST.
1. What would this express patch do?
More information will be provided in subsequent communication updates.
2.Â Â Will VMware still reissue the upgrade media and patch bundles in the timeframe that has been communicated?
Yes.Â We still plan to reissue upgrade media by 6pm, August 13 PST (instead of noon, August 13 PST) and all update patch bundles later in the week. Â We will provide an ETA for the update patch bundles subsequently.Â NOTE: the “patch bundles” referred to here are for the patches listed above under “Affected Products” and the other bundles released at GA.Â They are not the same as the express patch which is targeted for 6pm, August 12, 2008 PST as stated above.
3.Â Â Why does VMware plan to reissue the upgrade media before the patch bundles?Â That is a wrong priority call!
This is not aÂ matter of priority.Â Since we can get done buildingÂ and testing the upgrade media before the patch bundles, we want to make that available to customers first instead of reissuing all the binaries later in the week.
4.Â Â Can VMware issue a patch that opens the licensing backdoor in the next hour as a critical measure?
There is no licensing backdoor in our code.
5.Â Â Does this issue affect VC 2.5 Update 2?
6.Â Â What is VMware doing to make sure that the problem won’t happen again?
We are making improvements on all fronts.Â The product team had endeavored to deliver a release with support customers deem important. Â But we fell short and we are deeply sorry about all the disruption and inconveniences we have caused.Â We have identified where the holes are and they will be addressed to restore customers’ confidence.