It’s an unlikely bug, but it’s really happened, as people around the world have discovered. After being powered off, VMWare’s ESX 3.5 Update 2 hypervisor refused to start again on August 12, ZDNet reports.
Martin Niemar, group manager of virtual infrastructure product marketing at VMware, said:
"We had an issue with 3.5 Update 2. It’s actually a licensing problem. 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."
