VMware Cloud Community
NJKwork
Enthusiast
Enthusiast
Jump to solution

Which NIC for Windows 2008? E1000 or VMXNET 3?

In ESXi 4, Windows 2008 VMs seem to want to default to the E1000 model NIC when creating a new one. However, after reading the KB on this (), is seems the new VMXNET 3 is supported for Windows 2008 (and Windows 2003 for that matter).

So which is the best to use? It seems the VMXNET it the best choice because it has all the latest bells and whistles - but sometimes that is a bad thing too. The KB really does not say WHAT to use, but rather what options are available...unless I overlooked it.

Any advice?

SB

Reply
0 Kudos
27 Replies
jasoncllsystems
Enthusiast
Enthusiast
Jump to solution

Check out this http://communities.vmware.com/thread/208241?start=0&tstart=0

Regards,

Jas aka Superman

MALAYSIA VMware Communities

http://www.malaysiavm.com

'If you found this or any other answer useful please consider allocating points for helpful or correct answers ***

http://www.malaysiavm.com
Reply
0 Kudos
DerHesse
Contributor
Contributor
Jump to solution

I have the exact same issue on a Windows 2008 64bit VM.

All the settings on the guest and the host are correct.

--

David Hesse

IT-Support Professional and Virtualization Specialist

Tel: +353 87 9716178

VDI.com/DaHess

-- David Hesse SAN-Health Check Analyst and Solutions Deployment Specialist at Dell EMEA Expert Center Ireland (VCP3) Tel: +353 87 9716178
Reply
0 Kudos
beckhamk
Enthusiast
Enthusiast
Jump to solution

Has there been anymore progress made on this issue with regards to windows 2008 64bit not working correctly?

Reply
0 Kudos
Deb0
Contributor
Contributor
Jump to solution

I've been having problems with the VMXNET3 driver on win2008 x64 systems and had to roll back to the e1000.

Reply
0 Kudos
Scissor
Virtuoso
Virtuoso
Jump to solution

I've been having problems with the VMXNET3 driver on win2008 x64 systems and had to roll back to the e1000.

What problems?

Reply
0 Kudos
tegz
Contributor
Contributor
Jump to solution

Keep in mind that if your server has a static IP, it will need to be set again on the new adapter if you change from E1000 to vmxnet. If you are using a VLAN, it could explain the loss in connectivity until the IP is set on the new adapter.

Reply
0 Kudos
vChr1s
Contributor
Contributor
Jump to solution

I know I'm coming in late here but are there any issues with Server 2008 R2 x64.  Please take a look at my post as I have never experienced this before.

http://communities.vmware.com/message/1718589

Chris A. Consider awarding points for "helpful" and/or "correct" answers.
Reply
0 Kudos
PhoenixSWScully
Contributor
Contributor
Jump to solution

Anyway, on topic.

     I'm running 4 server 2008  x86 in both web cluster, and a sqlcluster (i know i know) and suffering performance issues. The VM simply 'Pauses' now and again. No errors, no performance log alerts. This causes obvious delay in the application.

     following this example, http://www.yellow-bricks.com/2010/02/02/e1000-and-dropped-rx-packets/ where they determined the e1000 was dropping packets, upgrading to vmxnet3 helped, I will try the vmxnet 3 and let you know if it improves my situation at all.

     just to bust the previous posters stones a bit, Anyone else feel like reading an entire other thread to get the info? What ever happened to a synopsis, sheesh. Thats like, the most obvious variation of a thread hijeck Iv ever seen. Sorry sir, callm like i see them. Here, see this wiki on the brief history of lanuage, once youve reasd the whole thing, you probably still wont understand what im saying, but youll have done as much work.

http://en.wikipedia.org/wiki/Language

Reply
0 Kudos