It is the first time I use this forum and I am not sure to be in the good place. Also excuse me. Excuse too my bad english: I am french.
I expose my problem. I have two computers and on the both I use VirtualBox. On the number 1, I create one VM on Windows 7 (32-bit) that I can use without problem on the other computer, number 2. On number 2 computer I installed a version of Linux Ubuntu, and it works. But yesterday when I gone back home and used number 1, was this :
Runtime error opening 'V:\VirtualBox\VM Pierre Windows 7 (32-bit)
\VM Pierre Windows 7 (32-bit).vbox' for reading: -103 (path not found.).
And my VM Linux doesn't appear so ... Somebody could explain to me or help me to resolve this problem, because I prefer work on number 1, more powerfull ? Thank you very much.
Pibakou.
Last edited by Pibakou on 13. Jul 2017, 11:37, edited 1 time in total.
Virtualbox tried to open:
'V:\VirtualBox\VM Pierre Windows 7 (32-bit)\VM Pierre Windows 7 (32-bit).vbox'
and couldn't find the vbox file on that path.
Does the drive letter and series of folders and vbox file exist?
If VirtualBox says "path not found" then the path does not exist. I've never known VirtualBox to lie in an error message.
If I'm understanding the problem correctly then your .vbox file contains an absolute path, using Windows path syntax. Naturally this does not work on an Ubuntu host.
scottgus1 wrote:Please clarify your two physical computers' operating systems. Mpack is hot on the trail with the "Windows path on a Linux host" thought.
On rereading, I assume it's the front end which can't find a VM, rather than the VM which can't find a file. Virtually the same thing though, except that the path to a VM folder is always absolute. So, I'm guessing that the VirtualBox.xml file has been unnecessarily copied between dissimilar hosts.
As I read, both your hosts are Windows 10. On the host where the W7 guest isn't working and this "path not found" error happens, do you still have a V: drive?
If so, is there a folder in the V: drive called "Virtualbox"?
If so, in that "Virtualbox" folder is there another folder called "VM Pierre Windows 7 (32-bit)"?
If so, in that "VM Pierre Windows 7 (32-bit)" folder is there a file called "VM Pierre Windows 7 (32-bit).vbox"?
Note that your host may be set to hide known extensions, meaning that you may not see a file with the .vbox extension, even if it is there. Google for how to show all file extensions on Windows 10.
As I read, both your hosts are Windows 10. On the host where the W7 guest isn't working and this "path not found" error happens, do you still have a V: drive?
If so, is there a folder in the V: drive called "Virtualbox"?
If so, in that "Virtualbox" folder is there another folder called "VM Pierre Windows 7 (32-bit)"?
If so, in that "VM Pierre Windows 7 (32-bit)" folder is there a file called "VM Pierre Windows 7 (32-bit).vbox"?
Yes for all ...! Otherwise it would not work on number 2 ... And it did work previously, when I installed from number 1.
Pibakou wrote:Otherwise it would not work on number 2
Not true. As I stated earlier, just because a path exists on one PC doesn't mean it exists on another even if you copied it. It may have disappeared or a name could have been changed.
On the computer that has the error and where the guest won't open, open the folder window to the .vbox file. Open a command window and drag the .vbox file into the command window. The full path and name of the vbox file will appear in the command window. Take a screenshot of that command window and post it here as an attachment using the Upload Attachment tab below the textbox where you type new posts. I want to see what the computer thinks the path to the vbox file is.
Which takes us back to the first post. I await with interest the proof (not a mere assertion) that the path "V:\VirtualBox\VM Pierre Windows 7 (32-bit)" actually exists, on the machine which is displaying the error.
