Conversion Manager

XenServer Conversion Manager helps you migrate workloads from VMware to XenServer by moving batches of VMware virtual machines to your XenServer environment.

XenServer Conversion Manager makes migration easier; it does more than just convert virtual machines. XenServer Conversion Manager helps you prepare the virtual machines for networking and storage connectivity. Following conversion the virtual machines are almost ready to run.

Convert from VMware to XenServer

XenServer Conversion Manager allows you to:

  • Convert multiple VMs using one simple wizard

  • Map network settings between VMware and XenServer so your converted VMs can be up and running with the proper network settings

  • Select a storage location where you would like your new XenServer VMs to run

Notes:

  • XenServer Conversion Manager does not remove or change your existing VMware environment. VMs are duplicated onto your XenServer environment and not removed from VMware.

  • XenServer Conversion Manager is available for XenServer Enterprise Edition customers or customers who have access to XenServer through their Citrix Virtual Apps and Desktops entitlement. For more information about XenServer licensing, see Licensing. To upgrade, or to buy a XenServer 7.6 license, visit the Citrix website.

Understand XenServer

Before you can convert your environment, it is suggested that you become familiar with XenServer concepts. For more information, see Technical overview.

To use XenServer Conversion Manager successfully, perform the following tasks:

  • Setting up a basic XenServer environment, including installing XenServer. For more information, see. Quick start](/en-us/xenserver/current-release/quick-start.html) and Install.

  • Creating a network in XenServer, assigning an IP address to a NIC. For more information, see Quick start.

  • Connecting to storage. For more information, see Quick start.

Note:

XenServer documentation is available from docs.citrix.com, Knowledge Center articles, and white papers are available from the Citrix Knowledge Center.

Compare VMware and XenServer terminology

The following table lists the approximate XenServer equivalent for common VMware features, concepts, and components:

VMware Term XenServer Equivalent
VMware vSphere Client XenCenter (the management console for XenServer)
Cluster / Resource Pool Resource Pool
Data Store Storage Repository
vMotion XenMotion
Distributed Resource Scheduling (DRS) Workload Balancing
High Availability (HA) High Availability (HA)
vCenter Converter XenConvert, XenServer Conversion Manager
Role Based Access Control (RBAC) Role Based Access Control (RBAC)

Conversion overview

XenServer Conversion Manager creates a copy of each targeted VM. After converting the targeted VM to a XenServer VM with comparable networking and storage connectivity, it imports the VM into your XenServer pool or host. You can use XenServer Conversion Manager to convert as few as one or two VMs or perform batch conversions of an entire environment.

Note:

Before converting the VMs from vSphere, you must shut down the VMs (intended for conversion) on vSphere. The current version of XenServer Conversion Manager does not support converting a running VM using memory copied from vSphere to XenServer.

The XenServer Conversion Manager conversion process requires four items:

  • XenServer Conversion Manager Console - the user interface where you set conversion options and control conversion. You can install the console on your Windows or a Linux local desktop. XenServer Conversion Manager requires a connection to XenServer and the XenServer Conversion Manager Virtual Appliance.

  • XenServer Conversion Manager Virtual Appliance - a pre-packaged VM you import into the XenServer host or pool where you want to run the converted VMs. The virtual appliance converts the copies of the VMware VMs into the XenServer virtual-machine format. After conversion, it imports these copies into the XenServer pool or host.

  • XenServer standalone host or pool - the XenServer environment where you want to run the converted VMs.

  • VMware server. XenServer Conversion Manager requires a connection to a VMware server that manages the VMs you want to convert. This connection can be to a vCenter Server, ESXi Server, or ESX Server. The VMs are not removed from the VMware server. Instead, the XenServer Conversion Manager Virtual Appliance makes a copy of these VMs and converts them to XenServer virtual-machine format.

The following illustration shows the relationships between these components:

Conversion Manager Virtual Appliance facilitates communications

This illustration shows:

  1. How XenServer Conversion Manager communicates with XenServer Conversion Manager Virtual Appliance.
  2. How the XenServer Conversion Manager Virtual Appliance authenticates with the VMware server.
  3. How the VMware server responds to the XenServer Conversion Manager Virtual Appliance during conversion.

The VMware server communicates with the XenServer Conversion Manager Virtual Appliance only when the appliance queries the VMware server for environment information and disk data through-out the conversion.

Summary of how to convert VMs

