Isso é muito bonito ao mover o VDI para o outro sistema, mas há mais algumas coisas a serem consideradas se você não quiser reativar o Windows 7. Consulte as informações a seguir, conforme observado no Fóruns de usuários para o VirtualBox
Q: I want to move my VM to a different host, how do I do that?
Q: I want to share my VM with my dual-boot, how do I do that?
A: The VDI need to be on a shared location so both OSses can read and write to the file in case you want to share it between your dual-boot Host.
Você pode ignorar o local compartilhado, já que está fazendo uma mudança.
Create a new VM on the other system, select the VDI from the first Host as hard drive instead of creating a new one and make sure that every setting is exactly the same. The MAC addresses of the virtual NICs also need to be the same, to avoid possible Windows activation prompts and new interface names on Linux.
For Windows 7, there is one additional step that needs to be the done to avoid reactivation. The VM UUID need to be transferred from the original VM to the new one. Open the XML file of the original VM and copy the UUID and transfer that to the new VM XML file. Look for this line at the start of the file:
Machine uuid="{075d42da-6025-4a95-a1d5-57b1f4b09dd7}" name="Windows 7" OSType="Windows7"
The 'hash' in curly brackets is the UUID you need to copy and replace in the new VM XML. This change is not yet done, because the VirtualBox.xml file doesn't know that UUID, it still holds the old UUID of the VM. Open the VirtualBox.xml file in a text editor like with the machine.xml file and look at a line that looks like the following and replace the UUID.
<MachineEntry uuid="{075d42da-6025-4a95-a1d5-57b1f4b09dd7}" src="/media/Extern/Virtual Machines/Windows 7/Windows 7.xml"/>
The src= line is how you can spot your VM. The actual location of the XML depends on the Host and configuration of the VM location. By default it's in the user profile folder.