Hello All,
I've recently installed VirtualBox-4.2.1.4-86644-Win.exe on my 64-bit Windows 7 host. I then tried to import an existing OracleVM and get the following error:
Failed to import appliance C:\Users\IBM_ADMIN\Desktop\OracleVM Linux\Q7Template.ova.
Seeking within the archive failed (VERR_TAR_CHKSUM_MISMATCH).
Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: Appliance
Interface: IAppliance {3059cf9e-25c7-4f0b-9fa5-3c42e441670b}
I'm not sure if the platform the original image got created on makes a difference or not, but I can find out that info if it helps. My first time using virtualbox so I'm stumped.
Error importing .ova image Seeking within the archive failed
-
BigDataITGuy
- Posts: 2
- Joined: 28. Jun 2013, 13:55
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Error importing .ova image Seeking within the archive fa
No, the source makes no difference. The method of transporting the image might, e.g. if the file is larger than 4GB and you used a FAT32 formatted external drive. Bad downloads are also possible. The error message is saying that the OVA file has been corrupted somehow.
Do an md5 checksum test if you doubt the error.
Do an md5 checksum test if you doubt the error.
-
BigDataITGuy
- Posts: 2
- Joined: 28. Jun 2013, 13:55
Re: Error importing .ova image Seeking within the archive fa
File is less than 3GB. I downloaded it and then copied it to another machine using a FAT32 formatted flash drive. Also, copied from 32-bit system to 64-bit. I've done an md5 checksum but how would I verify the image downloaded correctly without the original checksum value to compare against?
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Error importing .ova image Seeking within the archive fa
You need to get the original md5 from the provider of the VM, after confirming that the file is not corrupted at source.
Again, a 32bit / 64bit difference in the hosts is not significant.
Again, a 32bit / 64bit difference in the hosts is not significant.