Had the same issue and had to swap out my e1000 virtual adapters for vmxnet3 on all my VMs last week. No word on an update yet, so workaround was the only way to go.
HAve the same problem of 5.5 crashing wenn tryning to push image.
So i tried to swap to vmxnet3 adapter.
Did it two ways (machine shut dwon and tehne booted up again):
Manually editing in the .vmx file e1000 to vmxnet3 and then i tried by removing e1000 adapters and adding vmxnet 3 adapters.
MAchien boots up but, static ips are assigned, as i can see using ipconfig but i cant ping out or get pinged.
Changing back to e1000 and everythings working agaien, escapt WDS of course..
Are there any chnges to be made to the vswitch or somethin else to be done to get the vmxnet3 adaptesrs to work (vm hardware version 7)?
Are you sure you assigned the proper named network when you added the vmxnet3 adapter? By default it grabs the first one (alphanumerically) in the list and if the VM operates on a specific network you need the one valid for the Guest and it's IP address. If it is a Windows guest, you might also want to go back and eliminate the "phantom" adapter from the OS; I used the method below to clean up those devices and their drivers that no longer exist:
Thanks for your replys.
Yes I took care for using the right network and checked at the vswitch.
Actually i have 2 vswitches connected to the virtual server.
I will try to remove the networkdapater first lke you suggested, but when I checked the nics in the deveice manager the used driver was vmxnet.
Is there any possibility to see in the logs if therer is something wrong?
Is there maybe an issue with the hardware version 7? Made an upgrade from ESXi 4.1 to 5.5 about 2 weeks ago and everything was working fine until i started to install a new machien by wds.
This bug is now finally fixed for ESXi 5.5 as well with today's release of 5.5 U1/esx-base patch to build 1623387:
Yay, updated to the HP 5.5 U1 image when it was finally back on the website and I those PSODS have stopped now thankfully, wish I saw the workaround, oh well, nevermind, I was close to going back to 5.1.
I'm back here and found this thread as I'm looking for another PSOD issue now, LINT1/NMI, but I'm glad there was a reason and fix in U1 for this, I hoped so, but nice to read and confirm it.
Yes, with HP 5.5U1 this issue seems to be fixed.
Tried this on HP MicroServer Gen8 / ML110 G7 (unsupported) / ML310e Gen8 / DL380 G7 / ML350p Gen8.
All work fine, even the WDS-Issue is fixed
For all who have not applied the Upgrade yet, here a short how-to for ESXi (free):
1. download it from the VMWare Site https://my.vmware.com/web/vmware/details?downloadGroup=HP-ESXI-5.5.0U1-GA&productId=353
2. place the ZIP (not the ISO) file into a datastore of your host
3. shut-down all VMs
4. place your Host into Maintenance Mode
5. SSH to your Host (SSH needs to be enabled...)
6. Fire "esxcli software profile update -d /vmfs/volumes/[your datastore]/[your folder]/VMware-ESXi-5.5.0-Update1-1623387-HP-5.73.17-Mar2014-depot.zip -p HP-ESXi-5.5.0-Update1-5.73.17" in your SSH Session
7. Wait between 1 and 5 minutes until you see the bunch of removed/replaced VIBs etc.
8. end Maintenance Mode
Even the Bug with "lost" iSCSI Paths was fixed. Prior updates forgot an iSCSI Path and it was required to re-configure the correct iSCSI Path.