Why is VirtualBox so stupid ?

[rabol]

Hi

I know... VirtualBox is NOT stupid, I'm stupid

Problem: I have a Windows 2008 Server VM, where the .VHD files where stored on my NAS (Synology), it worked perfectly, until the HD in the NAS 'crashed'
I had a copy of the .VHD files on my Mac Mini server, so I thought: Just copy the .VHD files to my local /usename/VirtualBox VMs/VM_Name/ folder, attach the .VHD files and off we go, but....

When I try to attach the .VHD file, I get the following error:

Failed to open the hard disk /Users/XXX/VirtualBox VMs/AX2012Image/AX2012-A.vhd.

Cannot register the hard disk '/Users/XXX/VirtualBox VMs/AX2012Image/AX2012-A.vhd' {fc63083a-35fd-4181-a66f-ebe551f5215c} because a hard disk '/Volumes/public/AX2012/AX2012-A/Virtual Hard Disks/AX2012-A.vhd' with UUID {fc63083a-35fd-4181-a66f-ebe551f5215c} already exists.

Result Code: NS_ERROR_INVALID_ARG (0x80070057)
Component: VirtualBox
Interface: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}


And that's my point: Why do I get the error

Kind regards
Steen

[Perryg]

You can't add it because you already have one registered with the same name or UUID.
You would need to remove the old one first or try using a different name.

[rabol]

You can't add it because you already have one registered with the same name or UUID.
You would need to remove the old one first or try using a different name.

Yes, I just found out that I can use the virtual media manager to remove the .VHD, but...
If I remove a .VHD file from a VM, it should automaticlly remove it from the virtual media manager - or at least ask to remove - since it is no longer in use AND why can I not use a 2nd copy of the same .VHD for a 2nd VM (E.g I could make a 'base installation' and then use it in several VM's) ?

[Perryg]

Not really. it all depends on how you remove it. you could select to remove and not delete. Older versions of VBox were built different and to keep things downward compatible some things could not be changed.

You can edit the control files but really it is easier to just remove and add it back.

[Noquierospam1]

Yes! it is incredible stupid!

This is an incredible common use case for me:

1. create virtual machine. use it. create snapshots
2. move it to another system or replace mount point, etc.

All i want to do is move my files!!!! i don't want to go changing my VM. this is idiotic

And the solution is NOT to go changing UUIDs because that is silly and i bet it will ruin snapshots.

Why you can't simply click settings, go to storage, click the existing drive, click locate it and be done? this would be the only thing that would make sense. Actually... relative paths for the disks would make even more sense, but i'd take even the least optimum solution.

the only sane solution:

edit the .vbox file, and manually change the path for the disk. done.

[mpack]

Howto: Moving a VM.