"File Not Found" error after installing VBox 3.2.6

[donls]

After I upgraded from 3.2.4 to 3.2.6, all my VMs became inaccessible, with messages like:

Code: Select all

Runtime error opening '/Volumes/UsersPlus/VirtualBox/Machines/JauntyJackalope904/JauntyJackalope904.xml' for reading: -102 (File not found.).

/Users/vbox/tinderbox/3.2-mac-rel/src/VBox/Main/MachineImpl.cpp[665] (nsresult Machine::registeredInit()).
Result Code:  NS_ERROR_FAILURE (0x80004005)
Component:  VirtualBox
Interface:     IVirtualBox {3f36e024-7fed-4f20-a02c-9158a82b44e6}

Also, when I look at the VDI file used by the VM (with Virtual Media Manager), I get:

Code: Select all

Could not open the medium '/Volumes/UsersPlus/VirtualBox/VDI/JauntyJackalope904.vdi'. VD: error VERR_FILE_NOT_FOUND opening image file '/Volumes/UsersPlus/VirtualBox/VDI/JauntyJackalope904.vdi' (VERR_FILE_NOT_FOUND)

The files have not been moved, and when follow the paths, I see the files where they always have been.

I removed a couple of the vdi files from the Virtual Media Manager listing and pointed to the same locations, and the files are shown as present now. However, I don't know how to re-enable the xml files, and some of the disk configurations would not let me remove the vdi.

Code: Select all

Failed to close the hard disk
/Volumes/UsersPlus/VirtualBox/VDI/CentOS54Test.vdi.

Cannot close medium
'/Volumes/UsersPlus/VirtualBox/VDI/CentOS54Test.vdi' because it has 1 child hard disk(s).

Details:
Result Code:     NS_ERROR_FAILURE (0x80004005)
Component:     Medium
Interface:     IMedium {1d578f43-5ef1-4415-b556-7592d3ccdc8f}

I tried removing 3.2.6 and re-installing 3.2.4, and I see no difference.

Since I was able to make some vdi files available by removing them with Virtual Media Manager and locating them again, I tried removing a machine and creating a new one using the newly-located vdi, however I got this message:

Code: Select all

Failed to create a new virtual machine KoalaFromJaunty.

Could not create a directory
'/Volumes/UsersPlus/VirtualBox/Machines/KoalaFromJaunty' to save the settings file (VERR_ACCESS_DENIED).

Details:
Result Code:     NS_ERROR_FAILURE (0x80004005)
Component:     Machine
Interface:        IMachine {6d9212cb-a5c0-48b7-bbc1-3fa2ba2ee6d2}
Callee:            IVirtualBox {3f36e024-7fed-4f20-a02c-9158a82b44e6}

I checked permissions on the Machines directory, and I have r/w access. Group and others are read-only.

It seems like this should be something really simple, but I'm not seeing it.

[donls]

Well, I found out what happened...

I started one of my VM tools (VBox, Parallels, or VMWare) when the external HD was not connected. At that time, all storage SHOULD indicate unavailable, unless an item is on the internal drive. Then I attempted to access or create a VM that should have been on the external HD. A subdirectory was created whose name matches the volume name of the external HD. All further attempts to access the external HD would go to the permanent subdirectory until it was removed.

I don't know which operation aggravated this situation, but I do have internal VMs in Parallels, and VMWare allows me to open a VM on the external drive directly, which creates a new registry entry for the one newly opened, in addition to the one that couldn't be found.

Thanks for giving me a place to vent and share this info. Maybe it will help someone else?