JaapL
Contributor
Contributor

Intel dual ET adapter installed - VM shows Intel Pro/MT adapter ???

Jump to solution

Hi all,

I have installed an Intel ET dual adapter in my ESXi v4.0 host.

Loaded the driver via "vihostupdate offline-bundle" >ok.

INT-intel-lad-ddk-igb-1.3.19.12.1-offline_bundle-185976.zip

The problem is that when I use this adapter in a VM it shows up as a Intel pro/MT adapter instead as a Intel ET dual adapter.

In my opinion this means that the NIC will not work properly.

The advanced properties do not show the options of the Intel ET nic has.

My question is:

- How can I find and 'bind' the right driver to this NIC?

Thanks Jaap

PS

I had it correctly configured on this system before.

To test my installation doc I started over. Smiley Sad

0 Kudos
1 Solution

Accepted Solutions
AWo
Immortal
Immortal

You'll never see the physical network adapter in the guest as this is virtualized hardware. Either you see the VMware adapter or an em,ulated Intel E1000.

When you see it as an Intel adapter in the guest the vNIC is set to the Intel E1000 type. You also can choose to use different "vmxnet" types.

However, the drivers you need come with the VMWare Tools you should install in every guest. While the "e1000" vNIC type can be used with the drivers delivered with the guest OS you need the VMWare Tools if you use the "vmxnet" vNIC types.


AWo

VCP 3 & 4

Author @ vmwire.net

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

View solution in original post

0 Kudos
9 Replies
Kasraeian
Expert
Expert

I used these steps in my home lab, and I think there's must be some simple way for HCL complaint Devices/Server.

first find the information about your NIC with this command

(if i remember the parameter of lspci right, its something like this)

lspci -v

or

lspci -n

then use these two command

vi /etc/vmware/pci.ids | grep ????

vi /etc/vmware/simple.map | grep ????

simple.map is contain all driver and their peer info, like below

8086:10a7 0000:0000 network igb.o

so replace the ???? with the info of your NIC. (here 8086 and 10a7)

these are hardware vendor info.

by working on simple.map you can change the driver you want to use(it must be supported or build using VMware development pack - SDK)

by working on pci.ids the information shown in vSphere Client (Intel ET/MT/ ... Model and ...) would be customized.

IMPORTANT: doing any of these without telling the support team and getting their permission or idea, may be affect/cancel your support.

-= If you found this note/reply useful, please consider awarding points for "Correct" or "Helpful" =-

-= If there's any mistake in my notes, please correct me! =-

-= Thanks =-

MCTS, VCP

If you found this note/reply useful, please consider awarding points for "Correct" or "Helpful" If there's any mistake in my notes, please correct me! Sohrab Kasraeianfard | http://www.kasraeian.com | @Kasraeian
JaapL
Contributor
Contributor

Hi Sohrab.

Thanks for your reply and info.

The Intel ET is on the HCL.

The thing is that I 've done the install once before with vihostupdate.pl with the driversoftware supplied bij VMWare.

  1. vihostupdate.pl --server 10.16.0.250 -i -b c:\tmp\INT-intel-lad-ddk-igb-1.3.19.12.1-offline_bundle-185976.zip

The result being that the NIC was properly described in the 'Networks Adapters' tab

There are two versions, but I can only download 1.3.19.12.1 from

http://www.vmware.com/resources/compatibility/search.php?action=search&deviceCategory=io&productId=1...8086&did=10c9&svid=&ssid=&rorre=0

Mode/Release details:

igb version 1.3.19.12.1 (async ???) > Dell

igb version 1.2.44.3 (inbox ???) > Intel

I 've reinstalled update v4.0.1 without the ET nic in it. Then updated it with the offline-bundle > still Intel pro/MT

Then I 've changed the oem.tgz as mentioned at vm-help.com. In the VM > still Intel Pro/MT

I 've reinstalled update v4.0.0 with the ET nic in it

It looks like the igb.o driver doesn't support the Inte ET Dual Server Adapter !?!?!?!

But then again I had a good result using this driver the first time !!!!

Pffffffff Smiley Sad

Jaap

0 Kudos
Kasraeian
Expert
Expert

have you got screenshot or output from your driver installation or can you make it?

did you check if after installing the driver, the simple.map and pci.ids is changed and the NIC using the new one?

what kind of changes did you make in your oem.tgz?

did you point the HW-Vendor code (????:????) to the proper driver (igb.o or ...?)

-= If you found this note/reply useful, please consider awarding points for "Correct" or "Helpful" =-

-= If there's any mistake in my notes, please correct me! =-

-= Thanks =-

MCTS, VCP

If you found this note/reply useful, please consider awarding points for "Correct" or "Helpful" If there's any mistake in my notes, please correct me! Sohrab Kasraeianfard | http://www.kasraeian.com | @Kasraeian
JaapL
Contributor
Contributor

Hi,

Italic is info after the update. Hope this helps.

The differences are the pci,ids file and igb.o file

8086 Intel Corporation

0007 82379AB

...

10c9 82576 Gigabit Network Connection

10cb 82567V Gigabit Network Connection

8086 Intel Corporation

+ 0007 82379AB 10c9 82576 Gigabit Network Connection+

