Could not open the medium

[allisbs]

Could not open the medium '/Volumes/Virtual Boxs 1/Windows 10.vdi'.
VD: error VERR_FILE_NOT_FOUND opening image file '/Volumes/Virtual Boxs 1/Windows 10.vdi' (VERR_FILE_NOT_FOUND).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}

My virtual box (WIndows 10) was working just fine yesterday. Hooked up my external drive today and tried to load Windows 10 and get the above error.

/Volumes/Virtual Boxs 1/Windows 10.vdi
is not the location. It is located at /Volumes/Virtual Boxs/Windows 10.vdi
I have not messed with anything. Don't understand why it changed and won't load.

[andyp73]

Hooked up my external drive today and tried to load Windows 10 and get the above error.

Running guests from an external drive isn't really recommended. Even with a USB3 drive the throughput may not be good enough for a pleasant user experience.

VD: error VERR_FILE_NOT_FOUND opening image file '/Volumes/Virtual Boxs 1/Windows 10.vdi' (VERR_FILE_NOT_FOUND).

You could always go into the settings for the guest, delete the drive and then attach the .vdi file again from the correct location.

-Andy.

[socratis]

Hooked up my external drive

/Volumes/Virtual Boxs 1/Windows 10.vdi is not the location. It is located at /Volumes/Virtual Boxs/Windows 10.vdi

When you connect an ext. hard drive, and you already have a hard drive connected with the same name, the host OS will assign a new name. In your case, you must have had an existing mounted volume at "/Volumes/Virtual Boxs" and when you attached the HD, the host OS gave it a new attachment point "/Volumes/Virtual Boxs 1". Eject all the mounted volumes and try again.

BTW, this wouldn't have been necessary if the VM definition (.vbox file) and the VDIs were all in the same folder. But somehow you've managed to separate them...