![]() |
| Example of a PSOD kernel stack trace screen |
- Hardware failure
- Out of memory
- Hung CPU conditions
- Misbehaving drivers (null pointers, invalid memory access, etc)
- NMI (Non Maskable Interrupts)
- Screenshot of PSOD kernel stack trace screen (if possible)
- Support logs from the vm-support command
- Kernel log(should be included in vm-support, but better safe then sorry)
- Kernel core dump (only needed if a developer asks for it)
## Kernel log - will output: vmkernel-log.1
# esxcfg-dumppart -L /vmfs/devices/disks/$( \
esxcfg-dumppart --get-active | awk '{print $1}' )
To manually collect the kernel core dump: (if developer asks for it)
## Kernel core dump - will output: vmkernel-zdump.1
## Note: ESXi 5.x will put kernel dump here:
## /scratch/core/vmkernel-zdump.*
# esxcfg-dumppart -C -D /vmfs/devices/disks/$( \
esxcfg-dumppart --get-active | awk '{print $1}' )
For testing purposes, one can manually trigger a PSOD:
# vsish -e set /reliability/crashMe/Panic

No comments:
Post a Comment