Installation guide

Maintenance Procedures
24
The following procedure describes how to install the current version of the XenServer Host over
an existing installation of XenServer Host 3.2.0
When upgrading from version 3.2.0 to the current version, be aware of the following:
any custom RPMs which you might have installed on the XenServer Host control domain will
not be preserved
existing Windows VMs will need to have the paravirtualized device drivers reinstalled
Procedure B.5. To upgrade XenServer Host from version 3.2
1. Perform an orderly shutdown on the VMs hosted on the XenServer Host.
If any of your VMs are in the in the Suspended state, Resume them first, and then perform
an orderly shutdown on them too.
2. Reboot the XenServer Host, and boot from the 4.0.1 Installation CD.
3. The installation script will identify the older version and prompt you whether you want to
install over the existing 3.2 installation and preserve VMs. Select OK to proceed with the
installation.
4. Follow the rest of the installation procedure as described in the 4.0.1 installation guide.
5. Run XenCenter and connect to the upgraded XenServer Host.
6. To upgrade the drivers for a Windows VM, select the "Install Tools" menu option and open
its console. Run the xensetup.exe installation program to upgrade your paravirtualized
drivers. When finished, reboot the VM.
To upgrade the kernel and guest utilities for Linux VMs, follow the instructions in the XenServ-
er 4.0.1 Virtual Machine Installation Guide.
Repeat for all other Windows VMs.
Note that there is no direct upgrade path to the current version from 3.2. You must first upgrade
to 4.0.1, and then proceed to the next version. This will ensure that your VMs are preserved
correctly.
B.6. Upgrading VHD files from version 4.0.1
VMs ext3 and nfs storage repositories, which are stored in the Microsoft Virtual Hard Disk (VHD)
format under the 4.0.1 version of XenServer, have a free space bitmap written in with the wrong
byte order. Version 4.1 provides an upgrade utility vhd-update, located in /usr/sbin/.
The command
vhd-update -f <filename>
copies all bitmaps in filename to filename.journal, then writes all bitmaps, transformed appropri-
ately, from filename.journal to filename, and finally deletes filename.journal.
If the update is interrupted for any reason, it can be resumed by running: