Grab our RSS feeds Follow us on Twitter Join our Facebook Group Connect with us on LinkedIn
myITforum.com, Powered by You.
you are not logged in

Articles

Newslinks

Links

Downloads

Site Services

Community Forums

Discussion Lists

Article Search

Newsletter

Web Blogs

FAQs

Live Support

myITforum TV

Take a Poll

Monthly Drawing

myITforum Network

User Group Directory

Our Partners

About Us

Register

Login

BRONZE PARTNER:

BRONZE PARTNER:



Industry News:




  Home : Articles : Virtualization print | email | | Forums |   print | email | | Blogs |   print | email | | Wiki |   print | email | | FAQs |   print | email | Article Search  
VMware ESX 3.5 update 2 -Serious bug


Bookmark and Share

By: Ian Lockhart
Posted On: 8/12/2008

We have just received notification from our technical account manager at VMware informing us that there is a serious bug in the latest build of ESX server. The message states:


***************************************


We have had a serious issue come up in ESX 3.5 U2 release. It looks like the build went out with a “time bomb” built in. Due to this the product will expire on 12th August 2008.

Any customer running 3.5 U2 will fail to power on any virtual machines after 11th Aug 2008.

Any power operations such as VMotion / Manual Power on, Reset, Suspend Resume are expected to fail.

Engineering has been alerted and are working on the issue. Please be assured that due to the seriousness of this problem this has the highest focus within VMware and a fix will be released ASAP.

The current work-around: turn off NTP or any time sync (if you're using it), and then manually set the date of all ESX 3.5u2 hosts back to 10th of August. This can be done either through the VI Client (Host -> Configuration -> Time Configuration) or by typing date -s "08/10/2008" at the Service Console command line on the ESX hosts.


***************************************

We are obviously still waiting to receive the promised update from VMware, but in the meantime I'm hoping that they're also developing a much better checking system before releasing their code (luckily we're only running test VMs on this box at the moment).


  myITforum.com ©2010 | Legal | Privacy