Panic! Installed 4.1.8, Now Guest Machine Inacessable -Help?

[EvanAlaska]

The *.vbox file is in the same folder that has the *.vdi if you installed with version 4.* of VirtualBox

Hi Again

The program installed to C:\Program Files\Oracle\VirtualBox on my host.

I set up the guest .vdi to be on the F: drive and the .vdi file is at this path: F:\Vista 64 Pro Nov 2011, however there is no .vbox file in that folder.

[Perryg]

Then this guest must have been installed before 4.*.
Try your rollback then and see if that will get this back to work.

[EvanAlaska]

I'm really not sure what "*.vbox" file I should be looking for. I'm not seeing any ".vbox" file extensions in my directory (this is windows)...

All of my files in the C:\Program Files\Oracle\VirtualBox directory are dated no later than yesterday, and there are five subdirectories with today's date (nls, doc, drivers, sdk, accesible).

Given I can't find the file you are refering to, I don't see how I can edit it .

And rebooting the system didn't allow me to delete the .ISOs from the Virtual Media Manager, but like I said, they are not "attached" so I'm not sure that it's the crux of the problem...

I think I may need to try to roll back to ver 4.1.6...I'm running out of time and if I can't get to the work I saved there soon, I'm in big trouble...

[EvanAlaska]

Then this guest must have been installed before 4.*.
Try your rollback then and see if that will get this back to work.

Hi Again Perryg

I do appreciate your sticking with me through this.

The original install file I used to set up VirtualBox for the very first time was VirtualBox-4.1.6-74713-Win.exe, so the guest was not installed before 4.*

I searched my entire computer for *.vbox files, all drives, and found two of them in C:\Users\Praxis\VirtualBox VMs

Vista 64 Pro Nov 2011.vbox
Vista 64 Pro Nov 2011.vbox-prev

Both are time stamped when I did the upgrade.

What tool do I use to edit them?

[Perryg]

First backup the Vista 64 Pro Nov 2011.vbox
Then edit with notepad. Find and remove the line that has 53f9cc0c-e0fd-40a5-a404-a7a5272082cd, save and exit.
Then try to start the guest.

[EvanAlaska]

First backup the Vista 64 Pro Nov 2011.vbox
Then edit with notepad. Find and remove the line that has 53f9cc0c-e0fd-40a5-a404-a7a5272082cd, save and exit.
Then try to start the guest.

We are getting closer! Unfortunately I can't find that line in the file. There were four instances ending with "cd."

In case this helps, here is the error message attached to the guest machine:
Cannot attach medium 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' {c2fd9e07-e8fd-4bc3-bed0-d30156cc4b82}: medium is already associated with the current state of machine uuid {4025e5b1-3c03-497b-8fea-c0106eab6ebd}!.
Result Code:
VBOX_E_OBJECT_IN_USE (0x80BB000C)
Component:
Medium
Interface:
IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}

I can see that you got the code ^^^^ I am to search for just above this line, but perhaps I am to search for a different code?

I renamed the .vbox file to .xml so I could upload it here. Please see attached.

[Perryg]

remove these two lines save and try again Make sure that VirtualBox is not running when you edit and save!

Code: Select all

<Image uuid="{9f9bf362-5f57-4fa0-8cfd-b4021444e263}" location="F:/en_windows_vista_x64_dvd_X12-40712.iso"/>
        <Image uuid="{c2fd9e07-e8fd-4bc3-bed0-d30156cc4b82}" location="C:/Program Files/Oracle/VirtualBox/VBoxGuestAdditions.iso"/>

[EvanAlaska]

That worked!

I had to disable USB 2.0, because I'd tried removing Guest Additions, but I got my access back.

Thank you so much for your help!

Now I can start a new thread on my one remaining problem

[itai]

I got the same error message after installing version 4.1.8 . I have removed the Guest Extensions from the Preferences window, but the error persists. SHAME ON YOU ORACLE for releasing such a bug! What do i do now to restore my VM?

[Perryg]

I got the same error message after installing version 4.1.8 . I have removed the Guest Extensions from the Preferences window, but the error persists. SHAME ON YOU ORACLE for releasing such a bug! What do i do now to restore my VM?

Did you read the entire topic? There are several hints telling you what to look for and do.

[bcld]

I bet someone else will stumble on to this as I did. I had version 4.2.4-81684 on Max OS X and got the inaccessible error after messing around trying to add a qcow image from the VBoxManage command line utility. When I started virtualbox, all of my machines were "inaccessible." To fix it, I downgraded to 4.1.23, and was able to see the machines, but only one was inaccessible and there was an error that it could not recognize the qcow image. So I simply edited the machine's .vbox files to remove the qcow hard drive and then restarted. All of my virtual machines were accessible from there on out. I upgraded to 4.2.4-81684 again without problem.