VMware ESXi and vSphere Cluster Management

How to Clone a Virtual Machine in Oracle VirtualBox

Learn how to clone a VirtualBox VM, choose full or linked clones, handle MAC addresses, verify the copy, and avoid network and storage problems.

What Is Virtual Machine Cloning?

A virtual machine (VM) is a software-defined computer that runs a guest operating system on a physical host system. Oracle VirtualBox is software for creating and managing these VMs.

Cloning creates a separate VM from an existing source VM. The newly created clone VM has its own VirtualBox configuration and, for a full clone, its own copied virtual disks. After cloning is complete, changes made inside the clone do not change the source VM.

Why Clone a VM?

  • Test changes safely: apply a risky update or configuration change to the clone while preserving the original.
  • Preserve a known-good state: keep a working baseline available as a rollback point.
  • Create a backup-like duplicate: make an independent copy that can be started or moved separately, especially with a full clone.
  • Prepare repeatable lab machines: create several training or development systems from one prepared baseline.

Prepare the Source VM

  1. Identify the source carefully. Confirm the VM name, guest operating system, disk contents, and purpose before starting the wizard.
  2. Shut down the guest cleanly. A normal guest shutdown gives VirtualBox a consistent disk state. Some VirtualBox versions and VM states allow additional cloning choices, but a powered-off VM is the safest starting point.
  3. Check host storage. A full clone may need space comparable to the source virtual disks, plus configuration files and any retained snapshot data.
  4. Review snapshots. A snapshot preserves a VM state and may create associated differencing disks. Decide whether the clone needs only the current state or the snapshot history.
  5. Review attached resources. Check virtual disks, optical media, shared folders, USB filters, network adapters, and any files stored outside the VM folder.
  6. Check identity-sensitive software. Operating-system activation, licenses, endpoint-management agents, certificates, and application registrations may require reactivation or identity changes in the clone.

Open the Clone Workflow in VirtualBox Manager

  1. Open VirtualBox Manager and select the intended source VM.
  2. Open the VM's context menu and choose the clone action, or use the applicable machine menu in your VirtualBox release.
  3. Confirm that the selected VM is the source. The wizard will create a new destination VM from it.

The exact labels can vary between VirtualBox releases, but the workflow normally asks for a destination name, location, clone type, snapshot handling, and network identity options.

Name and Place the Clone

Give the destination a unique, descriptive name. Avoid names that could be confused with the source in scripts, backups, or VirtualBox Manager.

Useful naming patterns include:

  • dev-app-baseline for a known-good development machine
  • dev-app-update-test for a temporary update test
  • lab-linux-student-03 for a training machine
  • win-test-2026-08-18 for a dated copy
  • production-baseline for a carefully preserved reference VM

When VirtualBox offers a destination folder, select a host location with enough capacity and appropriate backup or access policies. A separate volume can make storage planning and cleanup easier.

Choose MAC Address Handling

Every virtual network adapter has a MAC address, a hardware-style identifier used by Ethernet networking and many virtual network configurations. A cloned adapter can either receive a new MAC address or retain the source identity, depending on the cloning choice and VirtualBox version.

Reinitializing the MAC address means generating a fresh MAC address for the clone's virtual adapters. Enable this option when the source and clone might be powered on or connected to the same network.

Duplicate MAC addresses can cause network conflicts, unpredictable connectivity, confused DHCP leases, and problems identifying the correct machine in monitoring or access-control systems. A new MAC address does not by itself solve duplicate hostnames, static IP addresses, DHCP reservations, or operating-system machine identifiers.

Keeping the original MAC can be intentional for an offline archival copy or a controlled environment that requires identity preservation. Do not connect such a copy to the same network as the source at the same time.

Situation — Recommended MAC address choice — Reason

Source and clone may run on the same network — Generate a new MAC address — Prevent adapter identity conflicts and DHCP confusion.

Offline archival copy — Retaining the original may be acceptable — The copy is not participating in live network communication.

Isolated temporary test machine — Normally generate a new MAC address — Isolation reduces exposure, but a unique identity is still safer if networking is later enabled.

Software or network setup tied to a fixed MAC address — Retain it only when required and prevent simultaneous network use — A fixed identity may be part of licensing or network policy.

Choose a Full Clone or Linked Clone

A full clone copies the virtual disks and creates an independent VM. A linked clone uses a base VM or snapshot and stores only the changes made by the clone. The installed VirtualBox version must provide linked-clone support for this option to appear.

