$ 0 0 We have just experienced this gotcha. Our fix was to use vmxnet3 adapters rather than e1000g0. Hope this helps Cheers