VMware ESXi and vSphere Cluster Management

How to Move a Virtual Machine in Oracle VirtualBox

Learn how to safely move an Oracle VirtualBox VM to another folder or computer, including file checks, compatibility, registration, and troubleshooting.

Moving an Oracle VirtualBox virtual machine (VM) means relocating its files and then registering the existing machine from its new location. You can move a VM to another folder on the same host system, or transfer it to a different host computer.

The safest approach is to shut down the guest completely, inventory every referenced file, copy the complete VM structure, register the relocated .vbox definition, and test the copy before deleting the original.

What a VirtualBox VM Contains

A virtual machine is a software-defined computer with virtual hardware and its own guest operating system. The physical computer and its operating system are the host system.

A VM is not just one file. It normally consists of a VirtualBox definition file, one or more virtual disks, logs, optional snapshots, saved-state data, and references to other media. The .vbox file is an XML-based definition that describes the VM's virtual hardware and attached resources.

A successful move preserves the relationship between the definition file and every attached disk or referenced file. Copying only the .vbox file, or only the main virtual disk, can produce an incomplete VM.

Relocating versus transferring

Consideration — Move within one host — Move to another host

VM registration — The old registration may need to be removed or updated, then the new .vbox file is added — The destination VirtualBox installation must register the copied .vbox file.

Host compatibility — The same host hardware and operating system remain available — CPU architecture, virtualization support, VirtualBox version, memory, storage, and graphics must be checked.

Network and USB settings — Existing host devices and names usually remain available — Adapter names, USB filters, permissions, and devices may differ.

Shared-folder paths — Existing host paths may still work — Host paths must be recreated or changed for the new computer.

Transfer method — Local file copy or move — External drive, network share, or another suitable transfer method.

Validation — Check boot, disks, snapshots, and settings — Also test host-dependent integrations and guest additions.

Check Compatibility Before Moving

Before copying a large VM, confirm that the destination can run the guest operating system and the VM's selected architecture.

Check — Why it matters — Typical action if incompatible

64-bit guest support — A VM configured for a 64-bit guest needs suitable host processor and virtualization support — Use a destination host that supports the required 64-bit virtualization capability; do not expect an unsupported host to run the VM by simply copying files.

CPU virtualization availability — Hardware virtualization is processor-assisted virtualization used by many modern guest configurations — Enable the relevant virtualization feature in host firmware when supported, and verify that the operating system permits VirtualBox to use it.

VirtualBox version compatibility — VM settings and virtual hardware features can vary between releases — Install a compatible or current VirtualBox release on the destination before registering the VM.

Available RAM and disk space — The destination needs enough memory for the VM and enough storage for all disks, snapshots, and future changes — Free additional space or reduce the VM's assigned memory only after considering the guest operating system's requirements.

Host-specific devices and paths — Shared folders, USB devices, ISO files, and network interfaces belong partly to the host — Recreate or update those settings after registration.

Moving from a 32-bit-capable source host to a suitable 64-bit host is generally possible. Moving a VM configured for 64-bit operation to a host without supported 64-bit virtualization capability is not a supported architecture downgrade.

Substantially different host hardware, firmware settings, graphics support, available memory, or VirtualBox versions can affect startup. Install VirtualBox before transferring the VM so the destination is ready to register and test it.

Locate and Inventory Every VM File

First identify the VM's main directory. In VirtualBox Manager, select the VM and inspect its settings, especially Storage. Do not assume that every attached file is inside the displayed VM folder.

File or folder — Typical extension or name — Purpose — Must be copied — Notes

VM definition — .vbox — Stores the VM's virtual hardware and attachment configuration — Yes — Open this file at the destination to register the existing machine.

Primary and additional virtual disks — .vdi, .vmdk, or .vhd — Stores the guest's virtual hard-drive contents — Yes — Additional disks may be outside the main VM folder.

Snapshots and differencing disks — Snapshots directory and related disk files — Stores point-in-time states and changes made after snapshots — Yes, when snapshots exist — Preserve the entire hierarchy; do not copy only the base disk.

Saved-state files — Saved-state data associated with the VM — Stores suspended memory and device state — Avoid transferring as an active state — Perform a full shutdown or discard the saved state first.

Logs — Logs directory — Helps diagnose startup and hardware issues — Recommended — Logs are useful for troubleshooting but are not the guest's main data.

Attached ISO or external media — ISO files or other host paths — Provides installation or boot media — Copy if needed, or plan to reattach it — The path may be absolute and host-specific.

Host-specific configuration references — Network, USB, shared-folder, and device settings — Connects the guest to host resources — Inspect and reconfigure as needed — These references may not exist on the destination host.

In Storage settings, record each controller, disk, optical medium, and additional attachment. If a disk path points outside the main VM folder, copy that file separately or plan to attach it from its new location after registration.

Example inventory

VM definition:       C:\VM\Windows7\Windows7.vbox
Primary disk:        C:\VM\Windows7\Windows7.vdi
Additional disk:     D:\VirtualDisks\Data.vdi
Snapshots:           C:\VM\Windows7\Snapshots\
Optical medium:      C:\Install\Windows.iso

The additional disk, ISO, and every snapshot-related file must be accounted for even though some are outside the main directory.

