Opened 13 years ago
Closed 8 years ago
#9662 closed defect (fixed)
changing vm name prevents boot
Reported by: | Owned by: | ||
---|---|---|---|
Component: | virtual disk | Version: | VirtualBox 4.1.2 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Mac OS X |
Description (last modified by )
I renamed my VM after creating the virtual drive and the location of the virtual drive changed because the base directory for the VM changed, but the file path which was stored in the configuration was not changed. this cause the vm to fail to boot because it could not open the virtual drive. the VM was also a clone. I got my vm running by creating a soft link to the new directory using the name of the old directory. here is the error text:
Failed to open a session for the virtual machine My xp vm. Could not open the medium '/Users/daviddelikat/VirtualBox VMs/xp vm Clone/Snapshots/{459e5792-c7f9-4e36-b1a9-e987ab50ff82}.vdi'. VD: error VERR_FILE_NOT_FOUND opening image file '/Users/daviddelikat/VirtualBox VMs/xp vm Clone/Snapshots/{459e5792-c7f9-4e36-b1a9-e987ab50ff82}.vdi' (VERR_FILE_NOT_FOUND). Result Code: NS_ERROR_FAILURE (0x80004005) Component: Medium Interface: IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
I fixed the problem by creating a soft link 'xp vm Clone' to the correct directory.
Change History (1)
comment:1 by , 8 years ago
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Likely fixed long ago, please reopen if still relevant with a recent VirtualBox release.