VMware Cloud Community
LogitComputer
Enthusiast
Enthusiast

Reproducable PSOD on 5.1U1 and 5.5 with Windows 8.1 and Server 2012 R2 and E1000E NIC

Hello everybody,

I figured the last two weeks a strange, reproducable issue with following constellation:

Hardware (tested with both Servers)

HP ProLiant ML110G7, SmartArray P410, 1GB FBWC, RAID5, 32GB HP ECC RAM

HP ProLiant ML310e Gen8, SmartArray P222, 512MB FBWC, RAID1, 16GB HP ECC SmartMemory RAM

Hypervisor (tested vice-versa on both Servers)

ESXi 5.1U1 HP Custom Image VMware-ESXi-5.1.0-Update1-1065491-HP-5.50.26.iso

ESXi 5.5 HP Custom Image VMware-ESXi-5.5.0-1331820-HP-5.70.38-Sep2013.iso

When I install a Windows 8.1 or Server 2012 R2 (NOT Windows 8.0 or Server 2012 w/o R2) with the suggested NIC E1000E, and I have a little bit "heavy" Network-Traffic from/to Windows 2012 or Windows 2012R2 Servers, an PSOD occurs with "pf exception 14 in world 107417".

Unfortunally, I didn't made a dump or Print-Screen of the issue, but I can write you what I've done (or make a little bit of load and then wait until it crashes again...)

Example 1

Network-Installation of "Windows 8.1 Pro" or "Windows Server 2012 R2" from an Windows Deployment Service wich resides on Server 2012.

WDS Server is VM on same ESXi Host like the new VM. WDS boots, made Domain-Login for selecting the Images, started Copying --> PSOD.

Reproducable only with 8.1 or 2012 R2 with E1000E NIC

Example 2

Network-Installation of "Windows 8.1 Pro" or "Windows Server 2012 R2" from an Windows Deployment Service, resides on Server 2012.

WDS Server is VM on different ESXi Host like the new VM. WDS boots, made Domain-Login for the Images, Started Copying --> ALL OK.

Then installed on Host 2 (2 x Server 2012 R2 and 1 x Windows 8.1 Pro) everything for a Domain (AD, DNS, WDS, WSUS) and when I first want to download the Windows-Update from the new Windows 8.1 Machine --> PSOD again.

Example 3

Network-Installation of "Windows 8.1 Pro" or "Windows Server 2012 R2" from an Windows Deployment Service, resides on Server 2012 (VM).

WDS Server is VM on ESXi Host, WDS Installation on Physical PC, not VM.

WDS boots, made Domain-Login for the Images, Started Copying --> ALL OK, no PSD at all.

After discussing this issue with a collegue he said that he has similar Problems with bigger DL380 and Server 2012 R2 (wich were unavaiable a couple of pings) and he told me that he loaded VMXNET3 Driver.

I've done this too and until now, no new PSOD was here.

But the silly thing is that VMXNET3 is unable to install via WDS, so therefore I have to install my Test-Machines the "old" way with mounting ISOs.

My question to you - had anybody else this issue or am I maybe the only one?

TIA - Josip.

0 Kudos
22 Replies
MKguy
Virtuoso
Virtuoso

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:

https://www.vmware.com/support/vsphere5/doc/vsphere-esxi-55u1-release-notes.html

VMware KB: VMware ESXi 5.5, Patch ESXi550-201403201-UG: Updates ESXi 5.5 esx-base vib 

-- http://alpacapowered.wordpress.com
0 Kudos
AJStevens
Contributor
Contributor

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.

0 Kudos
LogitComputer
Enthusiast
Enthusiast

Hello All,

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 Smiley Happy

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

9. Reboot

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.

Regards,

Josip.

0 Kudos