Posted by: badarrow
Barbara Darrow, Leading technology vendors, News, Server virtualization, Virtualization, VMware
The issues were triggered when the ESX 3.5 or ESXi 3.5 update 2 clocks hit midnight on August 12. At that point, code in the update triggers the user’s software license to expire. When that happens, virtual machines that are powered off may not be turned on and those that have been suspended may fail to leave suspend mode and VMs may not be migrated with VMotion.
The problem prompted new VMWare president Paul Maritz to publicly apologize for the agita.
Wrote Maritz: “I am sure you’re wondering how this could happen. WE failed in two areas: Not disabling the code in the final release of Update 2 and not catghing it in our quality assurance process.
The problem surfaced on this community thread.