If your servers are not keeping accurate time under load, consider running an SP2 VMI enabled kernel (with paravirtualization checked - in Virtual Centre --> Edit Settings --> Options --> Parvitualization) using NTP for time synchronisation. Ensure that the VMwareTools time synch with host is disabled. Refer - VMware KB article - Timekeeping best practices for Linux
Noatime - consider adding this parameter to /etc/fstab to prevent the access time from being updated unless the access involves a modification of a file’s or directory’s metadata or content. This may be useful for backup, news servers, and mail servers where the extra disk activity associated with updating the access time is not desired. Avoiding the writes associated with updating the access time can result in measurable performance gains. Refer: http://www.novell.com/documentation/oes2/stor_nss_lx_nw/index.html?page=/documentation/oes2/stor_nss_lx_nw/data/b55ln8c.html
Consider turning off unnecessary services such as:
portmap
nfslock
netfs
autofs
smartd
acpid
gpm
nfs
nfsboot
splash
splash_early
Guest Installation
Linux manages the memory up to 896MB RAM linearly. This memory section is faster and more efficient. Bear this in mind with your VM guests - try to plan around using less than 896MB RAM to keep your guests running optimally.
There are a lot of complaints about the free VMware's remote console being slow and unreliable. All the VMware documentation for all versions of VMware suggest the use of the native remote access tools (ssh, RDP, etc) instead of the console if possible.