Skip to content

WARNING

This page has not been translated yet and is shown in English. A localized version is coming soon.

Nutanix AHV as a source ​

This guide covers migrating guests out of a Nutanix AHV cluster into a KVM/libvirt target: either a single host managed by Awanio Vapor or a host fleet managed by Awanio Cockpit. The target side of the wizard is exactly the one described in VMware to Vapor and VMware to Cockpit; everything that differs is on the source side and is described here.

The Awanio CEP (KubeVirt) target is not available for a Nutanix source. Choose a Vapor or Cockpit target.

Before you start

  • Sign in to Condensa from the overview.
  • Add the target provider first: Vapor or Cockpit. The target host must run Vapor 3.0.2 or later.
  • Have Prism Element reachable from Condensa (port 9440), and SSH (port 22) to one AHV host of the cluster.
  • Power off each guest you intend to migrate, on Nutanix. Migration from Nutanix is cold only, and Condensa never powers a Nutanix guest off or on.

How the disks move ​

Prism lists the cluster's VMs, but it has no way to stream a disk's content. Every AHV host, however, serves every guest disk of its cluster as an iSCSI target on its own loopback address; that is how AHV itself attaches a disk to a running VM. So Condensa reads each disk on an AHV host:

  • Condensa logs in to the AHV host over SSH.
  • The host's own qemu-img opens the guest's disk through that iSCSI target, read-only.
  • It writes the guest's bytes straight into the target's storage, over an encrypted, short-lived channel. Blocks that hold nothing are skipped, so a mostly-empty disk transfers quickly and arrives thin.

Nothing is created on the cluster: no image, no snapshot, no clone, and nothing is written to its storage containers. That matters on a cluster that is short of space, which is often why it is being migrated off. The only thing written on the AHV host is the target's TLS client certificate, in a 0700 directory under /run (memory, not disk). Each disk gets the certificate the target issued for that disk, and its directory is removed once the disk is done.

The disk never passes through Condensa, and Condensa needs no public address.

Add the Nutanix provider ​

Click the Provider tab, then Add Provider. In the form:

  1. Vendor: choose Nutanix AHV. The port switches to 9440 automatically.
  2. Name: a display name (e.g. Nutanix Jakarta). Add an optional Label to tell apart several clusters, and an optional Description.
  3. Under Connection Details, the Prism login:
    • Host: the Prism Element address, usually the cluster virtual IP.
    • Port: 9440.
    • Prism username and Prism password: a Prism account that can read the VM list. Condensa only reads through Prism.
    • Connection security: Prism ships with a self-signed certificate, so choose Pin this endpoint. Condensa shows the fingerprint it sees; compare it against Prism (for example from a browser on a trusted network), then accept it. Skip verification accepts any certificate and is for throwaway labs only.
  4. Under AHV host login (for reading disks), a different login from Prism:
    • AHV host: the hypervisor IP of one AHV host, not a CVM. Any host of the cluster can read any disk of the cluster.

    • AHV host SSH user: root unless your hosts use another account that can read the iSCSI redirector.

    • AHV host SSH password: that account's password. Condensa stores it encrypted. A password is used rather than a key because Nutanix treats adding a key to an AHV host as an unsupported change to the appliance.

    • SSH Port: 22 unless the host changed it.

    • SSH host key: click Check host key, compare the fingerprint against the host itself, and accept it:

      bash
      ssh-keygen -lf /etc/ssh/ssh_host_ecdsa_key.pub

      Without a pinned host key, migrating requires Skip verification.

  5. Click Test Connection, then Create Provider.

Test Connection checks all of the following:

  • Prism accepts the login and the cluster runs AHV.
  • The AHV host you entered is one of that cluster's hosts.
  • The host accepts the SSH login.
  • The host's qemu-img can read iSCSI.

Listing VMs needs only Prism

The AHV host fields can be left empty while you only browse the inventory. A migration asks for them before it starts.

Cold only, and only for powered-off guests ​

