A VM Powers Off unexpectedly after failing to Resume.

Products

• VMware vSphere ESXi

Issue/Introduction

A VM Powers Off unexpectedly after failing to Resume.

Operations such a Taking or Removing Snapshots, Resizing a Virtual Disk or performing a vMotion will all require that the virtual machine be suspended and resumed.

The VM will "freeze" for a moment while the change is happening.

Very rarely an issue can occur which prevents the VM from Resuming after this "freeze".

You may see a message in the hostd.log of the ESXi Host or the vmware.log of the virtual machine stating:

"An operation required the virtual machine to quiesce and the virtual machine was unable to continue running."

Resolution

Some specific issue has occurred which has prevented the virtual machine from resuming, and so it has been powered off.

Potential causes of these issues include, but are not limited to:

• Could not lock the files of the VM. (Another process has the lock.)
  • Check the KB article https://kb.vmware.com/s/article/10051
• Could not open the files of the VM. (Storage inaccessible)
  • Check the following Kb:https://kb.vmware.com/s/article/2004684
• Could not read files of the VM. (File corruption.)

Please open a case with VMware Support to investigate the specific issue, being sure to include the Timestamp of the issue, the vmware.log files for the affected virtual machine (included with the the ESXi log bundle for the Host where the VM is currently registered) and the ESXi log bundle for the Host where the issue occurred. (In the case of a vMotion you must also provide the ESXi log bundles of both Source and Destination Hosts.)