This article provides steps to extract a log from a vmkernel-zdump
file after a purple diagnostic screen error. This log contains similar information to that seen on the purple diagnostic screen and can be used in further troubleshooting.
This article assumes that a vmkernel-zdump
file is available. If an ESX or ESXi host has failed with a purple diagnostic screen, but no vmkernel-zdump file is available, see:
vmkernel-zdump
file:
vmkernel-zdump
file in the /root/
or /var/core/
directory:# ls /root/vmkernel* /var/core/vmkernel*
/var/core/vmkernel-zdump-073108.09.16.1
vmkdump
or esxcfg-dumppart
utility to extract the log. For example:# vmkdump -l /var/core/vmkernel-zdump-073108.09.16.1
created file vmkernel-log.1
# esxcfg-dumppart -L /var/core/vmkernel-zdump-073108.09.16.1
created file vmkernel-log.1
vmkernel-log.1
created above is a file in plain text that you can read with a text editor, though may start with null characters. Focus on the end of the log, which is similar to:VMware ESX Server [Releasebuild-98103]
PCPU 1 locked up. Failed to ack TLB invalidate.
frame=0x3a37d98 ip=0x625e94 cr2=0x0 cr3=0x40c66000 cr4=0x16c
es=0xffffffff ds=0xffffffff fs=0xffffffff gs=0xffffffff
eax=0xffffffff ebx=0xffffffff ecx=0xffffffff edx=0xffffffff
...
vmkernel-log.1
. If another file with the same name already exists, the new file is created with the number suffix incremented.If you require further assistance in diagnosing a purple diagnostic screen error:
Generating a VMkernel zdump manually from a dump file in ESXi host