1 publicly visible post • joined 7 Oct 2015
Hey nerds: this bug was fixed in the October 6th release of ESXi 6.0 U1a. Get back to work!