Another thing that might be wrong – I am trying your binaries on ESXI 4.0 Update 1 – maybe some kernel incompatibility? I just had the server machine freeze on me when trying to download the vSphere over web interface. I’m pondering whether it is cheaper to just buy a NIC.

Awesome! Million thanks.

Just an update. I had to give up on ESXi 4 and trying to compile the tulip.o modules.

Ultimately switched to using VMware Server 2.0.2 on CentOS 5.4 x64. Everything configured fine since CentOS includes the tulip.o modules.

Ran VMware Server 2.0.2 for the past month and I’d have to give it a 6/10. The web interface continually dies every time I try to update, create new VM’s and I must constantly restart the web host. VMware opted for a web-based GUI to manage VM’s and I’d have to agree with a lot of the blogs out there, quite frankly, it sucks and renders the product semi-usable. Also, sometimes my VM’s will just blink off after a few days with no rhyme or reason. This is a development box, but some stability would be nice.

I’m now switching to using Win2K3 Server x64 Standard with VMware Server 2.0.2. I’ll report back after this experience.

Again, thanx for your input.

Best…

grittykitty@kissthesquirrel.com

dev_addr[0] = 0x08;
dev_addr[1] = 0x00;
dev_addr[2] = 0x20;
get_random_bytes(&dev_addr[3], 3);
return;

to something like;

dev_addr[0] = 0x08;
dev_addr[1] = 0x00;
dev_addr[2] = 0x20;
if (is_quattro_p(pdev)) {
   dev_addr[3] = 0x00;
   dev_addr[4] = 0x00;
   dev_addr[5] = (char) PCI_SLOT(pdev->devfn);
} else {
   get_random_bytes(&dev_addr[3], 3);
}
return;

Still not the greatest solution, but at least you know what the MAC addresses will be.

[root@node02 ~]# cat /etc/rc.local
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don’t
# want to do the full Sys V style init stuff.

vmkload_mod sunhme
touch /var/lock/subsys/local

[root@node02 ~]#

Best regards.

Unfortunately, although I’ve added right PCI IDs, it doesn’t find any interface (driver hme claimed 0 device)

This is the output of /var/log/vmkernel

————————————–

May 2 11:18:15 node02 vmkernel: 0:00:21:38.301 cpu2:4106)sunhme loaded successfully.
May 2 11:18:15 node02 vmkernel: 0:00:21:38.301 cpu2:4106)ALERT: Elf: 2518: Kernel module sunhme was loaded, but has no signature attached
May 2 11:20:59 node02 vmkernel: 0:00:24:22.747 cpu2:4106)Loading module sunhme …
May 2 11:20:59 node02 vmkernel: 0:00:24:22.748 cpu2:4106)Elf: 2320: <sunhme> symbols tagged as <GPL>
May 2 11:20:59 node02 vmkernel: 0:00:24:22.758 cpu1:4106)module heap : Initial heap size : 102400, max heap size: 4194304
May 2 11:20:59 node02 vmkernel: 0:00:24:22.758 cpu1:4106)module heap sunhme: creation succeeded. id = 0×4100bbc00000
May 2 11:20:59 node02 vmkernel: 0:00:24:22.758 cpu1:4106)module skb heap : Initial heap size : 524288, max heap size: 23068672
May 2 11:20:59 node02 vmkernel: 0:00:24:22.759 cpu1:4106)module skb heap : creation succeeded
May 2 11:20:59 node02 vmkernel: 0:00:24:22.759 cpu1:4106)PCI: driver hme is looking for devices
May 2 11:20:59 node02 vmkernel: 0:00:24:22.759 cpu1:4106)PCI: Trying 0000:00:02.0
May 2 11:20:59 node02 vmkernel: 0:00:24:22.759 cpu1:4106)PCI: Trying 0000:00:02.1
May 2 11:20:59 node02 vmkernel: 0:00:24:22.759 cpu1:4106)PCI: Trying 0000:00:04.0
May 2 11:20:59 node02 vmkernel: 0:00:24:22.759 cpu1:4106)PCI: Trying 0000:00:04.1
May 2 11:20:59 node02 vmkernel: 0:00:24:22.759 cpu1:4106)PCI: Trying 0000:00:06.0
May 2 11:20:59 node02 vmkernel: 0:00:24:22.759 cpu1:4106)PCI: Trying 0000:00:0a.0
May 2 11:20:59 node02 vmkernel: 0:00:24:22.759 cpu1:4106)PCI: driver hme claimed 0 device
May 2 11:20:59 node02 vmkernel: 0:00:24:22.759 cpu1:4106)Mod: 2986: Initialization for sunhme succeeded with module ID 57.
May 2 11:20:59 node02 vmkernel: 0:00:24:22.759 cpu1:4106)sunhme loaded successfully.

————————————–

After some retries, I decided to create a new file called /etc/vmware/pciid/hme.xml that contains the new PCI addresses :

<?xml version=’1.0′ encoding=’iso-8859-1′?>
<pcitable>
<vendor id=”108e”>
<short>Sun</short>
<name>Sun Microsystems Computer Corp.</name>
<device id=”1001″>
<vmware label=”nic”>
<driver>sunhme</driver>
</vmware>
<name>Sun Happy Meal</name>
<table file=”pcitable” module=”ignore” />
<table file=”pcitable.Linux” module=”sunhme”>
<desc>Sun Microsystems Computer Corp.|Sun Happy Meal</desc>
</table>
</device>
<device id=”1000″>
<vmware label=”nic”>
<driver>sunhme</driver>
</vmware>
<name>Sun Happy Meal</name>
<table file=”pcitable” module=”ignore” />
<table file=”pcitable.Linux” module=”sunhme”>
<desc>Sun Microsystems Computer Corp.|Sun Happy Meal</desc>
</table>
</device>
</vendor>
</pcitable>

Then I recalled the executable esxcfg-pciid that recreated correct simple.map (I’m under ESX 4 and I didn’t create an oem.tgz).

Now it works correctly, it sees all the NICs and they have been added to vSwitch to simulate NIC TEAMING. So, the driver works !!!

The only problem I have is that on reboot I must manually run the command “vmkload_mod sunhme” to load the module. Is there a way to make this automatically ?

Best regards.