You can configure the XenServer Conversion Manager and start to convert VMs in just a few easy steps:

  1. Download the XenServer Conversion Manager Virtual Appliance and the XenServer Conversion Manager Console from the [XenServer 7.6 Enterprise Edition page].

  2. Import the XenServer Conversion Manager Virtual Appliance into the XenServer using XenCenter.

  3. Configure the XenServer Conversion Manager Virtual Appliance using XenCenter.

  4. Install the XenServer Conversion Manager Console.

  5. From the XenServer Conversion Manager Console, launch the conversion wizard and start to convert VMs.

The sections that follow explain these steps in detail. Information is also available in the XenServer Conversion Manager Help, which appears in the XenServer Conversion Manager Console.

Prepare your environment

Before converting your VMware environment, you must create and prepare the target XenServer standalone host or environment to run the converted VMware VMs. Preparing your environment includes the following activities:

  1. Defining a strategy of how you convert your VMware environment. Do you just want to convert 1 or 2 VMs? Do you want to convert your entire environment? Do you want to create a pilot first to ensure that your configuration is correct? Do you run both environments in parallel? Do you want to maintain your existing cluster design when you convert to XenServer?

  2. Planning your networking configuration. Do you want to connect to the same physical networks? Do you want to simplify or change your networking configuration?

  3. Installing XenServer on the hosts you want in the pool. Ideally, you should have the NICs on the hosts plugged in to their physical networks before you begin installation.

  4. Creating a pool and performing any basic networking configuration. For example, do the following:

    • Configure a network to connect to the VMware cluster on the XenServer host (if the cluster is not on the same network as the XenServer host).

    • Configure a network to connect to the storage array. That is, if you use IP-based storage, create a XenServer network that connects to the physical network of the storage array.

    • Create a pool and add hosts to this pool.

  5. (For shared storage and XenServer pools.) Preparing the shared storage where you store the virtual disks and creating a connection to the storage, known as a Storage Repository (SR) on the pool.

  6. (Optional.) Although not a requirement for conversion, you may want to configure the administrator accounts on the XenServer pool to match those accounts on the VMware server. For information about configuring Role-based Access Control for Active Directory accounts, see the XenCenter Help or Quick start.

Install XenServer and create a pool

Before you can convert VMware VMs, ensure that you create a XenServer pool or host where you want to run the converted VMs. This pool must have networking configured so it can connect to the VMware server. You may also want to configure the same physical networks on the XenServer pool that you have in the VMware cluster, or simplify your networking configuration. If you want to run the converted VMs in a pool, create a storage repository before conversion and add the shared storage to the pool.

If you are new to XenServer, you can learn about XenServer basics, including basic installation and configuration, by reading Quick start.

XenServer environment considerations

Before installing XenServer and importing the virtual appliance, consider the following factors that may change your conversion strategy:

Selecting the host where you want to run the XenServer Conversion Manager Virtual Appliance. Import the virtual appliance into the stand-alone host or into a host in the pool where you run the converted VMs.

For pools, you can run the virtual appliance on any host in the pool, provided its storage meets the storage requirements.

The storage configured for the pool or host where you want to run the converted VMs must meet specific requirements. If you want to run your newly converted VMs in a pool, their virtual disks must be stored on shared storage. However, if the converted VMs run on a single standalone host (not a pool), their virtual disks can use local storage.

If you want to run the converted VMs in a pool, ensure that you add the shared storage to the pool by creating a storage repository.

Guest operating systems supported for conversion. XenServer Conversion Manager supports converting VMware VMs running any of the Windows guest operating systems that XenServer supports. For a list of Windows guest operating systems supported by XenServer, see Guest operating system support. The following Linux operating systems are also supported.

  • RHEL 5.4/5.6/6.4/7.0

  • CentOS 5.5/6.3/6.4/6.5/7.0

  • SLES 11 SP1/SP2/SP3/SP4

  • Ubuntu 12.04/14.04/16.04

Meet networking requirements

To convert VMware VMs, the XenServer Conversion Manager Virtual Appliance needs connectivity to a physical network or VLAN that can contact the VMware server. (In the following sections, this network is referred to as the “VMware network.”)

If the VMware server is on a different physical network than the hosts in the XenServer pool, add the network to XenServer before conversion.

Map your existing network configuration

