VMware Cloud Community
MobileWill
Contributor
Contributor

ESXi 4.1U1 w/ Intel Pro 1000 MT dual port

I have been runing vmware esxi 4.0 for almost 2 years now and decided I need some more NIC's so I can run a firewall.

I bought a Intel Pro 1000MT Dual port (82546) as it looked like it works and it was cheap. It looks like the chipset model is different than the others people had working. Either way I had it working last night I think when I uploaded a pci.ids and simple.map file I downloaded. Well esxi saw the card and showed it and could add it to a vswtich.  Today I tried to move a vm to it and start it and then I got PSOD.  Now for the life of me I can't get it to show again. I even updated to 4.1U1 and nothing. I thought it was a corrupt e1000.o file but it looks like the update updated the file.

This is driving me nuts as I thought it was a supported card. I have been at this for 2 evenings now.

Any ideas? I have searched and searched and searched and nothing has worked. The log file has more info than 4.0.

This is runing on a ECS gf7100/7050PVT-M3 Everything worked when I installed it two years ago except for sata which I had to edit some file to enable sata_nv. For the life of me I can't remember how I did it so I can't install esxi clean.

lspci -p

000:001:04.0 8086:1079 8086:117a  7/  7/0x88 A V              vmnic3
000:001:04.1 8086:1079 8086:117a 10/ 10/0x88 B V              vmnic4
lspci
000:001:04.0 Network controller: Intel Corporation PRO/1000 MT Dual Port Server Adapter [vmnic3]
000:001:04.1 Network controller: Intel Corporation PRO/1000 MT Dual Port Server Adapter [vmnic4]
From message log file:
Jul 20 04:59:00 vmkernel: 0:00:00:21.266 cpu1:4593)Loading module e1000 ...
Jul 20 04:59:00 vmkernel: 0:00:00:21.267 cpu1:4593)Elf: 2187: <e1000> provides name-space <esx:nover>
Jul 20 04:59:00 vmkernel: 0:00:00:21.268 cpu1:4593)Elf: 1612: <e1000> : R_X86_64_32 relocation(s) ignored
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)module heap : Initial heap size : 102400, max heap size: 5750784
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)module heap vmklnx_e1000: creation succeeded. id = 0x4100b4400000
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)module skb heap : Initial heap size : 524288, max heap size: 23068672
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)module skb heap : creation succeeded
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)<6>Intel(R) PRO/1000 Network Driver - version 8.0.3.2-1vmw-NAPI
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)<6>Copyright (c) 1999-2008 Intel Corporation.
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: driver e1000 is looking for devices
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Trying 0000:00:03.1
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Announcing 0000:00:03.1
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Trying 0000:00:04.0
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Trying 0000:00:04.1
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Trying 0000:00:08.0
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Announcing 0000:00:08.0
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Trying 0000:00:09.0
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Announcing 0000:00:09.0
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Trying 0000:00:0e.0
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Announcing 0000:00:0e.0
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Trying 0000:00:0f.0
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Trying 0000:00:10.0
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Announcing 0000:00:10.0
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Trying 0000:01:04.0
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Announcing 0000:01:04.0
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)WARNING: vmklinux26: __request_region: This message has repeated 1 times: Region conflict @ 0xbe0000 => 0xffbfffff
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)WARNING: vmklinux26: __request_region: This message has repeated 2 times: Region conflict @ 0xb80000 => 0xffbbffff
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)socket buffer cache creation succeeded for vmnic%d
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)WARNING: Buddy: 3550: xmap: size(1044513) is not supported
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Trying 0000:01:04.1
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: Announcing 0000:01:04.1
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)WARNING: vmklinux26: __request_region: This message has repeated 3 times: Region conflict @ 0xbc0000 => 0xffbdffff
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)WARNING: vmklinux26: __request_region: This message has repeated 4 times: Region conflict @ 0xb00000 => 0xffb3ffff
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)socket buffer cache creation succeeded for vmnic%d
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)WARNING: Buddy: 3550: xmap: size(1044513) is not supported
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)PCI: driver e1000 claimed 0 device
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)Mod: 4163: Initialization of e1000 succeeded with module ID 32.
Jul 20 04:59:00 vmkernel: 0:00:00:21.269 cpu1:4593)e1000 loaded successfully.

Thanks for any help. I hate to have to buy more hardware but I am thinking about it.

Reply
0 Kudos
5 Replies
MobileWill
Contributor
Contributor

Okay this is weird.

I shutdown and booted xenserver to see if it see's the hard driver natively, which it does and the I deceided to check the bios settings. I had read about C1E needing to be disabled. So I disabled that and reduced the video memory and enabled smart fan.

Rebooted back into Esxi and what do you know I can see the intel nic again. I don't know if the C1E had to do with it.

Here is the log file now

