If you are referring to http://kb.vmware.com/kb/2000091 this should have been fixed in ESXi 5.0 U2.
The KB article is not yet updated, but it's in the release notes of U2.
If you are referring to http://kb.vmware.com/kb/2000091 this should have been fixed in ESXi 5.0 U2.
The KB article is not yet updated, but it's in the release notes of U2.