Hello there,
I've recently received what I hope would be my new lab rig, this SuperMicro 1U Twin Server : http://www.supermicro.nl/products/system/1U/5016/SYS-5016TI-TF.cfm
It's not on the HCL, but it's still server grade material :
- Xeon X3440
- ECC RAM
- Dual Intel 82574L nic onboard
Most if not all of these components are on the HCL, and truth is, ESXi installs without complaining and works out of the box.
Problem is, when using the NICs (for example, I'm using an iSCSI SAN), the NIC "crash", but the ESXi keeps running.
I've attached an extract of the vmkernel during the following sequence :
- Boot a VM
- Start a Debian installation inside the VM
At some point during the installation of Debian the nic used for iSCSI traffic just crash, and the following lines can be seen in the log :
2012-02-27T20:15:31.595Z cpu2:2050)WARNING: NetSched: 1713: Scheduler [0x4100045c5b80] lock up [stopped=0] for vmnic3:2012-02-27T20:15:31.595Z cpu2:2050)WARNING: NetSched: 1723: detected at 866999 while last xmit at 861775 and 2/37092 packets/bytes in flight [window full 1] and binary heap size 1 [stress 0]2012-02-27T20:15:31.595Z cpu2:2050)WARNING: NetSched: 1732: Packets completion seem stuck, issuing reset on vmnic3 [stress 0]
The following lines are iSCSI software initiator complaining about not being able to write to the LUN.
I've also done the same test with the other onboard nic and no iSCSI traffic (ie with VM Network traffic), to the same result.
Any ideas on how to fix the problem ?
I have another dual port card in the server I intend to use in the meantime, but loosing 2 onboard nics that are on the HCL makes me sick ...
Sylvain.