"Admission failure in path:" messages spewing in vmkernel.log of an ESXi host. For example "2026-01-13T19:02:26.719Z hostname.domain.com vmkernel: cpu24:5781314)Admission failure in path: host/vim/vmvisor/dcui:dcui.2105653:uw.2105653".
Depending on the impacted service (DCUI service in the above example) the host may become slow or unresponsive.
NOTE: This error can be seen on occasion on any given environment, it should only be treated as a problem if it is seen constantly in the logs.
An admission failure indicates that ESXi is failing to allocate the requested amount of memory for a given process. In the example "2026-01-13T19:02:26.719Z hostname.domain.com vmkernel: cpu24:5781314)Admission failure in path: host/vim/vmvisor/dcui:dcui.2105653:uw.2105653" this process would be the DCUI process. Common causes are memory leaks or leaving a task running indefinitely (for example leaving a remote console to the DCUI connected and refreshing constantly).
services.sh restart command on ESXi hosts running vSANservices.sh restart command if LACP is in useservices.sh restart command if NSX is configured in the environmentservices.sh restart command if using shared graphics in a View environment (VGPU, vDGA, vSGA)Restarting the host management agents may impact currently running tasks, including impacting performance on the guest virtual machines of that host.
There are various known issues for admission failures for various services across various builds of ESXi, many of them benign, so it is also advised to search the Knowledge Base for your specific error. Some examples are listed below, however this list is not comprehensive.
vmkernel logs reporting Admission failure in path: host/user/pool0/pool1/vm####:vmmanon.#####
Host Remediaton fails intermittently when upgrading ESXi version with single image managed cluster
vSAN traces daemon (vsantraced service) fails with admission failure errors