XenServer Conversion Manager includes features that can reduce the amount of manual networking configuration needed after you convert from your existing VMware VMs to XenServer. For example, XenServer Conversion Manager will:

  • Preserve virtual MAC addresses on the VMware VMs and reuse them in the resulting XenServer VMs. Preserving the MAC addresses associated with virtual network adapters (virtual MAC addresses) may:

    • Help preserve IP addresses in environments using DHCP

    • Be useful for software programs whose licensing references the virtual MAC addresses

  • Map (virtual) network adapters. XenServer Conversion Manager can map VMware networks onto XenServer networks so that after the VMs are converted, their virtual network interfaces are connected accordingly. XenServer networks you can choose include standard physical networks (known as External Networks), VLANs, single-server private networks, and cross-server private networks.

    For example, if you map VMware 'Virtual Network 4' to XenServer 'Network 0', any VMware VM that had a virtual adapter connected to 'Virtual Network 4' is connected to 'Network 0' after conversion. XenServer Conversion Manager does not convert or migrate any hypervisor network settings. The wizard only alters a converted VM's virtual network interface connections based on the mappings provided.

    Note:

    You do not need to map all of your VMware networks on to the corresponding XenServer networks. However, if you prefer, you can change the networks the VMs use, reduce, or consolidate the number of networks in your new XenServer configuration.

    To gain the maximum benefit from these features, Citrix recommends the following:

    • Before installing XenServer, plug the hosts into the networks on the switch (that is, the ports) that you would like to configure on the host.

    • Ensure that the XenServer pool can see the networks that you would like to be detected. Specifically, plug the XenServer hosts into switch ports that can access the same networks as the VMware cluster.

    Though it is easier to plug the XenServer NICs into the same networks as the NICs on the VMware hosts, it is not required. If you would like to change the NIC/network association, you can plug a XenServer NIC into a different physical network.

Prepare for the XenServer Conversion Manager networking requirements

When you perform conversion, you must create a network connection to the network where the VMware server resides. XenServer Conversion Manager uses this connection for conversion traffic between the XenServer host and the VMware server.

To create this network connection, you must perform two tasks:

  • When you import the XenServer Conversion Manager Virtual Appliance, specify the network you added for conversion traffic as a virtual network interface. You can do so by configuring interface 1 so it connects to that network.

  • Before you run the conversion wizard, add the network connecting VMware and XenServer to the XenServer host where you want to run the converted VMs.

By default, when you import the XenServer Conversion Manager Virtual Appliance, XenCenter creates one virtual network interface associated with Network 0 and NIC0 (eth0). However, by default, XenServer Setup configures NIC0 as the management interface, a NIC used for XenServer management traffic. As a result, when adding a network for conversion, you may want to select a NIC other than NIC0. Selecting another network may improve performance in busy pools. For more information about the management interface, see the XenCenter help.

To add a network to XenServer:

  1. In the Resource pane in XenCenter, select the pool where you would like to run XenServer Conversion Manager.

  2. Click the Networking tab.

  3. Click Add Network.

  4. On the Select Type page, select External Network, and click Next.

  5. On the Name page, enter a meaningful name for the network (for example, "VMware network") and a description.

  6. On the Interface page, specify the following:

    • NIC. The NIC that you want XenServer to use to create the network. Select the NIC that is plugged in to the physical or logical network of the VMware server.

    • VLAN. If the VMware network is a VLAN, enter the VLAN ID (or "tag").

    • MTU. If the VMware network uses jumbo frames, enter a value for the Maximum Transmission Unit (MTU) between 1500 and 9216. Otherwise, leave the MTU box t its default value of 1500.

      Note:

      Do not select the Automatically add this network to new virtual machines check box.

  7. Click Finish.

Meet storage requirements

Before you convert batches of VMware VMs, consider your storage requirements. Converted VM disks are stored on a XenServer storage repository.

This storage repository must be large enough to contain the virtual disks for all the converted VMs you want to run in that pool. For converted machines that only run on a standalone host, you can specify either local or shared storage as the location for the converted virtual disks. For converted machines running in pools, you can only specify shared storage.

To create a storage repository:

  1. In the Resource pane in XenCenter, select the pool where you intend to run the XenServer Conversion Manager Virtual Appliance.

  2. Click the Storage tab.

  3. Click New SR and follow the instructions in the wizard. For more instructions, press F1 to display the online help.

XenServer requirements

