Search the VMware Knowledge Base (KB)
View by Article ID

"The CPU has been disabled by the guest operating system" error (2000542)

  • 463 Ratings
Language Editions


The virtual machine stops running and reports the error:

The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.

Note: For additional error and log entries, see the Additional information section.


This article provides steps to collect troubleshooting information that must be provided to the guest operating system vendor and to resolve this issue you must contact guest operating system vendor.


The error message is seen when a guest operating system running in a VMware virtual machine intentionally halts the virtual CPU by executing the instructions CLI and HLT in succession. This can occur during a critical error or fault within the guest operating system.

This error can occur in:
  • Windows virtual machines - Caused by the guest operating system crashing (BSOD).
  • Linux virtual machines - Caused by kernel panic can also generate those messages.


Note: For kernel panic, check if guest is configured to capture a kernel dump core file. Refer to your guest OS vendor documentation for the procedure on how to capture and analyse the core dump file.

Collect information from the current outage:
  1. Identify the virtual machine and time of the outage.
  2. Take a screenshot of the virtual machine's console and note the error messages.
  3. Suspend the virtual machine and copy the checkpoint suspend (.vmss) and memory image (.vmem) (if present) from the virtual machine directory. Set the files aside.
  4. Convert the checkpoint suspend files (.vmss and .vmem) from the virtual machine into a core dump file using the vmss2core utility. For more information, see the  Debugging Virtual Machines with the Checkpoint to Core Tool  technical note.
  5. Resume the virtual machine to the suspended state, then reset the virtual machine to start the GuestOS.
  6. Collect logs from the GuestOS kernel leading up to the outage. For more information, contact the guest operating system vendor.
  7. Collect logs from the host leading up to the outage.

Additional Information

You see these additional symptoms:

In the virtual machine's log file, you see message similar to:

Vix: [ nnnnnnn vmxCommands.c: nnnn]: VMAutomation_HandleCLIHLTEvent. Do nothing


CPU disabled, Guest OS Reset

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 463 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 463 Ratings