But whatever I try to do, VirtualBox fails to run new (moved) VM... When I boot to the old HD I can still run VM just fine.
1. I exported it as .OVA file and imported it in new location. When I try to run it, I'm getting error:
Code: Select all
Failed to open a session for the virtual machine W7-05.
A new node couldn't be inserted because one with the same name exists. (VERR_CFGM_NODE_EXISTS).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
How to reset VirtualBox to get rid of this error?
2. I tried to copy the whole folder of VM from HD to its new location in SSD. But how can I register it with new VirtualBox setup? Is it any way to make it configured and running in new VB setup?
3. I tried to make a new VM for the same OS (W7) and point its storage to the copied .VDI file. VirtualBox fails to run it too...
Whatever I do, VB fails to run the old machine that I can still run well from the old setup. I presume moving VM is a common task for many users and should not be so difficult...
Just in case: Old HD setup - VB v5.0.2. New SSD setup - VB v5.2.8. Both are in W7 OS.