You can run VMs converted with this release of XenServer Conversion Manager on the following versions of XenServer:

  • XenServer 6.5 Service Pack 1

  • XenServer 7.0

  • XenServer 7.1

  • XenServer 7.2

  • XenServer 7.3

  • XenServer 7.4

  • XenServer 7.5

VMware requirements

XenServer Conversion Manager can convert VMware VMs from the following versions of VMware:

  • vCenter Server 5.5.0, 6.0.0, and 6.5.0
  • vSphere 5.5.0, 6.0.0, and 6.5.0
  • ESXi 5.5.0, 6.0.0, and 6.5.0

Prepare to import the virtual appliance

Before importing the virtual appliance, note the following information and make the appropriate changes to your environment, as applicable.

Download the virtual appliance

The XenServer Conversion Manager Virtual Appliance is packaged in an xva format. You can download the virtual appliance from the [XenServer 7.6 Enterprise Edition page]. When downloading the file, save it to a folder on your local hard drive (typically, but not necessarily, on the computer where XenCenter is installed). After the .xva file is on your hard drive, you can import it into XenCenter.

Note:

XenServer Conversion Manager is available for XenServer Enterprise Edition customers or those who have access to XenServer through their Citrix Virtual Apps and Desktops entitlement. For more information about XenServer licensing, See Licensing. To upgrade, or to buy a XenServer 7.6 license, visit the [Citrix website].

Virtual appliance prerequisites

The XenServer Conversion Manager Virtual Appliance requires a minimum of:

  • XenServer 6.5 Service Pack 1, XenServer 7.0, XenServer 7.1, XenServer 7.2, XenServer 7.3, XenServer 7.4, XenServer 7.5, XenServer 7.6

  • Disk space: 30 GB of disk space

  • Memory: 6.5 GB

  • Virtual CPU allocation: 1 vCPU

Import and configure the XenServer Conversion Manager virtual appliance

The XenServer Conversion Manager Virtual Appliance is a single pre-installed VM designed to run on a XenServer host. Before importing it, review the prerequisite information and considerations in the section called Preparing to Import the Virtual Appliance.

Import the virtual appliance into XenServer

Import the XenServer Conversion Manager Virtual Appliance into the pool or host where you want to run the converted VMs. To import the XenServer Conversion Manager Virtual Appliance, use the XenCenter’s Import wizard.

To import the virtual appliance into XenCenter:

  1. Open XenCenter. Right-click on the pool (or host) into which you want to import the virtual appliance package, and select Import.

  2. Browse to locate the virtual appliance package.

  3. Select the pool or a home server where you want to run the XenServer Conversion Manager Virtual Appliance.

    Note:

    A home server is the host that provides the resources for a VM in a pool. While it can, a XenServer attempts to start the VM on that host, before trying other hosts. If you select a host, the XenServer Conversion Manager Virtual Appliance uses this host as its home server. If you select the pool, the virtual appliance automatically starts on the most suitable host in that pool.

  4. Choose a storage repository on which to store the virtual disk for the XenServer Conversion Manager Virtual Appliance and then click Import. To add a storage repository to the pool, see the section called “Meeting Storage Requirements.” You can choose either local or shared storage.

  5. Ensure the network to be used for conversion (the one that connects the VMware server to the XenServer host) is selected as the network associated with interface 1 ("virtual NIC 1").

    • If the correct network does not appear beside interface 1, use the list in the Network column to select a different network.

    • If you have not added the VMware network that is on a different physical network than the pool, do the following:

      1. Exit the wizard.
      2. Add the network to the pool.
      3. Rerun the wizard.

      For more information, see To add a network to XenServer.

      Warning:

      Do NOT configure NIC0 to your customer network. Assign NIC0 only to "Host internal management network.”

  6. Leave the Start VM(s) after import check box enabled, and click Finish to import the virtual appliance.

  7. After importing the .xva file, the XenServer Conversion Manager Virtual Appliance appears in the Resources pane in XenCenter.

Configure the XenServer Conversion Manager virtual appliance

