Integrate with Awanio Vapor (standalone)

A standalone Vapor target lets Condensa migrate VMs directly onto a single Vapor host — no control plane required. Ideal for small sites and proof-of-concepts. Since the single host is the destination, the wizard skips host selection automatically.

VDDK is required

The standalone Vapor path uses the VDDK direct-pull engine only — there is no staged fallback. Install VDDK on the host before running migrations.

Prerequisites

• A Vapor host with the Virtualization feature enabled, reachable from the Condensa server over HTTPS.
• Network access from the Vapor host to ESXi (ports 443 and 902).
• nbdkit (≥ 1.38) with the VDDK plugin installed on the host, plus qemu-nbd and nbdfuse. These are free software and are not uploaded through the UI — install them on the host first.
• VDDK uploaded on the host: in the Vapor UI open System → Third-party Libraries, upload the VDDK tarball downloaded from the Broadcom portal, and confirm the status shows Installed.

Both steps, with commands, are in About VDDK.

1. Create an API token in Vapor

In the Vapor UI, create an API token for Condensa (Host → API Tokens). Copy the token value — it is shown once.

2. Register the provider in Condensa

1. Go to Providers → Add Provider.
2. Choose vendor Awanio Vapor.
3. Fill in:
   • Label — e.g. vapor-site-b
   • API URL — the Vapor endpoint including the API base, e.g. https://vapor.example.com:8080/api/v1
   • API token — the token from step 1
4. Save, then click Test on the provider card.

3. Run a migration

In the migration wizard select your VMware source and VMs, choose the Vapor provider as target, then:

• Storage pool — pools are addressed by name (e.g. default)
• Network — the libvirt network for the VM's NIC (default None)

Host selection is skipped — the Vapor host itself is the destination. Warm migration is fully supported: full pull while the source runs, CBT delta passes, then a short cutover.

Verifying VDDK on the host

The provider Test action checks connectivity. To confirm the VDDK capability itself, the host's import-capability endpoint should report "vddk": true; in practice, the migration wizard shows whether the direct-pull engine is available for the selected target.

Troubleshooting

• 401 from Vapor — the API token is invalid or was revoked; create a new one and update the provider.
• nbdkit not found (exec: "nbdkit": executable file not found in $PATH) — the host has the VDDK library but not nbdkit itself. Uploading VDDK again will not help; install nbdkit with its VDDK plugin as described in About VDDK.
• Migration fails immediately with a VDDK message — VDDK is missing on the host; install it via System → Third-party Libraries.
• VDDK "Unknown error" on disk open — usually a stale ESXi TLS thumbprint or too many rapid connection attempts; retry after a minute and verify the ESXi certificate hasn't changed.