I found a totally cool gem today.
We found the following command on the website http://forums.virtualbox.org/viewtopic.php?p=33678.
Scenario: when cloning a VDI (virtual box image) image you may want to use that VDI image as the base for an additional image
Symptoms: A hard disk with UUID {23a663ea-a1a1-a2ea-9a34-1368b30ea813} or with the same properties ('D:\VBOX\VDI\XP_Work_Template_20GB.vmdk') is already registered.
Example:
You have an image with MYAPP 1.02.
Now you want an image with MYAPP 1.03 but you still want to keep your copy of 1.02.
You now will have a problem with mounting both images on the same box since they both have the same UUID. To resolve this issue run the following from the command line.
In our case we had to first navigate to C:\program files\sun\virtual box\ then we ran it. Replace mydisk.vdi with the full path to your actual vdi file you need a UUID for.
c:\>VBoxManage internalcommands setvdiuuid mydisk.vdi
We found the following command on the website http://forums.virtualbox.org/viewtopic.php?p=33678.
Scenario: when cloning a VDI (virtual box image) image you may want to use that VDI image as the base for an additional image
Symptoms: A hard disk with UUID {23a663ea-a1a1-a2ea-9a34-1368b30ea813} or with the same properties ('D:\VBOX\VDI\XP_Work_Template_20GB.vmdk') is already registered.
Example:
You have an image with MYAPP 1.02.
Now you want an image with MYAPP 1.03 but you still want to keep your copy of 1.02.
You now will have a problem with mounting both images on the same box since they both have the same UUID. To resolve this issue run the following from the command line.
In our case we had to first navigate to C:\program files\sun\virtual box\ then we ran it. Replace mydisk.vdi with the full path to your actual vdi file you need a UUID for.
c:\>VBoxManage internalcommands setvdiuuid mydisk.vdi
Comments