After you finish importing the XenServer Conversion Manager Virtual Appliance, you must configure it before you can use it to convert VMware VMs. Following the prompts in the XenCenter Console tab.

  1. After importing the XenServer Conversion Manager Virtual Appliance, click the Console tab.

  2. Enter yes to accept the terms of the license agreement. To decline the EULA, enter no.

  3. Enter and confirm a new root password for the XenServer Conversion Manager Virtual Appliance. Citrix recommends selecting a strong password.

  4. Enter a hostname for the XenServer Conversion Manager Virtual Appliance.

  5. Enter the domain suffix for the virtual appliance. For example, if the fully qualified domain name (FQDN) for the virtual appliance is citrix-migrate-vm.domain4.bedford4.ctx4, then enter domain4.bedford4.ctx4.

  6. Enter y to use DHCP to obtain the IP address automatically for the XenServer Conversion Manager Virtual Appliance. Otherwise, enter n and then enter a static IP address, subnet mask, and gateway for the VM.

  7. Review the hostname and network setting and enter y when prompted. This step completes the XenServer Conversion Manager Virtual Appliance configuration process.

  8. When you have successfully configured the appliance, a login prompt appears. Enter the login credentials and press Enter to log in to the XenServer Conversion Manager Virtual Appliance.

After you finish configuring the XenServer Conversion Manager Virtual Appliance, install XenServer Conversion Manager Console. For more information, see Install the Conversion Manager console.

Install the Conversion Manager console

After configuring the XenServer Conversion Manager virtual appliance, continue to install the XenServer Conversion Manager Console on your local workstation. The XenServer Conversion Manager Console is the user interface where you perform most conversion tasks. From the XenServer Conversion Manager Console, you can launch a conversion wizard that lets you select VMware VMs for conversion.

Note:

XenServer Conversion Manager is available for XenServer Enterprise Edition customers or those who have access to XenServer through their Citrix Virtual Apps and Desktops entitlement. For more information about XenServer licensing, see Licensing. To upgrade, or to buy a XenServer license, visit the [Citrix website].

System requirements

Supported guest operating systems:

XenServer Conversion Manager supports converting VMware VMs running any of the Windows guest operating systems that XenServer supports. For a list of Windows guest operating systems supported by XenServer, see Guest operating system support. The following Linux operating systems are also supported.

  • RHEL 5.4/5.6/6.4/7.0

  • CentOS 5.5/6.3/6.4/6.5/7.0

  • SLES 11 SP1/SP2/SP3/SP4

  • Ubuntu 12.04/14.04/16.04

Software requirements:

Microsoft .NET Framework 4.6

Hard drive space required for installation:

10 MB

Installation

The XenServer Conversion Manager Console is installed on the same computer where you run XenCenter.

Important:

  • Before installing the XenServer Conversion Manager Console, remove any other versions of the console from your computer.

  • The XenServer Conversion Manager Console depends on the browser for proxy settings. If XenServer, ESXi and vCenter can only be reached through a proxy server, the details of the proxy server must be entered in the browser's proxy settings. If XenServer, ESXi and vCenter can be reached without a proxy server, and the user has set the browser’s proxy to access the internet, then the addresses of XenServer, ESXi, and vCenter must be added in the proxy exception of the browser’s proxy settings.

To install the XenServer Conversion Manager Console:

  1. Right-click convui_setup.exe, and select Run as administrator.

  2. On the Welcome to the XenServer Conversion Manager Setup Wizard page, click Next.

  3. Review the license agreement and click I Agree to accept the terms of the agreement.

  4. On the Choose Install Location page, choose where you want to install the XenServer Conversion Manager Console and click Install.

    Note:

    By default, the XenServer Conversion Manager Console is installed in C:\Program Files (x86)\Citrix\XCM.

  5. Click Finish.

To remove the XenServer Conversion Manager Console:

  1. Open the Windows Control Panel.

  2. Open Programs and Features.

  3. Select XenServer Conversion Manager.

  4. Click Uninstall.

Convert VMware VMs

When you convert VMware VMs, they are imported into the XenServer pool or standalone host where you are running the XenServer Conversion Manager Virtual Appliance. Converted VMs retain their original VMware settings for virtual processor and virtual memory.

Using XenServer Conversion Manager to convert VMs requires the following tasks:

  1. Starting the XenServer Conversion Manager Console.

  2. Connecting to a XenServer host.

  3. Starting the wizard to a start new conversion job, which requires specifying VMware server credentials and selecting VMs and the storage repository.

Notes:

  • XenServer Conversion Manager supports converting VMware VMs with different storage such as thin provisioning, thick provisioning, IDE, and SCSI.

  • XenServer Conversion Manager does not require the source VMs to have VMware Tools installed. You can perform conversion on VMware VMs regardless of whether or not they have VMware Tools installed.

Task 1: Start the XenServer Conversion Manager console

