Import VirtualBox and VMware VMs into KVM
VMRelay imports VirtualBox .vbox and VMware .vmx machines, or individual .vdi and .vmdk disks, into KVM on a remote Ubuntu or Debian host. It reads available metadata, copies and converts the disks to qcow2, and leaves source files untouched. Check the imported guest before retiring the original.
Standalone tools. Apache licensed and free for commercial use. No SimpleHelp licence required.
What should I prepare before importing?
Shut down the source VM and keep a separate backup before copying its files. Do not take a live copy of changing disks. Keep the original machine available until you have verified the import.
- A connected, tested VMRelay host with enough free space for both the source files and the converted disks.
- The source metadata and every disk file it references. A
.vboxor.vmxfile alone is not the VM. - A complete source disk chain. If a VM uses snapshots or linked disks, consolidate or export a standalone copy in the source platform before transferring it.
- Guest recovery information where applicable, including encryption recovery keys, administrator access and application licence details. Do not put keys in a shared transfer directory.
How do I transfer and import the source?
Copy the powered-off test VM to a directory your SSH account can read on the host. For example, transfer a complete prepared export from your workstation:
ssh [email protected] 'mkdir -p ~/vm-imports'
scp -r ./test-vm [email protected]:~/vm-imports/- In
vmrelay, open the destination host and pressifrom its VMs or Config tab. - Press
Enteron Source to browse the remote filesystem. Select the copied.vboxor.vmxfile, or a supported disk file. - Review the import settings and start the import. VMRelay creates a new VM and copies/converts the disks to qcow2. It does not modify the source files.
- Open the imported VM and review its resources, firmware and disks before starting it. Open its browser console for the first boot.
A disk-only import has no full-machine metadata to read. Be ready to check firmware, boot order and guest-specific requirements yourself.
What changes when a VM moves to KVM?
VMRelay ignores source networking and applies its own NAT, VNC, USB tablet, lifecycle and ownership defaults. Import is not a promise to reproduce the source hypervisor configuration exactly.
- Check BIOS versus UEFI boot compatibility and any encrypted-disk recovery prompt.
- Check storage and network drivers. Remove obsolete guest integration tools or install appropriate replacements after confirming a recovery route.
- Check IP addresses, DNS, application connectivity and any service that relied on the original network adapter or static address.
- Check OS and application activation. A change of virtual hardware can require reactivation.
- Avoid running two copies of a domain-joined or service-hosting machine on the same reachable network until you have reviewed their identities.
How do I verify the migration?
- Boot the imported machine and sign in using its console. Confirm that expected disks and files are present.
- Test required applications, network access and a normal guest reboot. Record any manual adjustments.
- Retain the backup and original VM until the imported copy passes your test plan. Only then decide whether to remove the staged import files.
If import fails, check source paths and referenced disks, available host storage, and the host test results. If it imports but will not boot, investigate guest firmware, disk attachment and driver compatibility before changing or deleting the original.
Your questions, answered
Can I convert VMDK or VDI to qcow2 without a full VM definition?
Yes. VMRelay accepts .vmdk and .vdi disk-only sources and converts imported disks to qcow2. You still need to verify the guest configuration and boot requirements.
Does import preserve the original network?
No. VMRelay ignores source networking and uses its own defaults. Review addresses, drivers, connectivity and identity before placing the imported machine into service.
Related guides and tools
Manage Remote KVM VMs from macOS or Linux
Manage KVM virtual machines on an existing Ubuntu or Debian server from macOS or Linux. Use VMRelay over SSH, with browser consoles and no web admin port.
Read guideRun Windows 11 Test VMs on a Linux Server over SSH
Create Windows 11 test VMs on a remote Linux server with VMRelay. Configure UEFI, Secure Boot and TPM 2.0, then test installers through an SSH browser console.
Read guideRun AI Agents in Disposable Ubuntu VMs
Use VMRelay and agent-sudo to run trusted AI agents in disposable Ubuntu VMs. Keep root grants in the guest and review network access, data and cleanup.
Read guideVMRelay documentation and downloads · agent-sudo documentation and downloads