Posted by: Raj Perumal
August 12th bug, http://kb2.vmware.com/kb/1006716.html, Hyper-V, Update 2 Bug, Update 2 bug fix, Update 2 bug resolution, Update 2 time bomb, Virtualization, VMWare, XenServer
As you may have now heard, VMWare has fixed the bug with update 2. They pulled the update and were finally able to release a fix. What does this tell us?
Even the largest of companies can have issues with their Q&A processes. No matter how perfect we endeavour to be there is always the human error factor. Does this mean you should abandon all your VMWare projects and head to greener pastures with Hyper-V and XenServer? I’m sure with the FUD machine in full swing, quite a few people from opposing camps will advise you to do this.
The fact of the matter is that will serve you no good as all of these companies will be sure to run into their own problems at some point in time. Like I’ve said before, if you adopt a proper patch management strategy you can avoid 99% of these problems.
Here is the link to the knowledge base article that outlines the issue and the fix with VMWare.