Error: "The VM failed to resume on the destination during early power on" while Migrating a virtual machine
search cancel

Error: "The VM failed to resume on the destination during early power on" while Migrating a virtual machine

book

Article ID: 315380

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • Cannot migrate a virtual machine
  • Migrating a virtual machine fails
  • vMotion failing with error: 
    The VM failed to resume on the destination during early power on


    Environment

    VMware vSphere 7.0.x
    VMware vSphere 6.x
    VMware vSphere ESXi 5.1
    VMware vSphere ESXi 5.5

    Resolution

    Reason for vMotion failing with this error can be one from the following

    Resolution for the error for specific reason:

    For the error different resolution is listed below for every different cause of the error:

      The destination file system does not support large files

      This issue occurs if the block size of the destination datastore does not support a VMDK as large as the source.
       
      To resolve this issue, ensure that the destination datastore is formatted with a block size that is large enough to support the VMDK file of the source machine. For more information, see Block size limitations of a VMFS datastore (1003565).

      Failed to lock the file

      This issue occurs if another process/host has already opened the file that your process/host is attempting to open.
       
      To resolve this issue:

      Could not open/create change tracking file

      This issue may occur if a filename-ctk.vmdk file was earlier created and has not been cleared.

      To resolve this issue, see Powering on a virtual machine fails after a storage outage with the error: could not open/create change tracking file (2009244).

      Cannot allocate memory

      This issue may occur if the VMFS module runs out of heap space.

      To resolve this issue, see An ESXi/ESX host reports VMFS heap warnings when hosting virtual machines that collectively use 4 TB or 20 TB of virtual disk storage (1004424).

      The file specified is not a virtual disk

      This issue may occur when the .vmdk descriptor file is corrupt or missing.

      To resolve this issue, create a new .vmdk descriptor file for this disk and then unregister and re-register the virtual machine. This ensures that the vSphere Client detects the correct disk size and the virtual machine powers on properly.

      For more information on creating a new descriptor file, see Recreating a missing virtual disk (VMDK) header/descriptor file (1002511).

      Insufficient permission to access file

      This issue is usually observed in virtual machines located on NFS datastores. This issue may occur due to permissions issues on the NFS datastore.
       
      To resolve this issue, ensure that the host has the correct read/write permissions to access the NFS export. If your storage array has the No Root Squash option, ensure that the option is enabled or contact your Storage Administrator.


      Additional Information

      For more information, see: For translated versions of this article, see:

      Powered by Wolken Software