I copied my entire folder containing a VM to another drive (C:\ to E:\)
I then removed the VM from the VM manager (I did not delete the files on the C:\ drive in case of a failure)
I then tried to add the .vbox file on the E: drive via the manager. I get the following error message.
My question is why the virtual machine files are referencing anything on the C:\ drive?
Is there any way possible to move a VM - INCLUDING THE SNAPSHOT's) to another hard drive on the same system (or to another computer for that matter).
If there is any solution at all, please let me know. I need to clear up space on my C:\ drive. If I loose the snapshots, I loose about six months of work.
I just want an existing VM on the C:\ drive that has many snapshots moved to the E:\ drive and be able to run as before as I did on the E:\ drive.
If this is not possible, I just need to know simply "VirtualBox does not have this capability".
--- VirtualBox - Error (after copying VM files to another Drive)
Failed to open virtual machine located in E:/<path>/<machine_name>/<machine_name>.vbox.
Cannot register the hard disk 'E:\<path>\<machine_name>\Snapshots/{0ece4bff-9185-4cff-9069-b3d1f4536394}.vdi' {0ece4bff-9185-4cff-9069-b3d1f4536394}
because a hard disk 'C:\<path>\<machine_name>\Snapshots/{0ece4bff-9185-4cff-9069-b3d1f4536394}.vdi' with UUID {0ece4bff-9185-4cff-9069-b3d1f4536394} already exists.
Result Code: E_INVALIDARG (0x80070057)
Component: VirtualBox
Interface: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}
---
One question is how does the VM Manager know about the C:\<path>\<machine_name>.vdi file even after removing from the VM Manager? I deleted it.
Where is the metadata kept that the VM Manager reads? Can I open the metadata file and delete the reference to the VM on the C:\ drive from this metadata?
Error message after copying virtual box files
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Error message after copying virtual box files
You already have at least three other threads discussing essentially this same subject, I believe that is more then enough. Please continue here.
Locking this one.
Locking this one.