Jul 20 06:53:08 vmkernel: 0:00:00:21.262 cpu1:4593)Loading module e1000 ...
Jul 20 06:53:08 vmkernel: 0:00:00:21.263 cpu1:4593)Elf: 2187: <e1000> provides name-space <esx:nover>
Jul 20 06:53:08 vmkernel: 0:00:00:21.264 cpu1:4593)Elf: 1612: <e1000> : R_X86_64_32 relocation(s) ignored
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)module heap : Initial heap size : 102400, max heap size: 5750784
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)module heap vmklnx_e1000: creation succeeded. id = 0x4100b4400000
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)module skb heap : Initial heap size : 524288, max heap size: 23068672
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)module skb heap : creation succeeded
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)<6>Intel(R) PRO/1000 Network Driver - version 8.0.3.2-1vmw-NAPI
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)<6>Copyright (c) 1999-2008 Intel Corporation.
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: driver e1000 is looking for devices
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:03.1
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Announcing 0000:00:03.1
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:04.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:04.1
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:08.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Announcing 0000:00:08.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:09.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Announcing 0000:00:09.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:0e.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Announcing 0000:00:0e.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:0f.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:10.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Announcing 0000:00:10.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:01:04.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Announcing 0000:01:04.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)socket buffer cache creation succeeded for vmnic%d
Jul 20 06:53:08 vmkernel: <6>e1000: 0000:01:04.0: e1000_probe: (PCI:33MHz:32-bit)  00: 04:23:a8:e3:e8
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)<6>e1000: vmnic1: e1000_probe: Intel(R) PRO/1000 Network Connection
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)PCI: driver e1000 claimed device 0000:01:04.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)PCI: Registering network device 0000:01:04.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)VMK_PCI: 646: Device 000:001:04.0 name: vmnic3
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)Uplink: 11078: Device vmnic3 not yet opened
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)LinPCI: LinuxPCI_DeviceClaimed: Device 1:20 claimed.
Jul 20 06:53:08 vmkernel:
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)PCI: Trying 0000:01:04.1
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)PCI: Announcing 0000:01:04.1
Jul 20 06:53:08 vmkernel: <6>e1000: 0000:01:04.1: e1000_probe: (PCI:33MHz:32-bit)  00: 04:23:a8:e3:e9
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)<6>e1000: vmnic1: e1000_probe: Intel(R) PRO/1000 Network Connection
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)PCI: driver e1000 claimed device 0000:01:04.1
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)PCI: Registering network device 0000:01:04.1
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)VMK_PCI: 646: Device 000:001:04.1 name: vmnic4
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)Uplink: 11078: Device vmnic4 not yet opened
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)LinPCI: LinuxPCI_DeviceClaimed: Device 1:21 claimed.
Jul 20 06:53:08 vmkernel:
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)PCI: driver e1000 claimed 2 devices
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)Uplink: 13003: Opening device vmnic3
Jul 20 06:53:08 vmkernel: 0:00:00:21.963 cpu1:4123)IDT: 1036: 0x88 <vmnic3> sharable (entropy source), flags 0x10
Jul 20 06:53:08 vmkernel: 0:00:00:21.963 cpu1:4123)VMK_VECTOR: 143: Added handler for shared vector 136, flags 0x10
Jul 20 06:53:08 vmkernel: 0:00:00:21.963 cpu1:4123)IDT: 1133: 0x88 for vmkernel
Jul 20 06:53:08 vmkernel: 0:00:00:21.963 cpu1:4123)VMK_VECTOR: 231: vector 136 enabled
Jul 20 06:53:08 vmkernel: 0:00:00:21.964 cpu0:4593)NetPort: 982: enabled port 0x3 with mac 00:00:00:00:00:00
Jul 20 06:53:08 vmkernel: 0:00:00:21.964 cpu0:4593)Uplink: 13145: vmnic3 is opened
Jul 20 06:53:08 vmkernel: 0:00:00:21.964 cpu0:4593)Uplink: 13003: Opening device vmnic4
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4123)IDT: 1036: 0x88 <vmnic4> sharable (entropy source), flags 0x10
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4123)VMK_VECTOR: 143: Added handler for shared vector 136, flags 0x10
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4123)IDT: 1133: 0x88 for vmkernel
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4123)VMK_VECTOR: 231: vector 136 enabled
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu1:4593)NetPort: 982: enabled port 0x4 with mac 00:00:00:00:00:00
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4593)Uplink: 13145: vmnic4 is opened
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4593)Mod: 4163: Initialization of e1000 succeeded with module ID 32.
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4593)e1000 loaded successfully.

So odd. I am trying a vm on it now (vCMA) to see if it can boot and not PSOD.

.

.

.

.

So far the vm is running.

I don't understand.

The NIC does show up as VmNIC 3/4 instead of VmNIC 1/2

Any ideas? Think it will be reliable? Using the stock settings from 4.1.U1.

Anyone know where the sata_nv enable might have been? I think I uncommented something. I had to do with during the install and on the installed drive.

Reply
0 Kudos
MobileWill
Contributor
Contributor

On second thought it PSOD again. I rebooted the VM since I didn't have the cable plugged in the first time. It worked for awhile even was able to connecto the vm remotely.

Back to the drawing board.

Edit:

I rebooted and it still shows there. It will probably PSOD again.

Reply
0 Kudos
MobileWill
Contributor
Contributor

One thing I noticed is that after I reboot VmNic3 is not assigned to a nswitch anymore. VmNIC3 is not connected right now. Going to try a different vm on that nic now.

Reply
0 Kudos
MobileWill
Contributor
Contributor

After trying different VM's and PSODing 3 times it disappered again.

Reply
0 Kudos
MobileWill
Contributor
Contributor

So in the mean time I bought a cheap broadcom 5721 pci-e. Hopefully that will work. I still would like to get the intel pro working.

Anyone have problems with MT? or anyone have it working?

I am almost thinking that the chipset might have something to do with after some more reading. I have nforce 7100/630i.

Reply
0 Kudos