To start the XenServer Conversion Manager Console:

  1. From the Start menu, select All Programs > Citrix > XenServer Conversion Manager.

    Note:

    You can run only one instance of XenServer Conversion Manager per computer.

  2. Continue on to Connect to XenServer.

Task 2: Connect to a XenServer host

When you start the XenServer Conversion Manager Console, you must connect it to a XenServer host.

Before you begin, ensure that you have the credentials for the XenServer pool (or standalone host). Either the root account credentials or a Role-Based Access Control (RBAC) account with the Pool Admin role configured is acceptable.

To connect to a XenServer host:

  1. If the Connect to XenServer dialog does not appear when you start the XenServer Conversion Manager console, click the Connect button in the toolbar.

    Connect to XenServer

  2. In the Connect to XenServer dialog, enter the following details:

  • Server. Enter the IP address or Fully Qualified Domain Name (FQDN) for the XenServer host where you imported the XenServer Conversion Manager Virtual Appliance. To find the IP address, host in the XenCenter Resources pane, and click the Search tab.

  • User name. Enter the user name for a XenServer account for the pool (or standalone host). This account must be either the root account for the host or pool or have an RBAC role of Pool Admin.

    For detailed information about RBAC, see RBAC overview.

  • Password. Enter the password for that account and click Connect.

    After you successfully connect to the XenServer host, XenServer Conversion Manager displays the Jobs page.

Task 3: Start a new conversion job

Before you start the conversion procedure, ensure that the following is true:

  • You have the credentials for the VMware server containing the VMs you want to convert. The conversion procedure requires you connect the XenServer Conversion Manager Console to the VMware server.
  • THe VMware virtual machine to convert is powered off.
  • The XenServer pool (or host) that run the converted VMs is connected to a storage repository. The storage repository must contain enough space for the converted virtual disks.
  • XenServer pool (or host) has networks that the converted VMs use.

To convert VMware VMs:

  1. Click the Convert button in the Jobs screen.

    Convert VMware VMs

  2. On the Credentials page, enter the following and then click Connect:

    Server. Enter the IP address or FQDN for the VMware server that contains the VMs you want to convert to XenServer.

    User name. Enter a valid user name for this VMware server. This account must either be a VMware admin account or have a Root role.

    Password. Enter the password for the user account you specified in the User name box.

    Enter VMware Credentials

  3. On the Storage Repository page, select the storage repository you want to use during conversion. This storage repository is where the VMs and the virtual disks that you are creating are stored permanently.

    Configure storage repository

  4. On the Virtual Machines page, select the VMware VMs you want to convert, and click Next.

    Select VMware VMs

    As you select VMs to convert, the red-pie wedge increases to indicate what proportion of available storage for the converted VM’s virtual disks to consume.

    During conversion, XenServer Conversion Manager downloads and installs updated kernels for Linux VMs that are not updated. If there is no access to the Internet, XenServer Conversion Manager installs the kernel from the following location of the XenServer Conversion Manager appliance.

    /opt/vpxxcm/conversion/linuxv2v/\${distro}/
    

    The following table lists the kernel versions for the various Linux operating systems supported during conversion.

    Operating System 32-bit/64-bit Recommended Kernel Version Number
    CentOS 5.5 32-bit 2.6.18-412(kernel-Xen)
    CentOS 6.3 32-bit 2.6.32-642
    CentOS 6.4 32-bit 2.6.32-642
    CentOS 6.5 32-bit 2.6.32-642
    RHEL 5.4 32-bit 2.6.18-164
    RHEL 5.6 32-bit 2.6.18-412
    RHEL 6.4 32-bit 2.6.32-642
    SLES 11 SP3 32-bit 3.0.76-0
    SLES 11 SP4 32-bit 3.0.101-63
    Ubuntu 12.04 32-bit Internet connection not needed to update Xen kernel
    Ubuntu 14.04 32-bit Internet connection not needed to update Xen kernel
    Ubuntu 16.04 32-bit Internet connection not needed to update Xen kernel
    RHEL 5.4 64-bit 2.6.18-411
    RHEL 5.6 64-bit 2.6.18-411
    RHEL 6.4 64-bit 2.6.32-642
    RHEL 7.0 64-bit Internet connection not needed to update Xen kernel
    CentOS 5.5 64-bit 2.6.18-412 (kernel-Xen)
    CentOS 6.3 64-bit 2.6.32-642
    CentOS 6.4 64-bit 2.6.32-642
    CentOS 6.5 64-bit 2.6.32-642
    CentOS 7.0 64-bit Internet connection not needed to update Xen kernel
    SLES 11 SP3 64-bit 3.0.76-0
    SLES 11 SP4 64-bit 3.0.101-59
    Ubuntu 12.04 64-bit Internet connection not needed to update Xen kernel
    Ubuntu 14.04 64-bit Internet connection not needed to update Xen kernel
    Ubuntu 16.04 64-bit Internet connection not needed to update Xen kernel
  5. (Optional.) On the Networks page, do one or more of the following tasks to specify how XenServer Conversion Manager converts the virtual network adapters in the VMs under conversion:

    Change any of the XenServer networks the VMware network adapters are mapped to. XenServer Conversion Manager detects the virtual network adapters on the VMs being converted and lets you associate those adapters with networks in XenServer. After conversion, the new VMs will have virtual network interfaces that connect to the XenServer networks you specified in this step.

    Accept the default network mappings. If you specified the VMware physical network or VLAN when you imported the XenServer Conversion Manager Virtual Appliance, you may want to leave the networks on this page at their default settings.

    Select the Preserve Virtual MAC Address check box. XenServer can automatically generate virtual MAC addresses when you create or import VMs. However, you may want to preserve the virtual MAC addresses on your VMware VMs to preserve IP addresses in environments using DHCP. For more information, see the section Preparing for the XenServer Conversion Manager Networking Requirements.

    Configure VM networks

  6. On the Summary page, review the conversion details and click Finish. While the conversion is in progress, the status appears in the Jobs page.

    Conversion summary

    Note:

    Conversion from ESXi or vSphere can take several minutes depending on the size of the virtual disks.

