Clone a Virtual Machine in VirtualBox

SHARE & COMMENTShare on Facebook0Tweet about this on Twitter0Share on Google+0Share on LinkedIn0

In this post, I will show us how to clone a Windows Server 2008 R2 Virtual Machine using VirtualBox. The version of VirtualBox I am working with is v4.2.10.

Steps:

- Launch the Oracle VM VirtualBox Manager

VirtualBox Clone

- Right-Click on the VM you intend to clone and click Clone…

VirtualBox Clone

- Enter a new name for the clone VM and check the box “Reinitialize the MAC address for all network cards“. Note checking this box will generate new mac address for the clone VM to avoid duplicate.

VirtualBox Clone

- Select Full clone for Clone Type

VirtualBox Clone

- Click Clone for the cloning process to begin

VirtualBox Clone

Note: The system will create a new folder and .vdi file for the new clone VM in same location as the original VM you cloned.

- After cloning is completed, the new VM should now appear in list of VMs

VirtualBox Clone

Post Installation:

- When the original VM and the cloned VM both have virtual hard drives that have the same “hard drive UUID”, this may cause problems due to duplicate UUID. To validate this, simply navigate to the following location “<user profile folder>\.VirtualBox”, locate and open the file “VirtualBox.xml”. Locate entries in <MachineRegistry> as seen below and ensure each <MachineEntry uuid=” are not same per VMs

<MachineRegistry>
<MachineEntry uuid=”{xxxxxx-xxxx-xxxxx-xxxx-7f51dd7d899d}” src=”G:\Virtual Machines\SYS01DC01\SYS01DC01.vbox”/>
<MachineEntry uuid=”{xxxxxx-xxxx-xxxxx-xxxx-61795783c32c}” src=”G:\Virtual Machines\MAC OS Machine\MAC OS Machine.vbox”/>
<MachineEntry uuid=”{xxxxxx-xxxx-xxxxx-xxxx-59ry23bbc117}” src=”G:\Virtual Machines\SYS01SVR01\SYS01SVR01.vbox”/>
</MachineRegistry>

- Sysprep the OS of the newly cloned VM to avoid duplicate SID in Active Directory. Remember you will need to join the new cloned VM to the domain with a new hostname

SHARE & COMMENTShare on Facebook0Tweet about this on Twitter0Share on Google+0Share on LinkedIn0
Tagged with 
0 comments