Prepare the VM for Relocation

  1. Start VirtualBox Manager and identify the VM you will move.

  2. Shut down the guest operating system normally. A full shutdown is different from suspending or saving the VM state.

  3. If the VM is in a saved state, discard that saved state or start the VM and shut it down completely. A saved state contains suspended memory and device information and should not be treated as a clean shutdown for file copying.

  4. Close the VM window and confirm that no VirtualBox process is still using the machine's files.

  5. Check that the disks are not being modified by another backup, synchronization, or disk-management process.

Copy the Complete VM

Copy the complete VM folder to a new local folder, external drive, network share, or destination host. Preserve the directory structure, especially the Snapshots folder and any relative paths.

Copying first is safer than moving immediately because it provides a rollback copy. Delete the original only after the destination has been tested successfully.

Same-host example

Suppose the source folder is C:\VM\Windows7\ and the destination is C:\VM2\Windows7\. With the VM fully shut down, copy all contents from the source folder to the destination folder, including Windows7.vbox, virtual disks, snapshots, and logs.

Source:      C:\VM\Windows7\
Destination: C:\VM2\Windows7\

Transfer time depends mainly on the size of the virtual disks and the read/write performance of the source and destination storage. A large dynamically allocated disk can still contain a large file, so allow space for its actual file size and snapshot data.

Different-host example

  1. Install a compatible or current VirtualBox release on the destination host.

  2. Copy the complete VM directory using an external drive, network transfer, or another reliable method.

  3. Preserve the copied folder structure rather than extracting disks into unrelated folders.

  4. Copy separately referenced disks and media, or plan to reattach them later.

Register the Relocated VM

Copying files does not automatically make the VM appear in a separate VirtualBox installation. You must register it. Registering means adding an existing VM definition to a particular VirtualBox installation; it does not create a new empty machine.

  1. Open VirtualBox Manager on the host where the copy now resides.

  2. Use the manager's option to add or register an existing machine.

  3. Select the relocated .vbox file, such as C:\VM2\Windows7\Windows7.vbox.

  4. Confirm that the VM appears in the manager with its expected name and settings.

  5. Open Storage settings and verify that every attached disk and optical medium resolves to an accessible path.

If the VM is already listed because the old registration remains, do not register the same identity as an unrelated duplicate. First remove or unregister the stale entry from VirtualBox Manager without deleting the VM files, then add the definition from its new location. Be careful to choose an option that preserves the files.

Validate the Move

  1. Start the relocated VM and confirm that the guest operating system boots normally.

  2. Check that the expected system and data disks are present inside the guest.

  3. Review the VM's Storage settings if VirtualBox reports inaccessible media.

  4. Check snapshots and confirm that they are visible and usable if the VM used them.

  5. Test networking, including the expected adapter mode and connectivity.

  6. Test shared folders, USB devices, and guest additions where applicable.

  7. Verify host paths, permissions, mounted ISO files, and any other host-dependent integration.

Do not remove the source files until the destination copy works as expected and important guest data has been checked.

Troubleshooting

VirtualBox says a virtual disk cannot be found

The disk may have been stored outside the copied folder, referenced by an absolute path that changed, or omitted from a snapshot chain. Locate the missing disk in the source or backup, copy it to the destination, and use Storage settings to attach the correct file.

The VM is not listed after copying

File copying alone does not register a VM. Open or add the relocated .vbox definition from VirtualBox Manager.

The VM does not start on another computer

Check 64-bit guest support, hardware virtualization, available memory, VirtualBox compatibility, and the VM's System settings. If the destination lacks the required architecture or virtualization capability, use a suitable host rather than attempting an unsupported downgrade.

Snapshot errors appear

Snapshot errors commonly result from missing differencing disks or a changed folder hierarchy. Restore the complete snapshot-related structure from the source or backup. Do not selectively copy only the base disk when snapshots are in use.

Shared folders or USB devices no longer work

The new host may use different folder paths, usernames, device identifiers, or permissions. Update Shared Folders and USB settings on the destination and confirm that the host user has permission to access the resources.

The copied VM reports a lock or state problem

The source may have been copied while running or from a saved state, or the transfer may have omitted files. Return to the intact source, perform a full shutdown, repeat the copy, and keep the original until the replacement passes startup and data checks.

Limitations and Cautions

  • Host-specific integrations may need reconfiguration after migration.

  • Network adapter names, shared-folder host paths, USB filters, permissions, and mounted ISO paths can be different on another host.

  • Graphics behavior can change when the destination hardware or display configuration differs.

  • A saved state is not equivalent to a clean shutdown for relocation.

  • A folder move is different from exporting and importing an appliance. OVF/OVA export is a separate portability workflow that packages virtual hardware and disks for transfer.

  • Avoid manually editing VM configuration files unless there is a clear recovery need and you have a backup.

Quick Checklist

  1. Confirm destination CPU architecture, hardware virtualization, VirtualBox version, RAM, storage, and graphics suitability.

  2. Inspect Storage settings and inventory all disks, snapshots, ISO files, and external attachments.

  3. Perform a full guest shutdown and eliminate any saved state.

  4. Close VirtualBox and ensure no process is holding VM files open.

  5. Copy the complete VM folder while preserving its structure.

  6. Copy or reattach files stored outside the main folder.

  7. Register the relocated .vbox file in VirtualBox Manager.

  8. Boot the VM and test disks, snapshots, networking, shared folders, USB, and guest additions.

  9. Keep the original until validation is complete.

For the core procedure, see the VirtualBox virtual machine move guide whenever you need to review the relocation steps.