VMware Cloud Community
bmekler
Contributor
Contributor

Patching question

I had a host PSOD this morning, with a message '#PF Exception 14 in world 11290:vmm1:VMname". Looking it up led me to KB article 2048655 which advises updating system BIOS or installing patch 2051208. The host is a Dell PowerEdge R410 running the latest BIOS (1.12.0), so updating the BIOS is not an option. Looking at VMware patch downloads, "VMware ESXi 5.1, Patch ESXi510-201305401-BG: Updates esx-base (2051208)" corresponds to build number 1117900; however, I'm currently running build number 1483097 (update02). Are these updates cumulative, meaning that 1483097 already has the fixes in 1117900 and the PSOD I had was caused by something else, or can I apply the 2051208 patch to my host anyway? Or maybe I should go ahead and apply the latest available image (2191751, dated 10/30/2014)? For the reference, I don't have update manager installed.

Tags (2)
0 Kudos
7 Replies
JarryG
Expert
Expert

Patches are cumulative, so it is enough (and safe) to install just the latest one (for esxi it is ESXi510-201410001)...

_____________________________________________ If you found my answer useful please do *not* mark it as "correct" or "helpful". It is hard to pretend being noob with all those points! 😉
0 Kudos
Alistar
Expert
Expert

If you could post a screencap of the PSOD we can take a look at it and see what could have gone wrong, but I hope the ESXi upgrade will fix it Smiley Happy

Stop by my blog if you'd like 🙂 I dabble in vSphere troubleshooting, PowerCLI scripting and NetApp storage - and I share my journeys at http://vmxp.wordpress.com/
0 Kudos
bmekler
Contributor
Contributor

Here is a screenshot of the PSOD. I guess I'll schedule a maintenance window for this weekend to update the hosts to latest image, or maybe go directly to 5.5.

0 Kudos
a_p_
Leadership
Leadership

FYI, KB article VMware KB: VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing an... explains this issue, and - in addition to a workaraound - also lists the patches which are supposed to contain the fix.

André

0 Kudos
bmekler
Contributor
Contributor

Yes, I know about that one, but I'm already on update 2 which is supposed to fix it - in fact, I ran into that specific issue a while back, which is what prompted me to deploy update 2 in the first place.

0 Kudos
peetz
Leadership
Leadership

Probably this other KB article applies to your case:

http://kb.vmware.com/kb/2079094

And it mentions ESXi 5.1 Patch 5 which is newer than Update 2. So, just install the latest ESXi 5.1 patch and hopefully this will fix your issue.

Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
0 Kudos
vNEX
Expert
Expert

Hello,

to resolve this issue you have to apply ESXi 5.1 Express Patch 5:

VMware KB: VMware ESXi 5.1, Patch ESXi510-201407401-BG: Updates esx-base

_________________________________________________________________________________________ If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards, P.
0 Kudos