ESX 3.5 Update 2 refuses to start

VMware virtual machines on all hosts with the company's latest hypervisor, ESX 3.5 Update 2, in enterprise configurations have found that it will not power on after being turned off. The hypervisor refuses to start when the date is 12 August, with customers around the world discovering the problem as midnight was passed in their […]

VMware virtual machines on all hosts with the company's latest hypervisor, ESX 3.5 Update 2, in enterprise configurations have found that it will not power on after being turned off. The hypervisor refuses to start when the date is 12 August, with customers around the world discovering the problem as midnight was passed in their time zones.

A flaw in the VMware licensing code is responsible, according to Martin Niemar, group manager of virtual infrastructure product marketing at VMware, the most popular player in virtualisation.

“We had an issue with 3.5 Update 2. It's actually a licensing problem," said Niemar. "Currently, what we know is that licensing prevents new virtual machines from powering up after shutdowns, and it prevents virtual motioning, moving a virtual machine from one host to another.” Niemar said that VMware did not have a patch, but was working on one as a “top priority”.

Source:→ ZDNet Australia