Oracle virtual box unavailable

Question

I am using Oracle Virtual Box version 4.2.16 r86992. Everything was fine until yesterday's close. Today it shows inaccessible and causes this error:

Runtime error opening C:\Users\xxxxxx\VirtualBox VMs\vBoxxxxXubuntu_Beta\vBoxxxxXubuntu_Beta.vbox for reading: -102 (File not found.). D:\tinderbox\win-4.2\src\VBox\Main\src-server\MachineImpl.cpp[725] (long __cdecl Machine::registeredInit(void)). 

It’s good to restore it to work, it will save a lot of time and restore settings and configuration data. Thank you for your support.

Answer 1

This usually happens if the host OS fails or you pull the plug-in on it, leaving the .vbox file unsaved.

In place:

 C:\Users\xxxxxxx\VirtualBox VMs\vBoxxxxXubuntu_Beta\ 

you should find two files:

• vBoxxxxXubuntu_Beta.vbox-prev
• vBoxxxxXubuntu_Beta.vbox-tmp

Copy vBoxxxxXubuntu_Beta.vbox-prev to vBoxxxxXubuntu_Beta.vbox .

Select vBoxxxxXubuntu_Beta.vbox , in the VBox manager, right-click and then left-click on the update.

Notice that it now shows power cut off.

Now you are good to go.

Answer 2

Based on my experience, I was on Windows 7 and running Ubuntu 14.04 as a guest OS on a virtual machine.

• Go to the Virtualbox folder (in my case): C:\Users\Dev12\VirtualBox VMs\Ubuntu
• You will see files with extensions: Ubuntu.vbox-tmp or Ubuntu.vbox-prev
• Remove -tmp from the Ubuntu.vbox-tmp file Ubuntu.vbox-tmp so that it Ubuntu.vbox as Ubuntu.vbox
• Exit the virtual machine and start it again.
• You should now see that the error has disappeared.

Answer 3

Virtual box files with the extension .vbox contain metadata that the virtual unit hypervisor requires configuration permission for the guest virtual OS.

If the main .vbox file is damaged (i.e. reports that it is empty), use the .vbox-prev backup file to restore the contents of the original file.

Do this by renaming the empty .vbox files to a temporary name (for example, rename originalVM.vbox to the original VM-empty.vbox) .

Then create a copy of the backup file originalVM.vbox-prev, where the copy will have the same name as the original, but with the word "copy" added to it (that is, originalVM.vbox -prev is renamed to originalVM (copy) .vbox- prev).

It is important to keep the original .vbox-prev backup file, it should not be changed or renamed.

Now go to rename the copy of the newly created .vbox-prev file originalVM (copy) .vbox-prev to the original name of the empty .vbox file and remember to also change its extension from .vbox-prev back to .vbox.

This rename originalVM (copy) .vbox-prev back to the original VM.vbox. Now that this is done, you can add the .vbox (guest os) file back to the VBOX hypervisor .
This will restore the state and snapshot of the "inaccessible" guest virtual machine. Now delete the original empty .vbox file.

Answer 4

The version of VirtualBox 4.3 has been released and it may be that you updated or encountered some problems during the update?

In any case, if you cannot open Virtualbox, be sure to back up the VM ViritalBox folder, and switching to a new installation should be the best way forward.

Answer 5

I had the same problem and solved it by doing the following in Oracle Virtual box 4.3.28 with Ubuntu 14.04 LTS when the virtual virtual machine was shut down.

• Removed ubuntu.vbox to another folder outside the virtual window folder

• removed -prev from ubuntu.vbox-prev file

• Launch oracle virtualbox, it works fine.

Answer 6

Another problem may be that if your virtual machine was on an external hard drive, it is possible that the drive letter has changed. If so, go to Computer Management and select the hard drive and right-click to change the drive letter and save (note that this is for Windows).

Answer 7

I ran into the same issue using CentOs 6.8 on VirtualBox 5.1 installed on Windows 7 and the AjayKumarBasuthkar solution worked fine for me:

• I went to C: \ Users \\ VirtualBox VMs \ CentOS6.8
• I made a copy of the CentOS6.8.vbox-prev file and named it CentOS6.8.vbox
• I went to the VirtualBox GUI, right-clicked the virtual machine instance and clicked update
• The CentOS instance has transitioned from a state inaccessible to a disconnected one.

Answer 8

On a Windows 7 host, I found that the Daemon Tools service is holding a file.

The solution was to remove Daemon Tools, but I suspect that if you stop the service and remove the file association, you will be sorted.