Inaccessible VM after update to 4.1.10

Discussions related to using VirtualBox on Windows hosts.
Locked
yug
Posts: 44
Joined: 18. Aug 2011, 20:08
Primary OS: Fedora other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: fedora
Location: California

Inaccessible VM after update to 4.1.10

Post by yug »

This is very frustrating!
I upgraded to 4.1.10, booted the VM and received a message about old guest additions. For the first time ever, instead of mounting the iso from within the VM OS I used the "install guest additions" options in the mini menu bar. This failed with "Cannot attach medium 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso" so I just mounted the iso and ran the script as I normally do. Now after installing guest additions and building kernel modules I shut down normally. Today I start VBox and the machine is inaccessible!

Cannot attach medium 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' {d6c41d7d-3727-4845-9aad-d89f671f7dc7}: medium is already associated with the current state of machine uuid {a2844f20-fc58-4d8b-8d01-d25a0358c487}!.
Result Code:
VBOX_E_OBJECT_IN_USE (0x80BB000C)
Component:
Medium
Interface:
IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
stefan.becker
Volunteer
Posts: 7639
Joined: 7. Jun 2007, 21:53

Re: Inaccessible VM after update to 4.1.10

Post by stefan.becker »

Try unregistering the ISO in the VBOX GUI.
yug
Posts: 44
Joined: 18. Aug 2011, 20:08
Primary OS: Fedora other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: fedora
Location: California

Re: Inaccessible VM after update to 4.1.10

Post by yug »

stefan.becker wrote:Try unregistering the ISO in the VBOX GUI.
I'm not clear on what you mean. The GUI for the VM is inaccessible, there are no settings available only an error message.

I feel that I should be able to manually edit the *.vbox file or whatever stores the settings but I don't want to make things worse.
yug
Posts: 44
Joined: 18. Aug 2011, 20:08
Primary OS: Fedora other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: fedora
Location: California

Re: Inaccessible VM after update to 4.1.10 {SOLVED}

Post by yug »

I opened the associated *.vbox file in windows notepad and deleted all references to the "attached device" then I copied the file to *.vbox-prev. I'm writing this post from the VM (fedora 16).

I think there is a problem with whatever script is invoked by "Install Guest Additions" in the Devices Menu. It failed to mount the ISO and even gave an error but after shutting down the VM something is thinking it is still mounted even though it never was. It sucks that such a little thing could really screw you up.

I guess it's time I make back up copies of all my VMs.
BLACKHAWK
Posts: 1
Joined: 11. Sep 2012, 13:59

Re: Inaccessible VM after update to 4.1.10

Post by BLACKHAWK »

Steps followed to resolve the issue.

1) Stop Oracle VM VirtualBox Manager
2) Open REAL1.vbox file in notepad
3) Search for VBoxGuestAdditions.iso in the file
4) Remove the line which corresponds which has the entry VBoxGuestAdditions.iso. (Remove the complete line)
eg:-
<Image uuid="{0d0c7dc1-eee4-4f78-942c-7b62c4da37af}" location="C:/Program Files/Oracle/VirtualBox/VBoxGuestAdditions.iso"/>
5) Start the Oracle VM VirtualBox Manager the VM machine should be available for startup.
Freddie
Posts: 1
Joined: 17. Aug 2014, 07:54

Re: Inaccessible VM after update to 4.1.10

Post by Freddie »

Where can I find the REAL1.vbox file? I have the same issue. I'm running Solaris 11.2 on Oracle VM downloaded from the Oracle site and the VM works fine but when I power it off and save machine state, it simply becomes inaccessible with the same exact error message.
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: Inaccessible VM after update to 4.1.10

Post by mpack »

Don't hijack threads (I suspect you are not using 4.1.10), especially old, dead ones. Start a new topic and describe your problem properly.
Locked