VMware ESXi 5.0 and ESXi 5.1 host fails with a purple diagnostic screen and reports the error: NOT_IMPLEMENTED bora/vmkernel/sched/memsched.c:17724

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• ESXi 5.0 and ESXi 5.1 host fails with a purple diagnostic screen
• You see a stack trace similar to one of these:
  
  
• cpu4:8243)@BlueScreen: NOT_IMPLEMENTED bora/vmkernel/sched/memsched.c:17724
  cpu4:8243)Code start: 0x41802b200000 VMK uptime: 10:19:25:27.335
  cpu4:8243)0x412200cdbaf0:[0x41802b27abff]PanicvPanicInt@vmkernel#nover+0x56 stack: 0x3000000008
  cpu4:8243)0x412200cdbbd0:[0x41802b27b4a7]Panic@vmkernel#nover+0xae stack: 0x100000000000000
  cpu4:8243)0x412200cdbc50:[0x41802b3d88eb]MemSched_WorldCleanup@vmkernel#nover+0x426 stack: 0x4100018a4fb0
  cpu4:8243)0x412200cdbef0:[0x41802b3033b8]WorldCleanup@vmkernel#nover+0x1cb stack: 0x4700cdbf40
  cpu4:8243)0x412200cdbf60:[0x41802b303829]WorldReap@vmkernel#nover+0x318 stack: 0x0
  cpu4:8243)0x412200cdbff0:[0x41802b2483c8]helpFunc@vmkernel#nover+0x517 stack: 0x0
  cpu4:8243)0x412200cdbff8:[0x0]<unknown> stack: 0x0
  cpu4:8243)base fs=0x0 gs=0x418041000000 Kgs=0x0
  
  
• cpu12:115486)@BlueScreen: #PF Exception 14 in world 115486:vmast.115485 IP 0x41801f080a1e addr 0x410401503420
  cpu12:115486)Code start: 0x41801f000000 VMK uptime: 2:04:43:17.260
  cpu12:115486)0x41220c79bcd0:[0x41801f080a1e]PShareHashTableWalk@vmkernel#nover+0x219 stack: 0x41220c79bd24
  cpu12:115486)0x41220c79bd50:[0x41801f081c6d]PShare_RemoveHint@vmkernel#nover+0x178 stack: 0x41220c79bda0
  cpu12:115486)0x41220c79bdd0:[0x41801f0ca39c]VmMemCow_PShareRemoveHint@vmkernel#nover+0x123 stack: 0x9582e
  cpu12:115486)0x41220c79be30:[0x41801f0cd70a]VmMemCowPFrameRemoveHint@vmkernel#nover+0x6d stack: 0x410000000000
  
  
• cpu12:115486)0x41220c79bfa0:[0x41801f0cef79]VmMemCowPShareFn@vmkernel#nover+0x548 stack: 0x41220c79bff0
  cpu12:115486)0x41220c79bff0:[0x41801f0b13c4]VmAssistantProcessTask@vmkernel#nover+0x19f stack: 0x0
  cpu12:115486)0x41220c79bff8:[0x0] stack: 0x0 2012-12-14T22:17:28.820Z cpu12:115486)base fs=0x0 gs=0x418043000000 Kgs=0x0
  
  
