Upgrade from Citrix Hypervisor 8.2 Cumulative Update 1 < 编辑

By upgrading from an existing version of Citrix Hypervisor to Citrix Hypervisor 8 Cloud, you can retain your existing VMs and configurations.

Perform a rolling pool upgrade to keep all the services and resources offered by the pool available while upgrading all servers in a pool. This upgrade method takes only one Citrix Hypervisor server offline at a time. Critical VMs are kept running during the upgrade process by live migrating the VMs to other servers in the pool.

You can complete a rolling pool upgrade by using the Citrix Hypervisor Center or the xe CLI.

• The Citrix Hypervisor Center provides a Rolling Pool Upgrade wizard, which organizes the upgrade path automatically and guides you through the upgrade procedure. If you are a licensed customer of Citrix Hypervisor or have access to Citrix Hypervisor through a Citrix Virtual Apps and Desktops entitlement, you can use this wizard to upgrade your pool
• If you are using the xe CLI, perform the rolling upgrade manually by live migrating running VMs between Citrix Hypervisor servers accordingly.
• XenCenter is not supported for performing a rolling pool upgrade to Citrix Hypervisor 8 Cloud. Install the latest version of Citrix Hypervisor Center before attempting a rolling pool upgrade. For more information, see Citrix Hypervisor Center.

Can I upgrade?

Ensure that you are eligible to upgrade to the Citrix Hypervisor 8 Cloud release stream:

• Are your servers currently running Citrix Hypervisor 8.2 Cumulative Update 1?

  If not, you cannot upgrade directly to the Citrix Hypervisor 8 Cloud release stream. For more information, see Upgrade from other versions.

• Do you have a valid license for Citrix Hypervisor?

  Only licensed customers or customers that have a Citrix Virtual Apps and Desktops entitlement can upgrade to the Citrix Hypervisor 8 Cloud release stream. If you are an Express Edition (formerly Free Edition) user, you cannot upgrade to the Citrix Hypervisor 8 Cloud release stream. For more information, see Unlicensed users.

• Is the hardware your pool is installed on compatible with Citrix Hypervisor 8 Cloud?

  If not, you cannot move to the Citrix Hypervisor 8 Cloud release stream. For more information about hardware support, see the Hardware Compatibility List (HCL).

• Are you using a supported partition layout?

  The legacy partition layout is no longer supported. If you use it, you might not be able to upgrade to the Citrix Hypervisor 8 Cloud release stream and must instead perform a fresh installation. For more information, see Legacy partition layout

• Are the operating systems of your VMs are supported by Citrix Hypervisor 8 Cloud?

  If your VM operating system is not supported in Citrix Hypervisor 8 Cloud, upgrade your VM operating system to a supported version before upgrading your pool. For more information, see Guest operating system support.

• If you have Linux VMs running in your pool that will be migrated as part of your upgrade, ensure that the latest version of the Citrix VM Tools for Linux is installed.

• Are you registered for Health Check?

  Health Check is no longer supported. Before upgrading to the Citrix Hypervisor 8 Cloud release stream, disable Health Check for your pool. For more information, see Health Check.

• Are any of your VMs using Dynamic Memory Control (DMC)?

  DMC is no longer supported for VMs hosted on a Citrix Hypervisor server that runs the Citrix Hypervisor 8 Cloud release stream. Before upgrading to the Citrix Hypervisor 8 Cloud release stream disable DMC on all the VMs in your pool. For more information, see VMs using Dynamic Memory Control.

• Is the key size of the server’s identity certificate smaller than 2048 bytes?

  If your pool was first installed using XenServer 7.6 or earlier, it might still have certificates with a smaller key size than 2048 bytes. In this case, when you attempt to upgrade to Citrix Hypervisor 8 Cloud, the upgrade wizard shows an error during prechecks. To proceed with the upgrade, you must reset the self-signed certificate on each affected server by running the following command:

   xe host-emergency-reset-server-certificate