virtualbox.org

Runtime error opening '/Users/xxxx/VirtualBox VMs/WIN7EN/WIN7EN.vbox' for reading: -102(File not found.).
/Users/vbox/tinderbox/5.0-mac-rel/src/VBox/Main/src-server/MachineImpl.cpp[740] (nsresult Machine::i_registeredInit()).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}


I looked and to the best of my knowledge the file is still where it's supposed to be, is there another solution for this?

For what it's worth I have another Windows 7 guest and it's working perfectly fine, they look like they have the same contents in the VirtualBox VMs folder.

Open up Terminal and post the output of the following:

   ls -alR /Users/xxxx/VirtualBox VMs/WIN7EN/

Oh, and by the way, you don't really have to use xxxx. Nobody is going to hack you based on you revealing your username.

socratis wrote:Open up Terminal and post the output of the following:

   ls -alR /Users/xxxx/VirtualBox VMs/WIN7EN/

Oh, and by the way, you don't really have to use xxxx. Nobody is going to hack you based on you revealing your username.

I'm doing this for a friend so was more for his privacy.

Alright I tried the command for the working and non-working guests, I'm getting no such file or directory for all of them.

Of course it won't work! I made a mistake while issuing the command; didn't think about the space between "VirtualBox" and "VMs". Try the following:

   ls -alR "/Users/xxxx/VirtualBox VMs/WIN7EN/"

Notice the quotes at the beginning and end of the path. If that doesn't work, try:

   ls -alR "/Users/xxxx/VirtualBox VMs/"

and if that doesn't work, try:

   ls -alR /Users/xxxx/VirtualBox*

Notice the absence of quotes in the last one.

It worked. Logs, pineapple, and snapshots showed up.

Even I should've realized the need for quotes

jnuey wrote:I looked and to the best of my knowledge the file is still where it's supposed to be

Actually, no, it is not!

Something is not right over here. Your files are not in their default directories. The contents of the "WIN7EN/WIN7", i.e. "WIN7EN.vbox", "WIN7EN.vbox-prev" and "WIN7EN.vdi" should really be one level up, in the "WIN7EN" directory. Did you move them manually? What's the story here? How did this happen? For sure it wasn't VBox that did it on its own.

<humor>
BTW, you can now stop editing out the username... You forgot to obfuscate the terminal window title Tell A.G. to change his password, his ID and to move to another (undisclosed) location! A face transplant wouldn't be such a bad idea either. They're after him...
</humor>

I had no idea that was from Ashton's Mac until socratis gave his name away by including his initials. "A.G."

doh. lol.

I copied the files a directory up like you said, thanks for the help not sure what happened there!

jnuey wrote:I copied the files a directory up

In that case, I would erase the 3 files in the "WIN7EM/WIN7" directory, unless you want an extra 98,202,314,799 bytes occupying space on your hard drive. You should have moved those 3 files, not copy them...

Right I just copied them first to make sure it worked