Import from VMware ESXi (coming)

Planned import of virtual machines from VMware ESXi hosts and vCenter, with disks downloaded from the datastore and converted for KVM. Not released yet.

Note: The VMware import is coming and not released yet. This page describes what is planned so you can prepare; the details may change before release. The VMware choice may already be visible on the Connect a panel form of a current panel, but its VMs cannot be copied until a node agent with VMware support is released.

What is planned#

A VMware source will be one more kind of source on Infrastructure › Import from another panel, using the same wizard, dry run, queue and progress page as the SolusVM import:

  • Sources: a standalone ESXi host or a vCenter (6.5 or later), connected with a user and password. The password is stored encrypted and never shown; the TLS certificate is pinned after you compare its fingerprint. The inventory is read through the vSphere API, which also works with the free ESXi licence.
  • Inventory: VMs grouped by datacenter, cluster and host, with vCPUs, memory, disks (thin or thick), cards with their MAC addresses, guest addresses from VMware Tools, BIOS or EFI and Secure Boot, and power state.
  • Transfer: the receiving node downloads each disk from the datastore over HTTPS (no SSH on the ESXi host and no proprietary VMware libraries), writing it as a sparse file and resuming a broken download.
  • Conversion: on the node with virt-v2v, which removes VMware Tools and installs VirtIO drivers (for Windows from the virtio-win ISO in your image library). A "copy as is" option will give the server a SATA disk and an e1000 card instead.
  • Power: the VM is shut down first through VMware Tools and powered on again if the import does not complete. With the free ESXi licence, whose API refuses power operations, the import waits for you to shut the VM down yourself.
  • Limits: VMs with snapshots must be consolidated first; templates, raw device mappings and VMs with more than 16 disks are refused. UEFI VMs keep UEFI but start with fresh UEFI variables.

Preparing#

If you plan to use it, you can already:

  • make sure the VMStack nodes that will receive VMs can reach the ESXi host or vCenter on TCP 443;
  • create a vSphere user with datastore browsing and low-level file access (Datastore.Browse, Datastore.FileManagement) and the power-on and power-off privileges;
  • consolidate or delete VM snapshots;
  • add the virtio-win ISO to your image library for Windows guests.

The nodes will need the virt-v2v package, which the node installer is planned to add with a new option.

Progress on this item is on the roadmap and in the changelog.