Purple error during ESXi 8 installation: Failed to decompress vmx.v00, status: Admission check failed for memory resource

Written by - 1 comments

Published on - Listed in VMware Virtualization


As maintainer of the open source monitoring plugin check_esxi_hardware, I test the plugin's compatibility against multiple versions of VMware ESXi (vSphere). The newest version, ESXi 8, was officially released in November 2022. Time to test check_esxi_hardware on a ESXi 8.

ESXi 8 install fails with purple screen

To simplify the setup, I usually install a ESXi version as a virtual machine. This allows to quickly start up ESXi and its services, including the CIM server. The plugin can then be tested against this ESXi version. 

But when I created a new VM and tried to install ESXi 8 in it, the following purple error was shown on the VM console:

The system has found a problem on your machine and cannot continue.
Failed to decompress vmx.v00, status: Admission check failed for memory resource

This rather cryptic error message does not really show what is causing it.

With the [ESC] key the local debugger can be opened:

Using the [L] key to see the vmkernel log, which hopefully shows some additional information about this error.

Although the log events don't really show an explanation, there is one important "hint" in the logs:

BootModule: 446: Unable to allocate MPNs for decompression

Although I am not sure what "MPNs" stands for, the string "allocate" usually refers to memory allocation of a program or process. Could it be related to the memory of this VM?

ESXi 8 requires at least 8GB memory

To make sure, the ESXi 8 hardware requirements were verified. And indeed, one of the requirements clearly states:

ESXi 8.0 requires a minimum of 8 GB of physical RAM. Provide at least 12 GB of RAM to run virtual machines in typical production environments. 

After turning off the VM, increasing the memory to 8GB, the installation was attempted again. And this time the setup continued:


Add a comment

Show form to leave a comment

Comments (newest first)

SMandal from IN wrote on Jan 8th, 2024:

Its true, error due to inadequate resource allocation to ESXi.


RSS feed

Blog Tags:

  AWS   Android   Ansible   Apache   Apple   Atlassian   BSD   Backup   Bash   Bluecoat   CMS   Chef   Cloud   Coding   Consul   Containers   CouchDB   DB   DNS   Database   Databases   Docker   ELK   Elasticsearch   Filebeat   FreeBSD   Galera   Git   GlusterFS   Grafana   Graphics   HAProxy   HTML   Hacks   Hardware   Icinga   Influx   Internet   Java   KVM   Kibana   Kodi   Kubernetes   LVM   LXC   Linux   Logstash   Mac   Macintosh   Mail   MariaDB   Minio   MongoDB   Monitoring   Multimedia   MySQL   NFS   Nagios   Network   Nginx   OSSEC   OTRS   Office   PGSQL   PHP   Perl   Personal   PostgreSQL   Postgres   PowerDNS   Proxmox   Proxy   Python   Rancher   Rant   Redis   Roundcube   SSL   Samba   Seafile   Security   Shell   SmartOS   Solaris   Surveillance   Systemd   TLS   Tomcat   Ubuntu   Unix   VMWare   VMware   Varnish   Virtualization   Windows   Wireless   Wordpress   Wyse   ZFS   Zoneminder