id	summary	reporter	owner	description	type	status	component	version	resolution	keywords	cc	guest	host
8041	SHA1 sum check seems to be failing on import of OVF file	Ed Borasky		"I created a virtual machine using VMware Workstation 7.1. I exported it to OVF format using VMware's ""ovftool"", version 2.0.1, giving me the following four files:

-rw-r--r-- 1 znmeb users 2203095552 2011-01-08 23:43 Project_Kipling-disk1.vmdk
-rw-r--r-- 1 znmeb users 4346398720 2011-01-08 23:37 Project_Kipling-file1.iso
-rw-r--r-- 1 znmeb users        217 2011-01-08 23:43 Project Kipling.mf
-rw-r--r-- 1 znmeb users       4873 2011-01-08 23:43 Project Kipling.ovf

The ""manifest"" (.mf) file has the SHA1 checksums of the other three files:
> more Project\ Kipling.mf 
SHA1(Project Kipling.ovf)= 7ffc9e47eae73020d6eea9d05f9c9f910cf3a532
SHA1(Project_Kipling-file1.iso)= 2b6212d6df83c29dd1b1801cc25660359a0d917d
SHA1(Project_Kipling-disk1.vmdk)= d716e964d85beaa23bdbb4c5072f81539792490d

And the checksums look correct:
> sha1sum Project\ Kipling.ovf 
7ffc9e47eae73020d6eea9d05f9c9f910cf3a532  Project Kipling.ovf
> sha1sum Project_Kipling-file1.iso 
2b6212d6df83c29dd1b1801cc25660359a0d917d  Project_Kipling-file1.iso
> sha1sum Project_Kipling-disk1.vmdk 
d716e964d85beaa23bdbb4c5072f81539792490d  Project_Kipling-disk1.vmdk

But when I try to import the OVF file into VirtualBox 4.0.0, it spends a few minutes importing the virtual disk. Then it crashes with the attached error message. 


"	defect	closed	OVF	VirtualBox 4.0.0	obsolete	SHA1		Linux	Linux