ESXi 6.5/6.0 host fails with purple diagnostic screen when collecting diagnostic information
Article ID: 318356
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
Symptoms:
- ESXi host fails with a purple diagnostic screen when collecting diagnostic information and the stack trace:
2017-02-06T18:52:04.284Z cpu39:72196)@BlueScreen: #PF Exception 14 in world 72196:Default-drai IP 0x4180158f56de addr 0x4306a69c41c8
PTEs:0x800000208080e023;0x8000000146ba1063;0x800000018ac9b063;0x0;
2017-02-06T18:52:04.284Z cpu39:72196)Code start: 0x418015800000 VMK uptime: 0:00:53:55.612
2017-02-06T18:52:04.285Z cpu39:72196)0x4391d021bf50:[0x4180158f56de]SPLockIRQWork@vmkernel#nover+0x26 stack: 0x4306a69c41c8
2017-02-06T18:52:04.285Z cpu39:72196)0x4391d021bf70:[0x418015914b00]VMKStatsDrainWorldLoop@vmkernel#nover+0x90 stack: 0x6
2017-02-06T18:52:04.286Z cpu39:72196)0x4391d021bfe0:[0x418015ac8bd5]CpuSched_StartWorld@vmkernel#nover+0x99 stack: 0x0
2017-02-06T18:52:04.290Z cpu39:72196)base fs=0x0 gs=0x418049c00000 Kgs=0x0
2017-02-06T18:52:04.290Z cpu39:72196)vmkernel 0x0 .data 0x0 .bss 0x0
Note: This log excerpt is an example. Date, time, and environmental variables may vary depending on your environment.
Environment
VMware vSphere ESXi 5.1
VMware ESXi 4.0.x Embedded
VMware ESXi 3.5.x Installable
VMware ESXi 4.1.x Embedded
VMware ESXi 4.1.x Installable
VMware ESXi 4.0.x Installable
VMware vSphere ESXi 6.5
VMware ESXi 3.5.x Embedded
VMware vSphere ESXi 5.5
VMware vSphere ESXi 5.0
VMware vSphere ESXi 6.0
VMware ESXi 4.0.x Embedded
VMware ESXi 3.5.x Installable
VMware ESXi 4.1.x Embedded
VMware ESXi 4.1.x Installable
VMware ESXi 4.0.x Installable
VMware vSphere ESXi 6.5
VMware ESXi 3.5.x Embedded
VMware vSphere ESXi 5.5
VMware vSphere ESXi 5.0
VMware vSphere ESXi 6.0
Cause
This issue occurs due to a race condition when running vm-support. This is more likely to occur when gathering performance snapshots with the diagnostic information.
Resolution
This issue is resolved in ESXi 6.5 U1 & ESXi 6.0 P05, available at VMware Downloads.
To work around this issue, collect the performance snapshot separately by running esxtop in batch mode. For more information, see Exporting esxtop performance data as a CSV file and manipulating it from the command-line (1004953).
To work around this issue, collect the performance snapshot separately by running esxtop in batch mode. For more information, see Exporting esxtop performance data as a CSV file and manipulating it from the command-line (1004953).
Additional Information
Feedback
Yes
No
Powered by
