VM IIS W2003 are using 2 vCPU and a Flexible NIC. VMware TOOLS is continuous. In outdo panel/add give ironmongery we can comprehend VMware Accelerated AMD PCNet Adapter. VMware TOOLS is continuous.
VM SQL 2005 are using 4 vCPU and a Enhanced vmxnet NIC. In outdo panel/add give ironmongery we can comprehend VMware PCI Ethernet Adapter #3.
The amenable driver can jog as a vmxnet NIC (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805).
ESX 3.5 kiss 4 positioning uses the console. With VMware TOOLS it should be a vmxnet NIC driver.
Are we using RHEL? YES.
Are we using multiple vCPUs? YES.
Are we using vmxnet driver? YES.
How can we mad the behavior of the amenable driver to permit any other network driver than vmxnet?
If this is right-hand – then we accept respective VM using go downhill network driver.