+ ...+

+ 10c9 82576 Gigabit Network Connection+

+ 10cb 82567V Gigabit Network Connection+

simple.map extract:

8086:10c9 0000:0000 network igb.o

8086:10c9 0000:0000 network igb.o

lspci - p extract:

03:00.00 8086:10c9 8086:a03c 10/ 10/0x59 A V igb vmnic0

03:00.01 8086:10c9 8086:a03c 5/ 5/0x81 B V igb vmnic1

06:00.00 197b:2380 1462:522d 5/ 5/0x81 A V

07:00.00 8086:107c 8086:1376 10/ 10/0x59 A V e1000 vmnic2

07:01.00 8086:107c 8086:1376 5/ 5/0x81 A V e1000 vmnic3

03:00.00 8086:10c9 8086:a03c 10/ 10/0x59 A V igb vmnic0

03:00.01 8086:10c9 8086:a03c 5/ 5/0x81 B V igb vmnic1

06:00.00 197b:2380 1462:522d 5/ 5/0x81 A V

07:00.00 8086:107c 8086:1376 10/ 10/0x59 A V e1000 vmnic2

07:01.00 8086:107c 8086:1376 5/ 5/0x81 A V e1000 vmnic3

esxcfg-nics -l:

Name PCI Driver Link Speed Duplex MAC Address MTU Description

vmnic0 03:00.00 igb Down 0Mbps Half 00:1b:21:4d:e7:74 1500 Intel Corporation 82576 Gigabit Network Connection

vmnic1 03:00.01 igb Down 0Mbps Half 00:1b:21:4d:e7:75 1500 Intel Corporation 82576 Gigabit Network Connection

vmnic2 07:00.00 e1000 Up 1000Mbps Full 00:1b:21:23:c6:91 1500 Intel Corporation PRO/1000 GT Desktop Adapter

vmnic3 07:01.00 e1000 Up 1000Mbps Full 00:1b:21:27:4d:a9 1500 Intel Corporation PRO/1000 GT Desktop Adapter

Name PCI Driver Link Speed Duplex MAC Address MTU Description

vmnic0 03:00.00 igb Down 0Mbps Half 00:1b:21:4d:e7:74 1500 Intel Corporation 82576 Gigabit Network Connection

vmnic1 03:00.01 igb Down 0Mbps Half 00:1b:21:4d:e7:75 1500 Intel Corporation 82576 Gigabit Network Connection

vmnic2 07:00.00 e1000 Up 1000Mbps Full 00:1b:21:23:c6:91 1500 Intel Corporation PRO/1000 GT Desktop Adapter

vmnic3 07:01.00 e1000 Up 1000Mbps Full 00:1b:21:27:4d:a9 1500 Intel Corporation PRO/1000 GT Desktop Adapter

ls -al /etc/vmware extract

-rw------- 1 root root 529460 Nov 8 08:50 pci.ids

-rw------- 1 root root 23730 Nov 8 08:50 simple.map

-rw------- 1 root root 529617 Feb 7 10:21 pci.ids

-rw------- 1 root root 23730 Nov 8 08:50 simple.map

ls -al /usr/lib/vmware/vmkmod extract

-rw-rr 1 root root 200716 Nov 8 08:56 igb.o

-rw-rr 1 root root 170752 Aug 17 20:20 igb.o

Update Intel ET nic:

esxupdate update --bundle=/tmp/INT-intel-lad-ddk-igb-1.3.19.12.1-offline_bundle-185976.zip

Removing packages :vmware-esx.. ########################################

Installing packages :cross_vm.. ########################################

Running ...

ok.

The update completed successfully, but the system needs to be rebooted for the

changes to be effective.

0 Kudos
AWo
Immortal
Immortal

You'll never see the physical network adapter in the guest as this is virtualized hardware. Either you see the VMware adapter or an em,ulated Intel E1000.

When you see it as an Intel adapter in the guest the vNIC is set to the Intel E1000 type. You also can choose to use different "vmxnet" types.

However, the drivers you need come with the VMWare Tools you should install in every guest. While the "e1000" vNIC type can be used with the drivers delivered with the guest OS you need the VMWare Tools if you use the "vmxnet" vNIC types.


AWo

VCP 3 & 4

Author @ vmwire.net

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

View solution in original post

0 Kudos
JaapL
Contributor
Contributor

Hi

I 've done some more digging.

It 's what AWo says.

I hope that VMWare can use the advanced features 'behind the screens'.

Thank you both,

Jaap

0 Kudos
AWo
Immortal
Immortal

I hope that VMWare can use the advanced features 'behind the screens'.

What are you looking for?


AWo

VCP 3 & 4

Author @ vmwire.net

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
JaapL
Contributor
Contributor

Hi AWo,

Well I was just looking for an up-to-date NIC (virtualization features such as Next-generation VMDq) with the capabilty to improve network throuhput and lessen the strain on the CPU.

And on the VMware HCL.

Greetz Jaap

0 Kudos
AWo
Immortal
Immortal

Check this document for some information on what the virtual network drivers provide:

http://www.vmware.com/files/pdf/vsphere-whatsnew-networking-wp.pdf


AWo

VCP 3 & 4

Author @ vmwire.net

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos