Resolving import errors

For most import errors, Skytap Cloud skips the VM that caused the error and imports the other VMs in the import job. For MD5 errors, Skytap Cloud stops the import process and no VMs are imported.

Once you resolve the error, see Retrying a failed import for instructions about retrying the import.

Error Message

Resolution

Convert to a supported hardware version and try again.

The VM is set to an unsupported hardware version. For a list of supported hardware versions, see Hardware version compatibility for importing VMs into Skytap Cloud. Convert the VM to a supported hardware version by upgrading or downgrading the hardware version.

MD5 indicates one or more files are missing. Check files and retry.

  • Make sure that the MD5 hash value you entered in Skytap Cloud is correct.
  • Check the upload depot to make sure that you included all of the files you listed in the MD5 hash value set.
  • There may have been file corruption during the upload process.

    • Use SFTP instead of FTP to upload files.
    • Make sure the transfer is complete before you click Create environment on the Imports page.

MD5 indicates one or more uploaded file is corrupted. Upload and retry.

  • Make sure that the MD5 hash value you entered in Skytap Cloud is correct.
  • The file may be corrupted.
    • Use SFTP instead of FTP for uploading files.
    • Make sure the transfer is complete before you click Create environment on the Imports page.

Missing or corrupted files found in the upload. Check files and retry upload.

  • A file may be named incorrectly (for example, a 7z file may be named as a ZIP file).
  • The file may be corrupted.
    • Include an MD5 hash value during the import job.
    • Use SFTP instead of FTP for uploading files.
    • Make sure the transfer is complete before you click Create environment on the Imports page.

No .vmx or .ovf file found in the upload. Check files and retry upload.

  • A file may be missing from your upload. Make sure the upload includes a VMX, OVF, OVA, or compressed file containing a VMX or OVF file.
  • You may be importing the wrong file type. Make sure you are importing a supported file type.
  • The file may be corrupted.
    • Include an MD5 hash value during the import job.
    • Use SFTP instead of FTP for uploading files.

Uncompressed file size of the VM files must be less than 1 TB.

The combined size of the uncompressed VM files is larger than 1 TB. Separate the VM imports into smaller import jobs.

Unsupported hypervisor type

You tried to upload a VirtualBox VM or a non-VMware based image. Create a VMware-based VM (see Converting non-VMware-based VMs for import) and retry the import using a supported file type.

Unsupported OVF version. The VM must be OVF version 1.0 or 1.1

When you export the VM from the VMware hypervisor, select OVF version 1.0 or 1.1. Upload the new VM files and retry the import.

Upload and retry using MD5 and SFTP.

The VMDK file was corrupted.

  • Include an MD5 hash value during the import job.
  • Use SFTP instead of FTP for uploading files.
  • Make sure the transfer is complete before you click Create environment on the Imports page.

Upload missing VMDK files and retry.

  • The VM uses multiple VMDK files. Either the VM uses multiple virtual hard disks or the primary virtual hard disk for the VM was created using the Split virtual disks into multiple files option.
  • The import task cannot locate one or more of the VMDK files for a VM. Locate and restore the missing VMDK files, and then retry the import.

    To see a list of the VMDK files that belong to a VM

    • For a VM that contains multiple virtual hard disks, open the VMX file in a text editor, and then search for instances of vmdk in the file.
    • For a virtual hard disk was created with the Split virtual disks into multiple files option, open the 1k root VMDK file (for example, Debian 8.3.0 LXDE.vmdk) in a text editor.

VMDK filename contains prohibited characters

  • Skytap Cloud does not support the following characters in VMDK files:
    ' " \ `
  • If your VMDK file includes these characters, rename the file and generate a new OVF or VMX file that references the renamed VMDK file.

Your hardware version can’t be downgraded

Explanation: This error can occur when importing a VM with an unsupported hardware version. Skytap Cloud supports hardware versions 7 through 11. If the VM is set to a higher hardware version, you must downgrade it outside of Skytap Cloud before it can be imported.

For instructions about downgrading a VM outside of Skytap Cloud, see the following VMware videos:

Notes

  • VMware regularly releases new hardware versions. To support these, Skytap must perform extensive testing and backend changes to ensure maximum compatibility between Skytap Cloud and the new hardware version. As such, there is typically a lag time between the release of a new hardware version and its functionality in Skytap Cloud.
  • For more information about supported hardware versions, see Checking VM hardware version.