Timebomb in VMware ESX & ESXi Server Update 2

by David Davis [Published on 13 Aug. 2008 / Last Updated on 13 Aug. 2008]

There is a bug in VMware ESXi Server Update 2 such that virtual servers cannot power up after August 12. To me, this is what is called a "timebomb". Meaning, you installed the two and a half weeks ago, tested it, and everything seemed fine. However, on a certain date at a certain time, the software ceases to function - traditional timebomb!

Now, was this timebomb intentional? While most timebombs are intentional, it doesn't sound like this one was.

The actual error on the VI client is "The VI Client threw the error 'A general system error occurred: Internal Error." The manual workaround is to disable NTP and manually set the date and time back several days.

Just this morning, VMware released an 'express patch' that resolves this critical issue.
For more information see:  VMware licensing bug blacks out virtual servers

There is a bug in VMware ESXi Server Update 2 such that virtual servers cannot power up after August 12. To me, this is what is called a "timebomb". Meaning, you installed the two and a half weeks ago, tested it, and everything seemed fine. However, on a certain date at a certain time, the software ceases to function - traditional timebomb! Now, was this timebomb intentional? While most timebombs are intentional, it doesn't sound like this one was. The actual error on the VI client is "The VI Client threw the error 'A general system error occurred: Internal Error." The manual workaround is to disable NTP and manually set the date and time back several days. Just this morning, VMware released an 'express patch' that resolves this critical issue. For more information see:  VMware licensing bug blacks out virtual servers

Add Review or Comment

Featured Links