The ESXi host will be unable to save core dumps, resulting in the alert: "No Coredump Target Has Been Configured. Host Core Dumps Cannot Be Saved".
When this condition occurs, the host's configuration does not point to a valid location to save a core dump file (a snapshot of the system memory and state at the time of a crash), meaning critical diagnostic information will be lost if the host experiences a purple screen of death (PSOD).
VMware ESXi 8.x
The primary cause for this alert is that the previously configured core dump file location has become invalid or inaccessible.
This commonly occurs if the core dump file itself or the storage it resided on (such as a datastore) was manually deleted or removed from the host's view. When the file is lost, the ESXi host no longer has a designated, valid target to save the coredump.
This issue can be resolved by recreating and re-enabling a core dump file target on the ESXi host.
Run the following commands in the ESXi Shell (either through an SSH session or on the host's console):
esxcli system coredump file add --auto
esxcli system coredump file set --smart --enable true
esxcli system coredump file listOnce the configuration is verified as Active, the ESXi host will be able to save a core dump file if a PSOD occurs, and the alert should clear.