operating-system: SHA digest error when importing ova with VMWare Workstation 16
Describe the issue you are experiencing
Importing the Home Assistant OS ova appliance into VMWare Workstation version 16.2.4 build-20089737 fails with this error:
SHA digest of file home-assistant.vmdk does not match manifest.
This happens with the following versions of HAOS (note that this includes a recent dev version):
haos_ova-8.4.ova
haos_ova-10.0.dev20220907.ova
haos_ova-8.5.ova
If I remove the manifest home-assistant.mf from the .ova, the appliance imports successfully. Also noteworthy is that the appliance imports into Oracle VirtualBox (6.1) and VMWare ESXi (6.7, 7.1) as-is, without error.
The actual checksums are fine. As an example, the haos_ova-8.5 manifest (home-assistant.mf) contains these lines:
SHA256(home-assistant.ovf)= 64504b3ae7dd5bf32d74187874538bcf2ea204e1ce0cfbbee399e00ed46d4982
SHA256(home-assistant.vmdk)= 12cec555efcb96a675b7b4aab283ae0148f2b8f36a6983c3908b94519b9b7b12
When I compute the checksums for the two referenced files, they match:
home-assistant.ovf SHA-256: 64504b3ae7dd5bf32d74187874538bcf2ea204e1ce0cfbbee399e00ed46d4982
home-assistant.vmdk SHA-256: 12cec555efcb96a675b7b4aab283ae0148f2b8f36a6983c3908b94519b9b7b12
I have searched existing issues to avoid posting a dup, and found some related discussion, but nothing that addresses this specific issue with VMWare Workstation. One such issue was #826 - since fixed/closed - dealing with ESXi import errors, but one commenter reported that this was not yet fixed in relation to Workstation (see https://github.com/home-assistant/operating-system/issues/826#issuecomment-993766392 and https://github.com/home-assistant/operating-system/issues/826#issuecomment-993855319)
Many appliances still use SHA1 for the manifest file, and it made me wonder if perhaps VMWare Workstation only supported that, and not SHA256. There was an issue related to ESXi and the hash function on the nextcloud issue tracker https://github.com/nextcloud/vm/issues/910#issuecomment-673764335 but this was dealing with ESXi and not Workstation, and with an older (5.5) unsupported (https://kb.vmware.com/s/article/51491) release of the hypervisor. I looked at the manifest of another project (https://gns3.com/software/download-vm) that ships OVA appliance files, and it uses SHA256 hashes, and the OVA imports into Workstation fine, so the same should apply to the HAOS one. Interestingly, they ship a separate OVA files for Workstation/Fusion and ESXi.
[this is my first bug report for this project, so Iād appreciate any pointers if anything is amiss in my report]
What operating system image do you use?
ova (for Virtual Machines)
What version of Home Assistant Operating System is installed?
NA
Did you upgrade the Operating System.
No
Steps to reproduce the issue
- Download OVA appliance.
- Start to import into VMWare Workstation.
Anything in the Supervisor logs that might be useful for us?
N/A
Anything in the Host logs that might be useful for us?
N/A
System Health information
No response
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 21 (16 by maintainers)
He is correct.
Anyone still having the issue, try these instructions: https://rootedshell.medium.com/failed-to-open-virtual-machine-sha1-digest-of-file-xxxxxxxx779-disk1-vmdk-does-not-match-manifest-7d0d94db4451
STEP 1: Extract the xxxxxxxx.ova file with 7zip. STEP 2: Delete [xxxxx.mf] manifest file. STEP 3: Open xxxxxxxxxxxx.ovf File in VMWare. STEP 4: Virtual Machine Import, Done. š
This is still an issue.
Have you guys tried to import the ova images we at the RaspberryMatic project generate in a similar manner than here? See https://github.com/jens-maus/RaspberryMatic/releases/latest