Characteristic — Full clone — Linked clone

Disk independence — Has independently copied virtual disks. — Depends on a base disk or snapshot.

Storage use — Requires more space because data is copied. — Usually uses less initial space.

Dependency — Can operate without the source after copying finishes. — Requires the base resources to remain available and consistent.

Suitability for backup — Generally the safer choice for a long-term independent copy. — Poorer choice when the base may be deleted or moved.

Portability — Easier to move as a self-contained VM, subject to attached resources. — Less portable because its base dependency must also be preserved.

Risk when removing base resources — Removing the source does not normally break the full clone. — Deleting or altering the required base disk or snapshot can break the linked clone.

Choose a full clone for an independent backup-like copy, long-term retention, or moving the duplicate to another host. Choose a linked clone when saving storage and quickly creating dependent test environments matter more than independence.

Understand Snapshot Choices

A VM can contain snapshots and associated disk states. During cloning, VirtualBox may offer a choice between cloning only the current machine state and retaining snapshot history.

  • Current state only: creates a clone based on what the VM looks like at the selected point, without preserving the complete snapshot tree.
  • Retain snapshot history: copies the relevant snapshot structure when the version and clone mode support it, allowing more historical states to remain available.

Retaining snapshots can increase storage consumption and make the resulting VM more complex to manage. Select the mode that matches the goal: a simple test copy usually needs only the current state, while a recovery or investigation workflow may need snapshot history.

Clone a VM with VirtualBox Manager

  1. Power off the source VM cleanly.
  2. Select it in VirtualBox Manager and open the Clone action.
  3. Enter a unique clone name and choose a destination folder if offered.
  4. Select whether to copy the current state or retain snapshots.
  5. Select Full clone for an independent copy, or Linked clone when the dependency and storage trade-off is acceptable.
  6. Enable reinitialize MAC addresses when source and clone could coexist on a network.
  7. Start the operation and wait for the virtual disk copy to finish. Do not interrupt the host or move the involved files while the operation is running.
  8. Locate the new VM in VirtualBox Manager and review its settings before starting it.

Clone a VM from the Command Line

VBoxManage is VirtualBox's command-line administration utility. The exact flags and supported behavior can differ among releases, so check VBoxManage clonevm --help on the host before using a script.

A full clone of the current machine state can be created with a command like this:

VBoxManage clonevm "dev-app-baseline" --name "dev-app-update-test" --basefolder "/path/to/vms" --register --mode machine

Omit keepallmacs so VirtualBox can generate new adapter MAC addresses according to the release's default behavior. If a controlled offline copy must retain all MAC addresses and the release supports the option, use:

VBoxManage clonevm "dev-app-baseline" --name "dev-app-offline-copy" --register --mode machine --options keepallmacs

To retain snapshot history when supported, use --mode all instead of --mode machine. A linked clone can be requested with the link option:

VBoxManage clonevm "dev-app-baseline" --name "dev-app-linked-test" --register --mode machine --options link

Option combinations and names can vary by VirtualBox release. Confirm the syntax and the meaning of MAC-related options with VBoxManage clonevm --help before relying on a command in automation.

Verify the Clone Before First Boot

Before starting the clone, open its settings and compare the important values with your plan.

Area — What to check — Why it matters

VM name and location — Confirm the unique name and destination folder. — Prevents operating or deleting the wrong VM.

Virtual disk attachments — Confirm the expected disks are present and paths are accessible. — Missing disks can prevent booting or cause data loss.

Network adapter and MAC address — Review whether the adapter is enabled, its MAC is unique, and its mode is intentional. — Controls connectivity and network identity.

Guest hostname and IP settings — Check static addresses, DHCP behavior, reservations, and DNS records. — Prevents collisions with the source.

Boot success — Start the clone and confirm the guest operating system loads. — Verifies that the copied VM is usable.

Shared folders and removable devices — Review host folders, USB filters, and optical media. — These resources may still point to host-specific or unavailable objects.

After booting, verify network connectivity only when networking is intended. Confirm that the clone has the expected MAC address, hostname, IP configuration, and access to the required networks.

Isolate and Re-identify the Clone

For risky testing, disconnect the clone's virtual adapters before first boot or choose an intentionally isolated network mode. NAT commonly lets a guest access external networks through the host. A host-only network allows communication between the host and guests on an isolated virtual network. Select the mode based on the test rather than leaving the source's settings unquestioned.

