Resolves a method that VirtualBox virtual software creates that cannot be planned after VDI moves

Occasionally to use other systems, such as the old Windows XP, Linux, you need to use the virtual machine software, generally I will choose VirtualBox, because free ... VMware's very good, but you know--paid software.

Recently in the file to defragment the hard drive, move an XP VDI file to another location, and then inside the VIRTUALBOX hint that the UUID already exists.

G a bit, the original is: VirtualBox and VMware are different, not as VMware as direct replication of virtual disk files can be, because the VirtualBox recognition virtual disk file VDI uses the UUID recognition technology.

The workaround should be to reassign the UUID, but the UI interface does not find such an option, and G a bit, you can use the command:

1. Command window go to VirtualBox directory, like my

D:

CD Win_programvirtualbox

2. Reassign the UUID command

Vboxmanage internalcommands sethduuid Mirrored file path

Note: "Mirrored file path" if the directory contains spaces, use double quotes in English

If you are copying, use the VirtualBox Clone feature, which assigns a new UUID to the newly replicated VDI file, as follows:

Vboxmanage CLONEVDI Original VDI File New VDI file

Similarly: "Mirrored file path" if the directory has spaces, use double quotes in English

Also, the original hard drive image is to be released and deleted from the virtual Media Manager, or an error will be given.