Paul Turner, Virtzilla’s veep for vSphere product management, told The Register that the source of the problem was Intel driver updates that arrived out of sync with VMware’s pre-release testing program. When users adopted the new drivers – one of which had been renamed – vSphere produced errors that meant virtual server fleet managers could not sustain high availability operations.

Source: LXer – VMware fixes vSphere release it pulled, sorts out Log4j while it’s at it