Latest Update on AUG 12 BUG confirms ESX/ESXi 3.5 VM reboots still required
August 13th, 2008 | 
Author: I just received the third VMware email customer update about the August 12 time bomb bug. Unfortunately, this email informs customers that the effort to find a resolution where VM reboots could be avoided has not produced a reliable process. The email does indicate that the express patches are working properly and are compatible with VMware Update Manager. Also, The previously set deadline of 6 PM PST today (AUG 13) for the download availability of the corrected ESX/ESXi update 2 install media is still on schedule.
Here’s the body of the entire email as I received it:
Dear VMware Customers,
We have released the express patches for the product expiration issue. Please go to http://www.vmware.com/go/esxexpresspatches for download and KB articles. Since our last customer email we have completed our verification tests that the express patches we’ve released are fully compatible with the VMware Update Manager. Please see the KB articles for deployment information regarding Update Manager.
The KB articles are kept up-to-date. Please refer to the KB articles for information and updates.
In our last update, we referred to an initiative by our support and engineering teams to find an option to apply the patch without the necessity of entering maintenance mode and VMotion of VM’s to other servers, or VM power-off and re-power-on. Our earlier tests have not found a consistently successful way to address this. We continue to investigate this possibility, as we know that it would reduce the maintenance burden on our customers who may not have a patched server available for VMotion.
We are on target to release updated versions of the ESX/ESXi 3.5 Update 2 patch at 6 PM PST today. This is for customers who have not already upgraded to the previously released version of ESX/ESXi 3.5 Update 2
Thank you,
The VMware ESX Product Team
Problem:
An issue has been discovered by many VMware customers and partners with ESX Update 2 (build number 103909) and ESXi 3.5 Update 2 (build number 103908) 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.
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: http://www.vmware.com/info?id=4.
————–
Module License Power on failed.Affected Products:
- VMware ESX 3.5 Update 2 & ESXi 3.5 Update 2. Thank you, The VMware ESX Product Team
- The problem will be seen if ESX350-200806201-UG is applied to a system.
- No other VMware products are affected.
Resolution:
VMware Engineering has produced express patches for impacted customers to resolve the issue.
Posted in 
Tags: 
