Opened 13 years ago
Last modified 13 years ago
#8070 new enhancement
Less reliance on absolute paths in VirtualBox
| Reported by: | mark_orion | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.0.0 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Linux |
Description
VirtualBox should be able to work with relative paths properly. Example: The virtualdisk was created under /home/user/.VirtualBox/VDI/mydisk.vdi For ease of use I have symlinked /home/user/VirtualBox to /home/user/.VirtualBox, but whenever I try to work with diskimages through the symlink (/home/user/VirtualBox) I am getting errors of already registered diskimages under the hidden .VirtualBox directory.
Note:
See TracTickets
for help on using tickets.
I concur. I'd very much like to be able to use VMs created in Windows in Linux and vice versa. Right now I got it to work using an ugly hack that involves symlinking my Windows D: (where my VM folder is) to C:\media\d and creating all my VMs in Linux, but I'd very much like to be able to do this correctly, including for VMs created in Windows.
This should be very trivial: the .vbox file is always located in the same directory as the Snapshots folder (so no worries there), and the virtual disk(s) itself/themselves could simply be referred to as e.g. "../../Disks/VirtualDisk.vdi". It should be relatively (no pun intended) easy to add relative paths as an experimental feature, shouldn't it?