Migration from vSphere

Kyvernon names its objects by its own terms. Terminology for vSphere users lists the Kyvernon term next to the vSphere term for the objects and functions that have another name. The web console can show both: the setting Show vSphere terms in the user menu adds the vSphere name next to each Kyvernon term.

The order of work for a virtual machine:

1. Migration overview explains the methods that exist today and what is carried over.
2. Prepare guests lists what the guest needs before the move, because Kyvernon VMM presents virtio devices.
3. Import an OVA or OVF package moves a virtual machine that was exported from vSphere.
4. Import a VMDK disk covers the disk formats that the import converts and what to do with the others.
5. After the import checks networks, the guest agent and change tracking, and starts the first backup.

Tools and scripts that you used with vSphere keep working against the vSphere-compatible endpoints of Kyvernon: see Compatibility.

• Migration overviewWhich methods move a virtual machine from vSphere to Kyvernon today, what the import carries over and what it leaves to you.
• Prepare guestsWhat a guest needs before it moves to Kyvernon VMM, and how to check in the console that it came up: drivers, guest agent, cloud-init.
• Import an OVA or OVF packageImport a virtual machine exported from vSphere as an OVA or OVF package with the console wizard: package, destination, networks, disks.
• Import a VMDK diskImport the VMDK disks of a package in the console, the formats that the import converts to qcow2 and what to do with a disk that is refused.
• After the importCheck the networks, turn on change tracking, start the imported virtual machine, check the guest agent and run its first backup in the console.
• Terminology for vSphere usersThe Kyvernon term next to the vSphere term for objects and functions with another name.