ESXi Bugs – VMware Can’t Keep Letting This Happen!

There are a number of competing vendors (and industry watchers) waiting to capitalize on any weakness shown in the VMware stack and with the recent number of QA issues leading to a significant bugs popping up not abating, I wonder how much longer VMware can afford to continue to slip up before it genuinely hurts its standing.
The latest couple to watch out for have become common repeat offenders since the 5.5 release…problems with vMotion, Pathing leading to PDLs/APDs and CBT issues have seemed to be on repeat if you search through the VMwareKBs over the past twelve to eighteen months.
KB2143943 – vMotion Fails After Upgrading from a number of builds
KB2144657 – ESXi 6 may not fail over correctly after encountering a PDL
As a Service Provider the CBT bugs are the most worrying because they fundamentally threaten the integrity of backup data which is not something that IT Operation staff or end users who’s data is put at risk should have to worry about. Veeam have done a great job circumventing the issue, though these issues are being fixed with drastic measures like full CBT resets…On a IaaS Platform where machines are not easily scheduled for downtime this is a massive issue.

To be fair the VMware team do a great job and keep everyone up to date with issues as they arise and are generally fixed in quick time…VMware can’t afford to have many more:
Resolution:
This is a known issue affecting ESXi 6.0.
Currently, there is no resolution.
Especially if they are repeat bugs!
Well said Anthony! Hope it will improve soon.
Nice post mate. Very valid points.
Great post.
For us was a huge issue the CBT problem. Even using Veeam that was possible to “minimize” the problem, was still a huge problem to maintain.
Well I am pretty sure that company which can do it need to have their own sandbox. It s true that some huge bugs on core standard solutions like the CBT bug in ESXi is not acceptable. But software as a service is great until bugs. I can accept errors on vcac or system center bécause it is impacting thé management and not thé production stack. If some basic feature like vmotion, backup . . . are not valid so editor needs to wait to put their tools in GA. It s always thé course to have new functionality. New functionality are amazing but without compromise core solution.