Citrix XenServer Upgrade: 5.0 to 5.507 Jul
The Mission:
Upgrade three XenServer 5.0.2 hosts in a single Pool with an iSCSI attached Storage Array to the new and improved XenServer 5.5.
The Process:
The first thing we did was install the XenCenter 5.5 Client and, just to be sure, went on to apply the 5.0.3 update (aka update 3) to all of the hosts.
After that it requires a reboot (of course). To facilitate this, we were glad we had multiple hosts in the same pool as we were now able to utilize the ever popular XenMotion to ‘shuffle’ my VMs around, reboot a host, ‘shuffle’ the VMs again, reboot the next host, etc. This worked like a charm.
After we completed Update 3, we then cleared off the Primary Host (denoted by being the top-most Host of the Pool in XenCenter) using XenMotion. Using a browser (IE needed unfortunately – alternative with FireFox is IETab Plugin) we connected to each of the HP iLOs from our management server (physical windows host), mounted the XenServer 5.5 Disc 1 in the iLO virtual DVD-ROM drive and rebooted the physical XenServer host. The iLO also equips you with an ActiveX remote KVM for just this purpose, thankfully. We proceeded with the XenServer installation and even installed the Linux Pack (second ISO image… dismount the XenServer ISO and then mount the Linux Pack ISO all from the Virtual Drive functions in the iLO). Once the primary is completed, here is a catch: if you XenMotion/Launch a VM on 5.5, you CANNOT migrate it off to an older version host so plan carefully. That being said, we XenMotioned our VMs around several times (yes this does hurt performance on the VMs if you are overloading your hosts… see Noticable Issues) and completed all of the upgrades.
Now that all of the Hosts were done and our VMs were still running, we scheduled outage windows for each set of subsystems to allow us time to upgrade the XenTools on each VM (all 31 of them… yes 31 VMs on 3 hosts). No, there is not a way currently to mass update all VMs, so you have to do them one at a time. Watch out here too… see Noticable Issues.
All in all it wasn’t a horrific upgrade process, thankfully we have an excellent team that works well together under pressure.
Proof Positive – XenMotion keeps VMs accessible:
To provide proof positive that I was able to keep Citrix XenApp sessions running while doing this all, I logged into our HostMyIT (Hosted Messaging and Collaboration / Virtual Office) system prior to any work. My session stayed running throughout the entire process using Outlook 2007 as a published application. However, new logins eventually stopped… see Noticable Issues for an explaination.
Noticeable issues:
1. One of our Windows Active Directory Servers lost connection to our NetApp SAN (we use CIFS for the file shares) and this caused file access denials. The simple solution (after wracking our brains) was to redo the NetApp CIFS Setup routine. Instant access restored.
2. XenTools updates: Caused one of our iSCSI LUNS (used for Exchange’s Database) to be overmapped by the XenServer VCD-ROM. We had to remap the CD-ROM drive letter to J:, reconnect the iSCSI LUN to the Exchange Server and map its drive letter back to D:. Chances are, you will only hit this one if you use iSCSI LUNS mapped to lower drive letters.
3. Overloading your Physical Hosts with too many VMs will be seen by users as a noticable slow down occurs. Let your users know several thousand times prior to upgrade if you will be doing this while live.
If you are considering/planning a XenServer upgrade, let DedicatedIT be your Team, give us a call (561.491.5725) or drop us a line.
The issues enclosed in this post are just the ones we ran into in this specific upgrade. There are always snags. As I said before, it’s not a horrific upgrade process, but it is nice to have that same great team by your side that we do internally.