Condensa reads a Nutanix disk only while its guest is off, and it never changes a guest's power state. The cluster is yours, and so is the decision about downtime.

  • In step 3 of the wizard, a running guest cannot be selected. Its row is marked Power off first and says why.
  • When the migration starts, Condensa checks the power state in Prism again. A guest that was started since is refused before anything is copied.
  • After the last disk is copied, Condensa checks once more. If the guest was started while its disks were being read, the copy is not consistent: the migration fails and the copied volumes are removed from the target.

Create the migration ​

Click the Migrations tab, then Create Migration.

Step 1: Basic info and target ​

Fill in the Migration Name and choose the Target Provider (Vapor or Cockpit) and, for Cockpit, the Target Host. Set the Target Storage Pool. These fields behave exactly as in the VMware guides.

Step 2: Source provider ​

Select the Nutanix AHV provider. There is no datacenter to pick; Condensa lists the whole cluster through Prism.

Step 3: Select guests ​

Pick one or more powered-off guests. Each row shows its power state, vCPU and memory, and its disks. Use the search box on a large cluster.

Step 4: Mapping ​

Each guest's source network (the AHV network its NIC is on) is listed with a dropdown for the target network its interface should land on.

  • Map a network to keep the interface. The source MAC address is kept, so guest network configuration bound to the MAC still applies.
  • Leave a network Not mapped to create the VM without that interface. That is the safe choice for a test copy while the original still exists on Nutanix: the copy cannot answer for the original's address.
  • Untick Power on after migration to leave the copy off until you have checked it.

Step 5: Review ​

Check the target, the pool, the networks and the guest list, then click Create Migration.

What arrives on the target ​

  • Every data disk, in the guest's order (SCSI, then PCI, then SATA, then IDE, each by index), with the first disk as the boot disk. CD-ROMs are not copied.
  • The disk bus family the guest was installed with:
    • AHV's SCSI controller is virtio-scsi, so a SCSI disk stays on SCSI;
    • a PCI disk becomes virtio;
    • SATA and IDE disks arrive on SATA, which a guest without virtio drivers can still boot from.
  • Firmware: BIOS or UEFI, as Prism reports it for the guest.
  • vCPU and memory as configured on Nutanix.
  • Network interfaces you mapped, with their source MAC addresses.

The migration log lists each disk as it is copied and every interface that was or was not created.

Start and monitor the migration ​

  1. Open the action menu (three dots on the right of the row) and select Start Migration.
  2. The status changes to Running and the disk shows the phase ConvertingOnSource. The percentage counts through the disk's full size, empty blocks included, so it moves quickly over the empty parts.
  3. On completion the status becomes Success. Click the migration name for per-disk detail and the log. The data plane is shown as Cold · Read on AHV host.

As a reference, a powered-off CentOS 7.9 guest with one 50 GiB disk holding 2.4 GiB of data migrated to a Vapor host in under 30 seconds.

Large guests ​

A migration has no fixed time limit. Its ceiling grows with the size of the disks it copies, so a guest with tens of terabytes that needs more than a day is allowed to finish. What ends a copy early is a stall: a disk that reports no progress for too long (at least 30 minutes, longer for a larger disk) is stopped, and the migration fails.

Keep Condensa running for the whole migration. A migration interrupted by a Condensa restart or update cannot resume; run it again from the start.

What must reach what ​

FromToPortWhy
CondensaPrism Element9440Inventory and power-state checks
CondensaThe AHV host you entered22Running the copy on the host
The AHV hostThe target host (Vapor)The target's migration port rangeThe host writes the disk into the target

Open the migration port range from the AHV host to the target

The target opens its disk intake on a port from a configurable range. On Vapor 3.0.2 and later, set the range under Host → System → Migration and permit that range from the AHV host to the target host. When no range is set, the operating system picks from the ephemeral range (32768–60999 by default on Linux) and the firewall must permit all of it in that direction.

If the AHV host cannot reach the target, the migration stops before copying anything and names the address it tried. If the target is known to Condensa by an address the AHV host cannot reach, set the target provider's Disk stream address to one it can.

Verify on the target ​

Open the target host's dashboard, go to Virtualization, and confirm the migrated VM is present. Start it and check inside the guest that it booted and that every interface you mapped came up on the right network. The guest on Nutanix is left exactly as it was, powered off. Delete it yourself once you are satisfied.

For credit-based licensing and how migrations consume credits, see Licensing.