Applying a patch to the ESXi host results in a host panic after a reboot

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:
When you apply a patch to VMware vSphere ESXi 5.0 GA, you experience these symptoms:

• Rebooting the host after applying the patch results in the purple diagnostics screen:
   
  #PF Exception 14 in world 4739 : jumpstart IP 0xnnnnnnn addr 0xnnnnnnn
  PTEs:0xnnnnnnnnn:0xnnnnnnnn:0x0
  cr0=oxxxxxn cr2=0xnnnn cr3=0xennnnnn cr4=0xnnnnn
  frame=0xnnnnnnnn ip=oxnnnnn ip=oxnnnnnnn err=16 rflags=0x210246
  rax=oxnnnnnnn rbx=oxnnnnnn rcx=oxnnnnnn
  rdx=oxo rbp=0xnnnnnn rsi=0xnn
  PCPU 0: ISSISUISSHISSHISISISISISISISISISISIS
  Code start :oxnnnnn VMK uptime : 0:00:00:31.075
  No place on disk to dump data
  Debugger waiting(world 4739) -- no prt for remote debugger. "escape" for local debugger.
  Applying a patch to an ESXi host and rebooting results in PSOD at the time of loading the hypervisor
   
• You applied the patching using the command:
  
  esxcli software vib install -d /vmfs/volumes/esxi_patch_name.zip

Resolution

This is a known issue affecting VMware vSphere ESXi 5.0 GA.

 

To resolve this issue, upgrade to the latest version of ESXi 5.0 from VMware Downloads.

Note: When applying the upgrade, use the command in the workaround below.

 

To work around this issue, use this command when applying a host patch:

esxcli software vib update -d /vmfs/volumes/esxi_patch_name.zip

Also see: "Configuration Upgrade Failure" after reboot of upgraded ESXi 7.0 host

Additional Information

ESXi ホストにパッチを適用すると再起動後にホスト パニックが発生する