News Stay informed about the latest enterprise technology news and product updates.

VMware glitch locks up servers, fix won’t be available until tomorrow - Updated

Don’t you hate it when you go into iTunes and try to play a purchased song, and it won’t let you until it authenticates…again? Well, take away the authentication step and leave things hanging, multiply it by hundreds of enterprise virtual servers that cost far more than $0.99 each, and you’ve got what some IT managers have been experiencing today.

Thanks to an issue with VMware’s licensing code, VMs fail to power on, fail to leave suspend mode, or fail to migrate with VMotion – meaning those with HA/DR or other applications that require frequent migration of servers are having particular trouble.

According to VMware’s official site,

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:  Until then, VMware advises against upgrading to ESX/ESXi 3.5 Update 2.  

“Noon PST” August 13 – around 36 hours after the bug first struck today. Needless to say, VMware users are not happy.

My fellow blogger here on the Soup, Tory Skyers, hasn’t installed update 2 yet, but the glitch worries him nonetheless. “With all the headaches for VMware over the last couple of months, like the CEO leaving, I’m flabbergasted that they of all people would let something like this happen,” he told me today. For Skyers, this kind of bug was worse than flawed code. “It’s not really a bug per se – the license expiration is supposed to do what it’s doing, just not in these circumstances. This is a QA issue,” he said. 

Update: Just received a statement from VMware PR saying that while a fully-tested patch will still have to wait until tomorrow noon (PT), an “express patch” for production servers will be made available today. Let’s hope the express update is also bug-free!

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

Weird comment in your article: as I post this, it is 2:50pm EDT / 11:50AM PDT, so exactly what does this sentence mean? Noon PST August 13 - around 36 hours after the bug first struck today. Needless to say, VMware users are not happy. Are you posting from the future or something? Or did they skip over Daylight Savings time in your corner of the world?
i dunno, tsa, PST's also mentioned in the quote from the VMware website. PST, PDT, it's still a delay between bug and fix.