Bobcares

VirtualBox failed to import appliance – Top 4 Causes and Fixes

by | Nov 19, 2019

Failed to import appliance in Virtualbox?

In VirtualBox, virtual machines are referred to as appliances.

Virtualbox supports disk image files such as VDI, VMDK, VHD, and HDD.

At Bobcares, we often get requests from our customers regarding VirtualBox as part of our Server Management Services.

Today, we’ll see how our Support Engineers resolve failed to import appliance in VirtualBox error.

 

How to import Appliance in VirtualBox

First, let us discuss how our Support Engineers import Appliance in VirtualBox for your customers.

We open the Virtualbox manager.

Click on File and select Import Appliance option. Now a window appears.

Now we browse for the file and select the .OVA file. Then click next.

Within a few seconds, the file will be read and we select the RAM and the CPU required.

Finally, click on import.

Once the process is complete we can use the Virtual Machine.

 

Common errors and how we fix VirtualBox failed to import appliance

Let us discuss the common reasons for the failure and how our Support Engineers resolve the error for our customers.

1. Image file corrupt

One of the common reasons that fail VM import is file corruption. This is a common error when the file is downloaded from the internet. This happens because of network issues during the download or the file is not downloaded completely.

To resolve the error we re-download the file and try to import the file. Here, we always ensure that there are no download restrictions in the server network.

 

2. Attach as a virtual hard disk

Recently one of our customers contacted us regarding the error. Let us discuss how our Support Engineers helped the customer resolve it.

In this case, the file downloaded properly. But he was still facing the same error. Here, we helped him create a new VM and attach the file as a virtual disk.

We open Virtualbox Manager and click on New.

Now we enter the Name, Type, and version of the operating system and click next.

Then we select the Allocated memory size and click next.

Select the option Use an existing virtual hard disk file. Now we browse and locate the file. Click on Create.

Thus it creates a new virtual machine with the attached file.

3. Administrative privileges for vboxmanage.exe

Another common reason for import appliance failure in Windows happens when the vboxmanage.exe file does not have the administrative privileges. This occurs when trying to attach the disk from the USB drive. This is because the USB drive requires admin rights. So our Support Engineers run the application as an administrator and import Appliance in VirtualBox.

 

4. Corrupted VirtualBox installation

The corrupted VirtualBox installation will also fail to import appliance. During corrupted VirtualBox, the only option is to re-install the whole VirtualBox. So our Support Engineers re-install the VirtualBox once again and import the appliance.

[Need help in fixing VirtualBox errors? We are available 24×7.]

 

Conclusion

In short, we have discussed how our Support Engineers import Appliance in VirtualBox. Also, we have discussed the common causes for the error faced during import and how we resolve it.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

1 Comment

  1. Doug Munch

    If there is an aborted import, it will give fail – delete the complete folder from the Virtualbox_VMs folder. Then the import should then work normally.

    Reply

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF