One way you can kind of check in esxtop is switch to the memory view an enable the NUMA stats. I believe is NHN which is numa home node and that will tell you which numa node/socket the VM is running on. Normally they should be spread fairly evenly based on load over all your physical processors but in the case with this bug it would not move VMs around and favor 1 to 2 nodes. In my case with 4 cpu blades it would load everything up on 0 and 1 and rarely use nodes 2 and 3 which caused major issues with rdy time.
↧