Task 4: Steps after conversion

After conversion, open XenCenter and perform the following steps on your newly converted VMs:

On Windows Machines:

  1. On Windows VMs, depending on your Microsoft licensing model, you may need to reactivate the VM's Windows license. This happens because the Windows operating system perceives the conversion as a hardware change.

  2. On Windows VMs, install XenServer Tools to obtain high-speed I/O for enhanced disk and network performance. XenServer Tools also enable certain functions and features, including cleanly shutting down, rebooting, suspending, and live migrating VMs.

If you are working with a VM that does not have XenServer Tools installed, a Tools not installed message appears on the General tab in the Properties pane. For Windows VMs, you can double-click on this text to switch to the VM console, load the Tools ISO, and launch the Tools installation wizard.

Note:

XenServer Tools must be installed on each VM for the VM to have a fully supported configuration. Although VMs function without XenServer Tools, their performance can be impacted.

Enable VNC On Linux machines

On Linux VMs, perform the following steps to configure the VNC server.

Note:

VNC password must have at least six characters.

For CentOS 5.5 and RHEL 5.4/5.6

  1. Customize RHEL-based VMs firewall to open the VNC port using the following command:

    \> system-config-securitylevel-tui
    
  2. Select Customize and add 5900 to the **Other ports list. Alternatively, you can disable the firewall until the next reboot by running the command:

    \>service iptables stop
    
  3. For CentOS 5.5 and RHEL 5.4/5.6, if the VNC graphic console does not display properly, run:

    init 5
    

    Then check if the graphic console displays properly.

For CentOS 6.3/6.4/6.5 and RHEL 6.4

  1. Set the VNC password

    \>vncpasswd
    
  2. Start the VNC server

    \>service vncserver start
    
  3. For firewall settings, open the file /etc/sysconfig/iptables and add the following line:

    -A INPUT -m state \--state NEW -m tcp -p tcp \--dport 5900 -j ACCEPT
    

    Note:

    Add the above line after:

    -A INPUT -j REJECT \--reject-with icmp-host-prohibited:
    
  4. Enter the following command to restart iptables:

    \>service iptables restart
    

