Skip to main content
Talos Director is in Limited Availability. Limited Availability customers receive full production support and work directly with Sidero Labs engineering during onboarding. General availability is planned for January 2027, and the console is changing quickly until then, so details on these pages may differ from what you see.To request access, visit siderolabs.com/getdirector.
Talos Director converts virtual machines from VMware vCenter to run on its own hosts. The conversion copies each VM’s disks into a Talos Director storage pool, recreates the VM, and carries its network configuration across, so applications move without changes.

​
Convert a VM

Navigate to Compute > Virtual Machines > Import to start a conversion. The wizard has five steps.

​
1. Connect

Enter your vCenter’s hostname or IP address, a username, and a password. Clear Verify SSL Certificate only if your vCenter uses a self-signed certificate and you trust the network path to it.

​
2. Select VM

Choose the VM to convert from the VMs vCenter reports.

​
3. Requirements

Talos Director checks that the VM is ready to convert:
  • Guest credentials: an account on the VM’s operating system. Talos Director uses it to read the guest’s network configuration and to remove VMware Tools during the conversion.
  • No VMware snapshots: the VM must not have snapshots in vCenter.
  • VirtIO drivers and QEMU Guest Agent: these must be installed in the guest before conversion, whichever cutover mode you choose, so the converted VM can boot and report back on KVM. For Windows, the step links to the VirtIO driver ISO.

​
4. Configure

​
5. Convert

Start the conversion. Progress, transfer rate, and time remaining appear on the Conversion Jobs page (/conversion-jobs), alongside every past conversion and its outcome.

​
Cutover modes

​
Bring firewall rules across

If you use VMware NSX, Import from NSX in Network > Security Groups, Policies, and Services brings your NSX groups, rules, and service definitions into Talos Director. See Security.