It helped in the sense that the error you are getting has nothing to do with this thread from 2 yrs ago.
The error you are getting says the .ovf file is corrupted.
Where did you get the .ovf file?
Can't Import OVF - Error in File
-
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Re: Can't Import OVF - Error in File
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
Re: Can't Import OVF - Error in File
the ovf file was obtained from "retriever.us.oracle.com" , and it was packed as smaller self extracting zip files.
Not sure if the corruption happened during download or unzipping.
Not sure if the corruption happened during download or unzipping.
-
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Re: Can't Import OVF - Error in File
I don't know but, I've only downloaded multi-part zip files that are re-constructed into an .ova file from Oracle and Modern.IE. They've always worked. I use "The Unarchiver" which is a free archive App. I believe you can get it from the App Store. See if that helps.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
Re: Can't Import OVF - Error in File
Hello,
I solved this issue
1. Extracting the files in the OVA file
2. Files included 2 .vmdk files
3. Created a NEW VM with the characteristics of the one that I was importing
4. Instead of creating new Disks, I chose the .vmdk files extracted
5. Started the VM up
Regards
I solved this issue
1. Extracting the files in the OVA file
2. Files included 2 .vmdk files
3. Created a NEW VM with the characteristics of the one that I was importing
4. Instead of creating new Disks, I chose the .vmdk files extracted
5. Started the VM up
Regards
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Can't Import OVF - Error in File
A mistake. The VMDK from an OVA is usually stream optimized (i.e. compressed), and will give very poor peformance in a VM: you'll find that VirtualBox silently created a difference file for it in the Snapshots subfolder, since the VMDK you provided is not writeable. Every read from the VMDK will involve parsing the compressed image.Alebal76 wrote: 4. Instead of creating new Disks, I chose the .vmdk files extracted
Use VBoxManage to clone the VMDK to VDI format, then build a new VM around the clone (don't mount the VDI in the VM you already created, since the damage is already done to that VM).
Re: Can't Import OVF - Error in File
In my case (windows 10) the problem was that the virtualization was disabled.
So i enabled that through BIOS (search for: how-to-enable-intel-vt-x-in-your-computers-bios-or-uefi-firmware) and the machine was installed properly.
So i enabled that through BIOS (search for: how-to-enable-intel-vt-x-in-your-computers-bios-or-uefi-firmware) and the machine was installed properly.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Can't Import OVF - Error in File
@Drew7,
Thanks for the feedback, but your issue had almost nothing to do with the title of the thread, it was an entirely different problem.
And since this is a 5-year old thread, which seems to attract replies solely based on the title, I'm going to lock it. Something more ... recent should be referenced, if need be. If not, a new thread is always the best option.
Thanks for the feedback, but your issue had almost nothing to do with the title of the thread, it was an entirely different problem.
And since this is a 5-year old thread, which seems to attract replies solely based on the title, I'm going to lock it. Something more ... recent should be referenced, if need be. If not, a new thread is always the best option.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.