• cpu42:737265)@BlueScreen: #GP Exception 13 in world 737265:python @ 0x41801702449d
  cpu42:737265)Code start: 0x418017000000 VMK uptime: 11:22:39:06.836
  cpu42:737265)0x41237fc5b5a0:[0x41801702449d]BuddyAllocateInt@vmkernel#nover+0x168 stack: 0x41237fc5b610
  cpu42:737265)0x41237fc5b610:[0x4180170257f6]Buddy_AllocateColor@vmkernel#nover+0x1d1 stack: 0x4100013b4000
  cpu42:737265)0x41237fc5b670:[0x418017069521]MemMapAllocateAndAccount@vmkernel#nover+0x80 stack: 0x418017485f68
  cpu42:737265)0x41237fc5b6b0:[0x418017069de7]MemMap_AllocateFromNode@vmkernel#nover+0xd2 stack: 0x1
  cpu42:737265)0x41237fc5b850:[0x418017212725]MemDistributeNUMAPolicy@vmkernel#nover+0x7b0 stack: 0x6f0334d9
  cpu42:737265)0x41237fc5b8c0:[0x41801721154c]MemDistributeAllocateAndTestPages@vmkernel#nover+0xaf stack: 0x41237
  cpu42:737265)0x41237fc5b910:[0x41801721162d]MemDistributeAllocAndTestPagesLegacy@vmkernel#nover+0xa8 stack: 0x41
  cpu42:737265)0x41237fc5b940:[0x4180172116e1]MemDistribute_AllocUserWorldPages@vmkernel#nover+0x30 stack: 0x41237
  cpu42:737265)0x41237fc5b970:[0x4180174816f7]UserMemAllocPageInt@<None>#<None>+0xce stack: 0x41237fc5b9c0
  cpu42:737265)0x41237fc5bbc0:[0x418017485f68]UserMem_HandleMapFault@<None>#<None>+0x59b stack: 0x410023836b10
  cpu42:737265)0x41237fc5bc00:[0x418017475d04]UserExceptionHandleKernelFault@<None>#<None>+0xe7 stack: 0x0
  cpu42:737265)0x41237fc5bc20:[0x41801704cda2]Int14_PF@vmkernel#nover+0x131 stack: 0x41237fc5bd00
  cpu42:737265)0x41237fc5bc30:[0x418017110064]gate_entry@vmkernel#nover+0x63 stack: 0x0
  cpu42:737265)0x41237fc5bd00:[0x4180174d8cdd]UWVMKPrivateSyscall_AddPage64@<None>#<None>+0x104 stack: 0x200000000
  cpu42:737265)0x41237fc5bd30:[0x418017477339]User_CopyOut@<None>#<None>+0xa8 stack: 0x298549a6
  cpu42:737265)0x41237fc5bdd0:[0x4180172387e5]BC_ReadFHID@vmkernel#nover+0xac stack: 0x41237fc5be04
  cpu42:737265)0x41237fc5be30:[0x41801748ff0e]UserFileReadv@<None>#<None>+0x6d stack: 0x41237fc5be70
  cpu42:737265)0x41237fc5beb0:[0x418017496331]LinuxFileDesc_Read@<None>#<None>+0xf4 stack: 0x4180171b84d9
  cpu42:737265)0x41237fc5bef0:[0x4180174766fa]User_LinuxSyscallHandler@<None>#<None>+0xe5 stack: 0x0
  cpu42:737265)0x41237fc5bf10:[0x4180170a82be]User_LinuxSyscallHandler@vmkernel#nover+0x19 stack: 0xfff37f78
  cpu42:737265)0x41237fc5bf20:[0x418017110064]gate_entry@vmkernel#nover+0x63 stack: 0x0
  cpu42:737265)base fs=0x0 gs=0x41804a800000 Kgs=0x0
  
  
• You may experience this issue when performing a vMotion of a virtual machine from one host to another
• The ESXi 5.0 and ESXi 5.1 host fails with a purple diagnostic screen after upgrading VMware Tools in the virtual machine

Environment

VMware vSphere ESXi 5.0
VMware vSphere ESXi 5.1

Resolution

For ESXi 5.0
This issue is resolved in ESXi 5.0 P07 (build 1489271) (Build 1478905 Security-only)
For more information, see VMware ESXi 5.0, Patch ESXi500-201401401-BG: Updates esx-base (2065691).

For ESXi 5.1
This issue is resolved in ESXi 5.1 P01 (build 914609).

For more information, see VMware ESXi 5.1, Patch ESXi510-201212401-BG: Updates esx-base (2035777).

Additional Information

VMware ESXi 5.1, Patch ESXi510-201212401-BG: Updates esx-base
VMware ESXi 5.0, Patch ESXi500-201401401-BG: Updates esx-base
ESXi 5.1 主机失败并显示紫色诊断屏幕，其中报告以下错误：NOT_IMPLEMENTED bora/vmkernel/sched/memsched.c:17724
VMware ESXi 5.0 および ESXi 5.1 ホストが失敗し、紫色の診断画面が表示され、次のエラーが報告される: NOT_IMPLEMENTED bora/vmkernel/sched/memsched.c:17724