For Supermicro users (or those with intel 82573L e1000e) who have NIC troubles with 5.1 (that previously had no issues with 5.0) please see my post for a solution:
I had this problem also (Realtek 8168) in ESXi 5.1 few days ago, no network tracffic and PSOD when trying to bring vmnic down.
I found that only when I restarted the PC from Windows 7 and boot ESXi 5.1, this symptom happens. If I power off first, unplug power cord and wait for few seconds, and then start ESXi directly, NIC is working fine.
I'd extracted the driver of Realtek 8168 from 5.0u1 iso (vmtar -x NET-R816.V00), but still haven't tested it in 5.1 yet.
I replaced the driver net_r816.v00 from 5.0u1 iso to startup mount point (inside /vmfs/volumes), however still got the same problem. It looks like not as same as e1000 that can use 5.0u1 driver (applied from patch) to fix the issue. Because I don't want to re-install whole ESXi lab, I will keep using 5.1 and prevent using Windows before startup ESXi.
Any update on this topic? Anybody?
I tried jackhosy workaround, but still doesn't work in my case .
I don't think that this is such a big deal to get some help from VMware with this driver.
It's not like we're going to use it for productive traffic, but for lab environment would be excellent. This card is pretty popular around the products (desktop) sold out there.
If you have any suggestion, I'm willing to try it.
I upgraded from 5.0 where it worked fine on 5.1r8168 shows no errors, but the pings are going nowhere~ # Esxcfg-nics-lName PCI Driver Link Speed Duplex MAC Address MTU Descriptionvmnic0 0000:02:00.00 r8168 Up 100Mbps Full 00:16: e6: 84:2 d: f8 1500 Realtek Realtek 8168 Gigabit Ethernetvmnic1 0000:03:00.00 r8169 Up 100Mbps Full 84: c9: b2: 46: f0: 23 1500 D-Link System Inc DGE-528T Gigabit Ethernet Adapter
PS r8169 working ok
I am running VMware ESXi, 5.1.0, 799733 on ProLiant DL320 G5p with Embedded NC326i Dual Port Gigabit Server Adapter.
Everything works fine...!!!
Here it is the end of February and this issue in 5.1.0 has yet to be resolved? I'm finding the same issue with the Realtek 8111E NIC embedded onto the motherboard. After looking at the many log files and entries generated I believe there may be a of hint of reason for this NIC not functioning. In the VMkernal logs it shows at installation time it could not determine the correct hardware and chose to use the 8111B drivers. There may be something significantly different with this driver than the E version of chip.
I have installed a much older Realtek NIC in one of the PCI slots and everything is working fine, excluding the 8111E NIC.
It appears I have no other choice but to try the 5.0.0 version and see where I can get with getting this MOBO up with the onboard NIC.
I have the same problem, my motherboard is Asus P8Z77-V LE Plus, with Realtek 8111F. I'm getting an IP address in the boot, but not if I restart management connection.
What surprises me are people saying this 8111 (equivalent to the 8168) is a cheap controller, but yet it's on a $300+ motherboard which I don't consider being cheap. The cheap $10 Realtek 8169 I dropped into the PCI slot works just fine. I've tried installing the 5.0.0 drivers as I heard others say it worked for them, but alas it did not for me. Whether the onboard 8111 controller works or not seems to be dependant on the MOBO mfg and the model.
I was able to find a simple solution to my 8168/8111 delima purely by accident.I installed an LSI 9240-4i RAID controller and while it was recognized by the BIOS and VMware I had difficulty getting it to initialize. The RAID card is not the topic of dicussion, but during this diag procedure I found my Intel and the Realtek 8169 NIC I installed stopped working too.I tried everything I could think of until I just gave up and decided to choose the reset system configuration choice on the bottom of the menu.
Once I reset config and allowed the system to rediscover system hardware all NIC's came up and running, even the 8168. I scratched my head in wonderment and gift given, but curious as to why so I tried to break it again to figure out what happened and can't seem to break it. Bottom line, once your VMware software is installed and you have a 8168 either on your MOBO (motherboard) or an add-in card, try reseting as I did and see if everything comes online for you. You won't lose your VM files on the drive, but you will need to setup the virtual machines again. Good luck.
All, Do you have windows installed on this host? In my case r8168 will stop working only if i boot windows accidentally, and then restart host and boot ESXi. If i shutdown host first and then boot to vmware, everything is fine. Basically same behavior described by jackhosy.
Thank for the wise words. I just installed 5.1.o on a Dell XPS 8500. I couldn't get the nic to work and found your post and it works as it should. I can now ping my ESXI host. I tried to install 5.5 error message no network card detected.
So now I'm wondering how long it will stay running and if I set the nic to static if it will stay working. I will keep you posted. If it don't stay working when I set it to static I will reset again and update. Cheers
I reset my Dell XPS 8500 ESX 5.1 still working. I noticed a couple of request timed out. Set NIC to Static as well working. Thanks again
I followed your way and it worked too! That's an interesting phenomenon..