Problem
Some releases of VMware contain a faulty e1000 vNIC emulation
which can cause OSR600V or UW714+ VMs to hang or lockup when
the network is used. Both OSR600V and UW714+ use the e1000 vNIC
emulation by default. Cause
VMware released the faulty e1000 vNIC emulation when trying to address another issue with the e1000.
This problem was introduced in the following versions of ESXi: ESXi 5.1 Update 3 (Build 2323236) ESXi 5.5 Update 2 + patch ESXi550-201410001 (Build 2143827) ESXi 6.0 initial release
Solution
To correct this issue apply the latest VMware Update for your version of ESXi.
These updates are known to contain the fixed e1000 vNIC emulation: ESXi 5.1 patch ESXi510-201503001 (Build 2583090) (March 2015) ESXi 5.5 patch ESXi550-201505002 (Build 2718055) (May 2015) ESXi 6.0 patch ESXi600-201608001 (Build 4192238) (August 2016)
It is expected that future ESXi updates will also contain the fixed e1000 vNIC emulation.
Alternatively, if you are unable to apply the latest update from VMware, you can use one of the following workarounds to the problem.
A) The easiest workaround is to change the e1000 vNIC in the VM configuration a 'flexible' vNIC.
To change your vNIC to the 'flexible' vNIC, take these steps using your vSphere Client:
1) Shutdown the VM and make a clone/backup if you haven't already.
2) Edit Settings for the VM and highlight the e1000 vNIC Network Adapter and take note of which network it is connected to and remove it.
Then click ADD, choose Ethernet Adapter and set Adapter Type to 'flexible' and connect it to the same network that the old vNIC was using.
3) Open the console for the VM and power it on, boot into
single user mode. Run `netconfig` on OSR6V, or 'netcfg' on UW714+.Highlight SCO TCP-IP under the Intel Ethernet PCI NIC and choose Protocol->View Protocol Configuration
Take note of the current TCP-IP configuration information and
choose OK. You will need this information when configuring the
new vNIC.Highlight the Intel Ethernet PCI NIC.Then choose hardware-> Remove network device.Then choose hardware-> Add new Lan AdapterNetconfig should autodetect the AMD PC-NET NIC, configure it with the IP information that was used previously.
When exiting netconfig, you'll be prompted to relink, choose 'y' to boot by default and 'y' to rebuild the environment.
4) Shutdown and reboot again. The virtual machine should now be using
the flexible vNIC.NOTE: It is advised to swap back to the e1000 vNIC after applying the
VMware updates, as it has better performance than the 'flexible' vNIC.B) Another workaround to this problem is to use an older version of
the Intel e1008g driver which did not include the feature which
triggers this e1000 vNIC hang problem. The e1008g driver in the
nd.806c package can be used.https://ftp.scoexpert.com/openserver6/600/drivers/nd.806c/
https://ftp.scoexpert.com/unixware7/714/drivers/nd_806c/This workaround is harder because you usually need a working network to download and update the NIC driver. You may need to use the first workaround, just to implement this one.