You should encounter the checksum error again. Please follow this guide to fix this issue finally.
When you modify an
OVF file in a virtual machine deployment package, the checksum recorded in the .mf (Manifest) file will no longer match the altered OVF file. You must update the .mf file to reflect the new checksum. Here's how to do it:
Steps to Update the .mf File
- Verify the Current Structure
An OVF package typically contains:
- file.ovf: The OVF descriptor file.
- file.vmdk: Virtual disk file(s).
- file.mf: The manifest file containing checksums.
- file.cert (Optional): A certificate file for signing.
Open the .mf file to confirm its format. It looks like:
SHA256(file.ovf)= <checksum>
SHA256(file.vmdk)= <checksum>
- Generate a New Checksum for the OVF File
Use a checksum tool to calculate the new checksum for the modified OVF file.
sha256sum file.ovf
- Windows (using PowerShell):
Get-FileHash file.ovf -Algorithm SHA256
- The output will look something like:
8f8b37d89e77f1a1fefea5d1ffb24e78b1d79f1a4bce5e52e8a3b4794e87af68
Replace the old checksum in the .mf file with the new one. For example:
SHA256(file.ovf)= 8f8b37d89e77f1a1fefea5d1ffb24e78b1d79f1a4bce5e52e8a3b4794e87af68
SHA256(file.vmdk)= <original checksum for the VMDK>
Important: Ensure the file paths and naming conventions in the .mf file match the actual files in your package.
Recheck the format of the .mf file to ensure it matches the original syntax and includes checksums for all necessary files.
If you're using tools to repackage the OVF, you can bundle it back into an .ova file (optional).
tar -cvf file.ova file.ovf file.mf file.vmdk
- Windows (using a tar tool like 7-Zip):
- Select all the OVF package files.
- Add them to a tar archive with the .ova extension.
Verify the New Package
- Use tools like VMware Workstation, VirtualBox, or ovftool to ensure the updated package works correctly:
ovftool file.ovf
- Ensure no errors arise during the deployment of the virtual machine.