If both systems will coexist, update the clone as appropriate:

  • Change the guest hostname.
  • Review static IP settings, DHCP reservations, and DNS records.
  • Regenerate or generalize operating-system machine identifiers using the guest OS procedure.
  • Update endpoint-management registrations, application registrations, certificates, and machine-specific credentials where relevant.

Practical Examples

Test a Risky Software Update

  1. Clone the known-working development VM.
  2. Name the copy dev-app-update-test.
  3. Generate new adapter MAC addresses.
  4. Use NAT or an isolated test network as appropriate.
  5. Apply the update only in the clone.
  6. Keep the original VM untouched as the rollback point.

Create an Independent Backup-Like Copy

  1. Shut down the source cleanly.
  2. Create a full clone rather than a linked clone.
  3. Store it in a separate host location with sufficient capacity.
  4. Boot the copy once and verify that the guest starts and its disks are available.
  5. Record the clone's location, VirtualBox version, and any external resources it still requires.

Run Two Copies in One Lab

  1. Clone the Linux or Windows lab VM with new MAC addresses.
  2. Start the clone with networking disconnected if identity changes must happen first.
  3. Change the guest hostname after startup.
  4. Review static IP addresses and DHCP reservations.
  5. Choose NAT, host-only, or another deliberate network configuration.
  6. Reconnect and test communication without creating an address or identity collision.

Create Disposable Training Machines

  1. Maintain a baseline VM with the required learning tools.
  2. Clone it for each exercise or learner.
  3. Use clear names and folders for temporary machines.
  4. After the exercise, delete each clone and its associated disk files if it is no longer needed.

Delete an Unwanted Clone Safely

In VirtualBox Manager, removing a VM from the list is not always the same as deleting its files. The remove dialog may offer an option to remove only the registration or to delete the associated files. Removing only the registration leaves disks and configuration files on the host; deleting the files frees storage but permanently removes the clone's data.

Before deleting, confirm the VM name, check whether it is a full or linked clone, and verify that no other VM depends on its disks. A linked clone must not be deleted or separated from required base resources casually.

Troubleshooting

The Clone Has No Network Connectivity or Conflicts with Another VM

Likely causes include a duplicate MAC address, a duplicated static IP address, or a DHCP reservation tied to the original identity.

  1. Power off the affected VM.
  2. Generate a new MAC address in the clone's network adapter settings, or recreate it with MAC reinitialization enabled.
  3. Update the guest hostname and network configuration.
  4. Check DHCP reservations and DNS records.
  5. Reconnect and test networking.

The Clone Fails Because the Host Is Out of Disk Space

A full clone may require space for a complete virtual disk copy. Existing snapshots can substantially increase the requirement. Free storage, choose a larger destination volume, or use a linked clone only if its dependency model is acceptable.

The Clone Does Not Start or Reports Missing Media

Inspect the clone's Storage settings. Verify that virtual disk files exist and are accessible. Remove obsolete removable-media attachments or attach the correct optical image. Also check whether the clone references an external disk or host path that was not copied.

A Linked Clone Stops Working After Base Changes

A linked clone depends on its base disk or snapshot. Moving, deleting, or altering required base resources can make it unusable. Restore the required resources if possible, use a full clone for independent long-lived copies, and document dependencies before deleting source VMs or snapshots.

Both Machines Have the Same Identity in Management Tools

The guest operating system or an installed application may retain a machine-specific identifier from the source. Follow the operating system and management-platform procedure to generalize or regenerate that identity, then update hostnames, registration records, and credentials before placing both machines in service.

Exam-Relevant Notes

  • A clone is a new VM based on a source VM; it is not merely a shortcut or a renamed entry.
  • A full clone is independent because its virtual disks are copied.
  • A linked clone saves storage but depends on a base VM or snapshot.
  • Generate new MAC addresses when source and clone may use the same network.
  • Snapshots can affect both storage requirements and the history copied into the clone.
  • Changing a MAC address does not automatically change the guest hostname, IP address, or operating-system machine identity.
  • Removing a VM from VirtualBox Manager can mean unregistering it or deleting its files; check the selected action.

For related VirtualBox work, continue with the virtual machine cloning workflow and apply the same identity, storage, and verification principles when preparing test copies.