For SLES Linux Enterprise Server 11 SP3 to SP4

  1. Set the VNC password in startup console.

    \>vncpasswd
    

    Note:

    Would you like to enter a view-only password(y/n)? n

  2. Configure the fire wall settings as follows:

    A. Open a text console on the VM and run the YaST utility:

    \>yast
    

    B. Use the arrow keys to select Security and Users in the left menu, then tab to the right menu and use the arrow keys to select Firewall. Press Enter.

    C. In the Firewall screen, use the arrow keys to select Custom Rules in the left menu and then press Enter.

    D. Tab to the Add button in the Custom Allowed Rules section and then press Enter.

    E. In the Source Network field, enter 0/0. Tab to the Destination Port field and enter 5900.

    F. Tab to the Add button and then press Enter.

    g. Tab to the Next button and press Enter. In the Summary screen, Tab to the Finish button and press Enter. Finally, on the top-level YaST screen, Tab to the Quit button and press Enter.

  3. Click Switch to Graphical Console.

  4. If the Graphical Console does not display correctly, switch to Text Console and run command:

    /etc/init.d/vncserver restart.
    
  5. Click Switch to Graphical Console.

Notes:

  • For other graphical console display issues, run: /etc/init.d/vncserver restart.

  • Conversion of VMs with IDE disks are not supported for SLES 11 SP3 to SP4.

For Ubuntu 12.04

  1. Set the VNC password and log on.

Other conversion tasks

This section lists other tasks you may want to perform when converting VMs. These tasks include clearing jobs, saving a summary of jobs, retrying jobs, canceling jobs, and displaying the log file.

To clear all jobs

From the Jobs menu, select Clear Jobs.

To save a summary of jobs

From the File menu, click Save Job Summary.

To retry a job

Click Retry jobs.

Note:

The Retry jobs option is only enabled for failed or canceled jobs.

To cancel a job

Click Cancel jobs.

Note:

Cancel jobs is only enabled for queued or running jobs.

To save the XenServer Conversion Manager application log file

  1. From the Help menu, select Save Support Log Files.

  2. When prompted, specify where you want to store the log files for XenServer Conversion Manager Console (XCMUI.log) and XenServer Conversion Manager Virtual Appliance (XCM.log) logs.

To display conversion details

  1. Select the job in the XenServer Conversion Manager Jobs window.

  2. In the Job Summary pane, click the Get additional log information link.

XenServer Conversion Manager Console retrieves the log from the XenServer Conversion Manager Virtual Appliance and displays the result in a text editor.

To get log details

Logs for both Windows and Linux guests are present in the /var/log/conversion/convsvc.log file. If conversion fails, click the Get additional log information button for details. For Linux VMs, additional logs are present in /var/log/conversion/linuxxenfix.log.

Troubleshoot conversion

This section provides information about troubleshooting the conversion process and converted VMs.

Problems starting a converted VM

In general, conversion runs smoothly and XenServer Conversion Manager converts VMs without any issues. However, in some rare cases, you may receive errors when attempting to open converted VMs. The following sections provide some guidance on resolving errors and other issues.

Blue screen with Windows STOP code 0x0000007B

This stop code indicates that XenServer Conversion Manager was unable to configure a Windows device that is critical to boot in XenServer for the first time. Save the logs and send them to Citrix Technical Support for further guidance.

Windows product activation

Depending on your licensing model, an error message on system activation may appear when you attempt to start a Windows VM.

Note:

Conversion from ESXi or vSphere can take several minutes depending on the size of the virtual disks.

Lost network settings in a Windows VM

If you import a Windows VM from an ESXi server to XenServer, the IPv4/IPv6 network settings can be lost. To retain the network settings, reconfigure the IPv4/IPv6 settings after completing the conversion.

Unable to start VMware SCSI disk

If a VMware VM boots from a SCSI disk but also has one or more IDE hard disks configured, the VM may not boot when you convert it to XenServer. This is because the migration process assigns the IDE hard disks lower device numbers than SCSI disks. However, XenServer boots from the hard disk assigned to device 0. To resolve this issue, rearrange the virtual disk position in XenCenter so that the VM reboots from the virtual disk that contains the operating system.

To change the position of the virtual disk containing the operating system:

  1. In the XenCenter Resources pane, select the powered off guest VM.

  2. Select the Storage tab.

  3. On the Virtual Disks page, select the virtual disk containing the operating system and then click Properties.

  4. In the <operatingsystem> Properties dialog, click the <operatingsystem> tab to display device options.

    Display device options

  5. From the Device Position list, select 0 and Click OK.

Problems during conversion

If you see any errors when converting Linux VMs, remove the converted VM, restart the XenServer Conversion Manager virtual appliance and retry. Logs of failed conversions are stored in /var/log/xensource.log. When you contact Citrix support to raise any issues, we recommend that you provide the log file for troubleshooting.