-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: E1000 NIC
Presumably, based on the VMware KB article mentioned in the release notes.
-
- Veteran
- Posts: 387
- Liked: 97 times
- Joined: Mar 24, 2010 5:47 pm
- Full Name: Larry Walker
- Contact:
Re: E1000 NIC
thanks, most of my vm's use the E1000, didnt want to update them all
-
- Veeam Software
- Posts: 649
- Liked: 170 times
- Joined: Dec 10, 2012 8:44 am
- Full Name: Nikita Efes
- Contact:
Re: E1000 NIC
VMWare KB says that E1000 are at risk zone too: http://kb.vmware.com/kb/2059053
I should mention, that according to our internal tests, E1000E gives PSODs quite often, while E1000 does it much more rarelly.
However if you have any of that NICs at your environment I would suggest to monitor your ESXi state in any way.
If PSOD happens with exception mentioned in VMWare KB - it's high time to follow the instructions, provided there.
I should mention, that according to our internal tests, E1000E gives PSODs quite often, while E1000 does it much more rarelly.
However if you have any of that NICs at your environment I would suggest to monitor your ESXi state in any way.
If PSOD happens with exception mentioned in VMWare KB - it's high time to follow the instructions, provided there.
-
- Veteran
- Posts: 387
- Liked: 97 times
- Joined: Mar 24, 2010 5:47 pm
- Full Name: Larry Walker
- Contact:
Re: E1000 NIC
thanks... but now that my head is out of the sand I will need to start changing them. Never had the PSOD but dont want to go there. Will need to find time just not sure where.
-
- Veeam Software
- Posts: 649
- Liked: 170 times
- Joined: Dec 10, 2012 8:44 am
- Full Name: Nikita Efes
- Contact:
Re: E1000 NIC
Please note that VMXNET3 have some oun bugs. For example, large packet loss: http://kb.vmware.com/kb/2039495
So if I were you I wold better stay on E1000 and wait until VMware will fix their bug with it, or move to VMXNET3 temporary and then come back to E1000, depending on size of your infrastructure.
So if I were you I wold better stay on E1000 and wait until VMware will fix their bug with it, or move to VMXNET3 temporary and then come back to E1000, depending on size of your infrastructure.
-
- VP, Product Management
- Posts: 6035
- Liked: 2860 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
- Contact:
Re: E1000 NIC
Also remember that you can also just disable RSS in the Windows guest OS. This is a good temporary workaround and is unlikely to make a measurable performance impact unless you have a VM that is regularly moving data at wire speed. In other words, this might not be a great option for servers that act as Veeam proxies/repositories, but for almost every other server you'll never notice the difference.
Then, once VMware releases the patch, just reenable it.
And yes, VMXNET3 is far from bug free, although it does seem that it's become much better. I've wasted a lot of time troubleshooting issues that were caused by VMXNET3 in the past, weird networking issues and performance problems.
Code: Select all
netsh interface tcp set global rss=disabled
Code: Select all
netsh interface tcp set global rss=enabled
-
- Veteran
- Posts: 387
- Liked: 97 times
- Joined: Mar 24, 2010 5:47 pm
- Full Name: Larry Walker
- Contact:
Re: E1000 NIC
thanks I will take the easy road when I can.
Who is online
Users browsing this forum: No registered users and 32 guests