HP BL680c HP integrated Citrix XenServer 5.0 Release Notes - Page 7
XenServer HP Edition Release Notes
UPC - 884420396314
View all HP BL680c manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 7 highlights
XenServer HP Edition Release Notes Installation and upgrades System requirements, preparation, installation, and initial configuration are described in the XenServer Installation Guide. This release fully supports upgrading from XenServer 4.1.0 HP Edition hosts. You can upgrade 4.1.0 resource pools without any VM downtime by using the rolling upgrade procedures described below. NOTE: Rolling upgrade is not supported for beta versions of XenServer. To upgrade from 4.0.1 to 5.0.0, you must first upgrade 4.0.1 to 4.1.0, and then upgrade to 5.0.0. XenServer 4.1.0 might cause VMs on NFS storage to become detached from their XenServer host after applying an upgrade. To avoid this issue, type the command chkconfig netfs off in the XenServer host console before applying the upgrade. Unlike in Beta releases, the Windows Xen VSS provider is not installed by default and must be specifically installed in order to enable quiesced VM snapshots via the install-XenProvider.cmd script. See the Virtual Machine Administration Guide under the Windows section for more information on how to do this. The control domain uses slightly more memory in XenServer 5.0.0 relative to the previous releases, and automatically allocates approximately 100MB of host memory to the control domain upon upgrade. If you were using all available host memory prior to the upgrade, reduce the amount of memory used by one VM by 100MB before powering it on. Backup Citrix recommends that you take a host backup and/or a Status Report for each server prior to upgrade. See the Backing up and restoring XenServer hosts and VMs section in the XenServer Installation Guide for details. Citrix also recommends that you take a backup of the state of your existing pool using the pooldumpdatabase CLI command (see the XenServer Administrator's Guide). This allows you revert a partially complete rolling upgrade back to its original state without losing any VM data. NOTE: Because it is not possible to migrate a VM from an upgraded XenServer host to a XenServer host running an older version of XenServer, it may be necessary to shut down VMs if you need to revert the rolling upgrade for any reason. Remote database on iSCSI LUN for diskless hosts The capability of XenServer 4.1.0 HP Edition to persist pool-wide management state to a shared iSCSI LUN is not available in XenServer 5.0.0. A replacement capability will become available in an upcoming hotfix for XenServer 5.0.0. If you use this XenServer 4.1.0 feature, you must only upgrade directly to the upcoming hotfix, or contact HP Technical Support for more information before upgrading from XenServer 4.1.0. XenServer HP Edition Release Notes 7