OnApp enables you to migrate your vCenter virtual servers from VMware to KVM virtualization. You can initiate the migration from your OnApp Control Panel, using the procedure described in this document. The migration workflow includes several actions that are required to get your virtual servers up and running on KVM. 

This workflow describes the basic steps that are run to migrate a virtual server from vCenter to KVM. You can enable some additional automation settings while initiating the migration in the wizard.

The Migration Workflow

  1. You initiate the migration of a virtual server from your vCenter to a KVM compute resource. 
  2. The source virtual server is stopped and then exported from vCenter as a self-contained OVA package. 
  3. The OVA package is imported to the OVA List page in OnApp Control Panel. 
  4. The OVA package is converted to the KVM virtualization.
  5. The virtual server is built from the OVA package. 

Before you proceed to migrating your virtual server from vCenter to KVM, please take a look at the following section. 


Before You Begin 


Before you proceed further, please note that: 

  • The migration from vCenter to KVM is available on clouds that run OnApp 5.10 and subsequent versions.
  • You can migrate only virtual servers from your vCenter instance to KVM. 
  • vCenter virtual servers with XFS or LVM partitions/file systems cannot be migrated to KVM. 
  • The Migrate any/own virtual server permission should be enabled for a user who wants to migrate a virtual server. 
  • The destination KVM compute, data store, backup server, and network zones should be available in a bucket of a user who runs the migration.
  • You can migrate a virtual server to the KVM compute, data store, backup server, and network zones that have enough resources to handle the virtual server.
    If there are not enough resources available in these zones, you cannot complete the wizard and initiate the migration.

If you experience any issues while migrating a virtual server from vCenter to KVM, see Troubleshooting. 


Migrate Virtual Server to KVM


To migrate a virtual server from a vCenter instance to a KVM compute resource: 

  1. Go to your Control Panel > Cloud > Virtual Servers menu.
  2. Click a label of a virtual server that you want to migrate. 
  3. Click Tools and then click Migration to KVM.
  4. Go through the following steps in the wizard to migrate the virtual server: 

Step 1: Compute Resource

The first step enables you to select a KVM-based compute zone and resource to migrate your virtual server to. 

    • Hypervisor group - select a KVM hypervisor group (compute zone) where you want to migrate the VS
    • Hypervisor - select a destination KVM hypervisor (compute resources) from the compute zone
    • Label - edit a label of the VS if you want to keep the source VS after the migration

    • Hostname - edit a hostname of the VS if you want to keep the source VS after the migration

      • Hostname may contain letters (A-Z), numbers(0-9) and hyphens (-) but no spaces or periods (.). The name may not consists entirely of digits.
      • For Windows-based VSs, the hostname length should be between 1 and 15 characters.


Click Next. 

Step 2: Disks

The second step allows you to configure the logic of the disks migration to data stores associated with the KVM compute zone. You can migrate all disks to one data store or select a separate data store for each disk. 

    • Allow Disk to One Data Store - switch the option on/off to enable or disable the migration of disks to one data store. Depending on the selected option, one of the following boxes becomes available: 
      • All Disks to One Data Store - select one data store to migrate all the the disks to 
      • Select Data Store for Disk - select a separate data store to migrate each disk to

Click Next. 

Step 3: Networks

The third step enables you to apply the network configuration based on the networks available in the KVM compute zone. You assign each interface to a separate network from a destination network zone. 

    • Network - select a network for the interface or leave Any. If you select a specific network, you can also set the following network configurations.
    • IP net - select an IP net that contains the IP address ranges of the network or leave Any 
    • IP range - select an IP range from an IP net that you selected in the previous step or leave Any
    • IP address - select an IP address from an IP range that you selected in the previous step or leave Any

Click Next. 

Step 4: Windows Licensing 

If you migrate a Windows virtual server, the forth step of the wizard enables you to edit the licensing settings. You can select one of the following licensing options:

    • None - select the checkbox to migrate a virtual server without license changes
    • MAK - select the checkbox to migrate a virtual server with the MAK license and edit the following settings:
      • Distribution - select the Windows OS distribution of the virtual server
      • R2 - select the checkbox to use an updated release of the Windows OS distribution
      • Architecture - select the architecture of the OS (x86 or x64)
      • Edition - select the edition of the Windows OS
    • Your own license - select the checkbox and paste your own licensing key

Click Next. 

Step 5: Confirmation 

The final step allows you to configure the automation settings and initiate the migration. 

    • Start VS after migrate - enable the option to start the VS after the migration is finished. If you disable this option, you can start the VS via the Power Options after it is migrated. 
    • Remove source VS after successful migration - enable the option to delete the source VS after the migration is finished. If you disable this option, make sure that you edited Label and Hostname of the VS in the first step of the wizard. 

Click Submit to initiate the migration. 

After you submit the changes, several transactions are run to import your virtual server from vCenter to KVM. When the virtual server is built, you can see a log of the transactions in the Activity Log section of the destination VS. The migration process could take up to 15 minutes, depending on the virtual server configuration and the migration settings. If you cannot complete the wizard, see Troubleshooting. 


Troubleshooting


You may face the following issues while initiating the migration of your virtual server from vCenter to KVM:

  • Not enough resources are available in a destination compute zone. 
    If there are not enough resources, such as RAM and CPU, select another compute zone or allocate more resources to the destination compute zone. 
  • Not enough disk space is available in a destination data store zone. 
    If there is not enough disk space, select another data store zone or allocate more space to the destination data store zone. 
  • Not enough IP addresses are available in a destination network zone. 
    If there are not enough IP addresses, select another network zone or allocate more IP addresses to the destination network zone. 

See also: