We had another example today of our customers helping us to correct a small peice of information that had potential for wreacking havoc with one's ESX/ESXi host.

At 11:55 this morning I received a Tweet from colleague John Troyer, alerting me that more than one customer he knew of had been hit with a PSOD (purple screen of death) while attempting to apply an upgrade to their ESX/ESXi host. Apparently, our Compatibility Matrix had an error in it for which versions the update to version 5.0 could apply.

A blog post on Wahl Network here talked more about the problem. I sprung into action and tapped my team of Knowledge Base writers for some insight. By 12:02 I had my answer. KB article 2009586 was written to speak to the issue and it turns out our Compatability Matrix was already being updated to indicate the correct versions after someone internally noticed the oversight.

The main message for this problem is-

Update your host to ESX/ESXi 4.1 Update 1 before adding it to vCenter Server 5.0


By 12:06, the originating blog had an update posted.

Twitter status
Isn't it incredible how quickly information can move when all the right bits are in place? If you ever spot something like this, Tweet me up at @VMwareKB, and we'll get it fixed lickity split!