rshroff wrote:
So I take ESXi 5.0 is smart enough to do true load balancing for vMotion based traffic with no concern to the load balancing algorithm specified for the corresponding port group.
ESXi 5.0 is smart to do it, if it has been setup in a certain way, described for example on Yellowbrick, so it has to be done with Port ID load balancing and Active/Standby configuration, several Vmkernel ports with IP and so on. If this has been setup then the vMotion traffic is load balanced (in a more "true" way actually than other VM traffic) across the available VMNICs.