Hey,
I added a .ova file and it got accidently deleted by a colleague.
When I go back to add the .ova file again a message appears with the following:
Machine settings file '/Users/Phoenix123/VirtualBox VMs/Oracle DB Developer VM/Oracle DB Developer VM.vbox' already exists.
Result Code:
VBOX_E_FILE_ERROR (0x80BB0004)
Component:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
[Urgent please help] Failed to import applience
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: [Urgent please help] Failed to import applience
You must first unregister the machine before you can import it again.
Use the media manager.
Use the media manager.
-
Phoenix123
- Posts: 4
- Joined: 4. Oct 2015, 22:19
Re: [Urgent please help] Failed to import applience
Virtual Media Manager is open. There is nothing to select under the three different headings, 'Hard Disks', 'Optical Disks' and 'Floppy Disks'Perryg wrote:You must first unregister the machine before you can import it again.
Use the media manager.
What option is it that I'm looking for inside Virtual Media Manager ?
Thank you for your help. Really appreciate it.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: [Urgent please help] Failed to import applience
If nothing is in the media manager than the guest must be gone. Have you rebooted the host and then tried to import?
-
Phoenix123
- Posts: 4
- Joined: 4. Oct 2015, 22:19
Re: [Urgent please help] Failed to import applience
I deleted VirtualBox off the Mac and then did a fresh install of VirtualBox. Hoping that it might resolve it.Perryg wrote:If nothing is in the media manager than the guest must be gone. Have you rebooted the host and then tried to import?
Now a new error message appears:
Failed to import appliance /Users/Phoenix123/Downloads/OTN_Developer_Day_VM.ova.
Could not create the imported medium '/Users/Phoenix123/VirtualBox VMs/Oracle DB Developer VM/Oracle DB Developer VM-disk1_8.vmdk'.
VMDK: cannot write allocated data block in '/Users/Phoenix123/VirtualBox VMs/Oracle DB Developer VM/Oracle DB Developer VM-disk1_8.vmdk' (VERR_DISK_FULL).
Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: ApplianceWrap
Interface: IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e}
It seems to have made things worse.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: [Urgent please help] Failed to import applience
The error almost always means that there is insufficient space on the drive to be able to import the guest. I would check the free space and proceed accordingly.
-
Phoenix123
- Posts: 4
- Joined: 4. Oct 2015, 22:19
Re: [Urgent please help] Failed to import applience
Hi,Perryg wrote:The error almost always means that there is insufficient space on the drive to be able to import the guest. I would check the free space and proceed accordingly.
I've freed up an awful lot of space and now back to the original error message:
Machine settings file '/Users/Phoenix123/VirtualBox VMs/Oracle DB Developer VM/Oracle DB Developer VM.vbox' already exists.
Result Code:
VBOX_E_FILE_ERROR (0x80BB0004)
Component:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
I have just purchased this machine so there is not a lot on it at the moment. If I reset the computer back to factoty setting and wipe all the data on it. Would this fix what is happening as it would be like importing the file for the first time.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: [Urgent please help] Failed to import applience
The two errors don't meant the same thing. The error about it already being registered I answered and the one that the disk was full I also answered. Without diagnostic information there is little else I can tell you. Did you look in the media manager again and see if it shows anything? You should also search for the VirtualBox.xml file that controls this and after shutting VirtualBox down, rename or remove it and then start VirtualBox again.