Creating MD5 hash values for VM imports

A hash value can be used to verify that each OVA, OVF, VMX, VMDK, or 7z file was not corrupted during the upload process.

To create and use hash values during the import process
  1. Generate an MD5 hash value for each import file using an MD5 hash value utility or tool prior to the import. These tools are built into some operating system versions (for example, Certutil for Windows, md5sum for Linux, and md5 for macOS); there are also several third-party tools available.

    Sample command:

    CertUtil -hashfile MyVM.ova MD5
    

    Sample output:

    c4 14 d8 fe 88 18 86 8e a4 15 89 03 2f e1 d5 6e
    

    To format this into an accepted hash value format, remove the spaces and add the file name. Example: c414d8fe8818868ea41589032fe1d56e MyVM.ova

    Sample command:

    md5sum MyVM.ova > hash.md5
    

    Sample output:

    c414d8fe8818868ea41589032fe1d56e MyVM.ova
    

    Sample command:

    md5 MyVM.ova
    

    Sample output:

    MD5 (MyVM.ova) = c414d8fe8818868ea41589032fe1d56e
    

    Sample command:

    csum -h MD5 MyVM.ova
    

    Sample output:

    MD5 (MyVM.ova) = c414d8fe8818868ea41589032fe1d56e
    

    Create a single hash value for an archive, not for each file in the archive. For example, if you have a 7z file with several VMX/VMDK files, create just one hash value for the 7z file.

  2. Provide the generated MD5 hash value(s) (see Importing x86 VMs using the VM Imports page).

    The format for each hash value must one of the following:

    • MD5 (MyVM.ova) = bca6d3862c661b615a374d7ef61252c5
    • 9f1001eb94538c5ca664e1e1740b3504 MyVM.ova
    • 9f1001eb94538c5ca664e1e1740b3504 *MyVM.ova (for binary transfers)

    Notes

    • The file name is case sensitive.
    • List multiple values on new lines or separated by commas.
  3. During import, Skytap generates an MD5 hash value for each file and compares it against the MD5 hash value that you provide. If an MD5 hash value comparison fails, the import job stops with an error.