VB Manager GUI "move" machine command
|Reported by:||Andreas S||Owned by:||gombara|
|Guest type:||all||Host type:||Windows|
use VB on my laptop and have numerous machines for projects with engneering software. I want to keep only the current project VM on my laptop SSD (for speed and disc space reasons) and keep the other ones accessible on an external USB drive . So I attach 5TB external HD to the laptop and create a "machines" folder.
I use the "move" command in the GUI (right-click on the VM) and can select slect basically any drive and folder and pont it to my external HD machine folder.
However the results are mixed and the feature is not working.
A folder for the machine is created but only the VM vbox file and the log folder is moved to the destination. The VDI and snapshot folder remain on Original location :cry:
If I move the VM on the same internal HD drive letter to another location it seems to work better and shifts also the VDI and snapshots.
Background why I need the move feature: My problem is that I want to shift a VM (with it's VDI) which all reside in a folder (.vbox, .VDI, the Snapshot and log subfolders) and move it to another location either on my laptop or to an external HD over the network to a library (NAS). Reason behind it is that I work with many VM and I can't have all of them in my laptops SSD at the same time. I wanted to use the "move" feature from the VB GUI to move a complete VM (including its VDI, snapshots) to an external hard drive and keep those VM that I don't need immediately or only for a quick test on another drive (HDD) and easily move them between my internal SSD and an external drive. The GUI behaves inconsistent when it comes to applying the command on the same (internal) drive or on an external USB drive or a network drive. It doesn't make sense to use the "move" command when it only moves the VM definition and leaves the VDI in the old location or even worse when it only partially moves the files leaving some in the old location and some in then new location. What I figured out is that apparently due to the way the move is implemented in the GUI it works (almost(!!) all the time) within the local drive because only the path informations needs to be updatted on the hard drive file system and files are not physically moved (copied and then deleted from old location). By selecting an external drive for the move command it works "partially" but mostly some files are not properly moved.