Cool Solutions

Upgrade of OES Server on Citrix XenServer


June 27, 2011 2:52 pm





Karthik Ashok Kumar
Sakila Ravi

This article aims to describe the Media Upgrade of OES 2 SP2 to OES 2 SP3 on Citrix XenServer.


Note the vm-uuid, vdi-uuid and vbd-uuid of the OES 2 SP2 VM before the upgrade.

xe console-list – Lists the vm-uuid for all the VM guest on the XenServer.

xe vbd-list vm-uuid=<valid_vm_uuid>

The vbd-list command displays both the VBD and VDI UUIDs.

Media Upgrade to OES 2 SP3 on Citrix XenServer

  1. Shutdown the OES 2 SP2 VM and backup the entire VM within XenServer

    Run the command in XenServer

    xe vm-export vm=<vm_uuid> filename=<backup>

    vm-export – Export the specified VMs (including disk images) to a file on the local machine.

    vm_uuid – The unique identifier/object reference of the VM this console is open on.

    This backup also backs up all of the VM’s data. When importing a VM, you can specify the storage mechanism to use for the backed up data.

    In the Screenshot, CIFS share has been taken as the storage location to save the backup file of the VM.

    Click the Logs tab for the backup progress and Event log details.

  2. Create a new Xenserver OES 2 SP3 VM and connect it to SLES-10-SP3_x86_64 ISO
    NOTE: This is done so that the VM is considered first boot and will therefore boot the attached install media in a mode that can update the existing paravirtualized VM, same parameters as original and any sized disk . Do not start the VM on completion of the wizard.
  3. Detach the storage virtual disk from the OES 2 SP2 VM.
    • In XenCenter select the VM’s Storage tab
    • For each VDI to be moved, select the VDI and click the Detach button

    This step can also be done using the vbd-destroy command.

    xe vbd-destroy uuid=<uuid_of_vbd>
  4. Attach the storage from the OES 2 SP2 VM to the new VM OES 2 SP3
    • Within XenCenter select the VM’s Storage tab
    • Click the Attach button and select the VDIs from the local storage

    This step can also be done use the -create command.

     vbd-create vm-uuid=<uuid_of_the_vm> device=<device_value>
     vdi-uuid=<uuid_of_the_vdi_the_vbd_will_connect_to> [bootable=true] [type=<Disk | CD>] [mode=<RW |RO>]


    xe vbd-create vm-uuid=2580d0a1-7209-f3d1-f780-4150a11ca0af device=1 vdi-uuid=a73c7d69-49cc-43ae-a853-ae005703a416 bootable=true type=disk mode=rw

    The VM will not boot yet as it complains about too many bootable disks. Fix that by making the disk not bootable using:

    #set the disk to not be bootable:
        xe vm-disk-list vm=OES2SP3
    #(get the VDI uuid)
         xe vdi-param-list uuid=<VDI uuid>
    #(get the VBD uuid)
        xe vbd-param-set uuid=<VBD uuid> bootable=false
  5. Start the OES 2 SP3 VM and proceed with the Upgrade.
  6. After Stage1 of the Upgrade, if it fails to boot, execute the command and make the bootable as true on the Xencenter and proceed with stage2 of the Upgrade.
    xe vbd-param-set uuid=<vm-uuid> bootable=true
2 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 5 (2 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.

Tags: ,
Categories: Open Enterprise Server, Technical


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

1 Comment

  1. By:kjhurni

    One thing that’s missing in this article:

    After you install the OES upgrade (regardless of how you do it), the system needs to reboot into GUI mode in order to finish the installation (the GUI mode required for eDir setup).

    Since XENServer has no video card, the system cannot run in GUI mode, so that the installation never finishes properly.