I know this is a bit old, but thank you frutis! So far so good with this oem.tgz with the Realtek RTL8111DL on my MSI 785GM-E51.

Haven't done anything yet to "stress" it, but I've had it up and running for over a day now and been able to connect to the server multiple times with the vSphere Client.

Very simple.. used Workstation to install ESX to a 1GB flash drive. Then booted up an Ubuntu VM and inserted the oem.tgz file into the Hypervisor1 partition. For some reason my CentOS5 VM wouldn't insert it properly.

Inserted USB stick into my ESXi machine and had to make no changes. Now onto connecting to my NFS share to get some VM's loaded up.

UPDATE: Since connecting to my NFS share, I successfully imported a Win7 VM that is stored on the NFS share itself, and it has had zero network connectivity issues.

Hi,

I've bought a 10 Pound PCI card with an r8169 to get my ESXi server up, and I've been using the module from mymod-network.new2, which is in fact the one from the first post in this thread, quite successfully. I can connect to the server and use the console, but I've noticed that any data transfers to VMs or console get interrupted a lot - the only way I was able to transfer files to the box was using SCP with constant reconnects...

Looking at the diagnostics, I see a "Module r8169 was loaded but has not signature attached" and more importantly lots of failed assertions for the r8169 module in the vmkernel log. I originally installed ESX 4.0 with the oem.tgz and then upgraded to 4.1, but I haven't installed any of these January patches.

I tried compiling my own drivers off the Realtek source code, but just like when I tried compiling drivers for my on-board bcm4400 chip, I get lots of undefined symbols...

Any chance of getting this to work more reliably?

Does anyone know if any of these RTL 8168 builds support doing VLAN within ESX?

Folks,

I have modified the source build environment for the V8.018.00 version of the Realtek r8168 / r8111 driver to be ESX4.1 based.

I have successfully modified RTL V8.021.00 (Jan 27th 2011) version of the RTL sourcecode and included it as well.. This code will compile, but will NOT load under ESX4.1. Maybe someone can take a look and try to figure out what is causing it to bomb out.

LetnI

Hi brother!

I'm having a trouble when I try join the new driver r8168, published earlier, in a USB Stick.

I'm using:
- mkesxiaio_4.1.sh (script)
- VMware-VMvisor-Installer-4.1.0-260247.x86_64.iso
- inetd.conf
- ESX41_RTL8168-V8.018_oem.tgz

I put everything in the same folder, with full permission to execute, read and write and I execute ./mkesxiaio_4.1.sh

In the begin, everything works well, when:

bunzip2 imagedd.bz2 [Done]
Mounting imagedd to /dados/home/rfgomide/Desktop/vmware/esx-5./mkesxiaio_4.1.sh: line 1388: 512*: syntax error: operand expected (error token is "*")
Removing working folders (esx-*) [Done]

This script is the same that is published http://code.google.com/p/mkesxiaio/ and I follow all steps listed viewtopic.php?f=12&t=4.

There are 2 print screen attached.

If I try use the script mkesxiaio_4.1.sh without the add r8168, the USB stick works well, but without NIC SUPPORT.

I need so much of help! Please!
Thank you!

Hi!

I follow the instructions about make a Bootable USB Stick with VMware ESXi 4.1 and works well with my hardware. But, unfortunatelly, the NIC driver doesnt work!

My NIC adapter is r8168, but, when I try make the same procedure with this add file published, an error happened.

bunzip2 imagedd.bz2 [Done]
Mounting imagedd to /dados/home/rfgomide/Desktop/vmware/esx-5./mkesxiaio_4.1.sh: line 1388: 512*: syntax error: operand expected (error token is "*")
Removing working folders (esx-*) [Done]

When I make the same instructions without a ESX41_RTL8168-V8.018_oem.tgz, the process works well, but without NIC.

I follow the instruction of: viewtopic.php?f=16&t=4

And the script to generates USB Stick bootable is the same publised in: http://code.google.com/p/mkesxiaio/

If somebody may help, it will be very good!

Thank you!

Strange that it should work w/o the oem file.

You don't need to download the inetd.conf

What the script dose at that part is to mount the partition
where the oem file should be.

The problem is that fedora handles fdisk in another way.
I'm going to put up a new version but I haven't had the time.
you could download it here http://code.google.com/p/mkesxiaio/sour ... esxiaio.sh
It's not tested yet.

or

Open the script go to line 1388

change -ul to -u -l , save and testa again.

//Daniel

Hey Daniel!

Thank you for help!

I changed the lines from -lu to -l -u and works fine!

Tks!

Can I use this new r8168 driver with my r8169? After all, this is the thread for the r8169 - why are we discussing the r8168 here?

My ESXi box has Realtek 8110SC and I am using fruit r8169 driver. My ESXi is able to load the driver, however there is a problem that when copying file (especially big file over 500MB), it is very slow indeed. The speed just around 215KB/Sec. It is not even reach 100 mbps. Anyone have the same issues?