My Favorites

Close

Please to see your favorites.


Upgrading a XEN OES2 virtual machine

This document (7002177) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 10 Service Pack 4 XEN Host
SUSE Linux Enterprise Server 11 Service Pack 1 XEN Host
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 1
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 2
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3

Situation

Need to update/upgrade a XEN OES2 virtual machine to OES2 SP1
Need to update/upgrade a XEN OES2 virtual machine to OES2 SP2
Need to update/upgrade a XEN OES2 virtual machine to OES2 SP3

Resolution

Before you begin:
  • Back up the virtual machine's (VM) image/disk now!!  A failed update/upgrade will leave the VM un-recoverable.
  • Apply all current updates to the OES2 VM, re-start, and verify functionality.
  • Update the SLES XEN Host to a minimum of SLES 10 SP4 or SLES 11 SP1 & apply all updates.
  • Re-boot the XEN Host and verify that all VM's run.
  • Prepare the VMs operating system environment. Review the general documentation regarding known issues when updating OES2. i.e. OES servers with a NSS partition on the system device require special handling.TID 7002118:  How to upgrade to OES2 SP1 is a good place to start.
  • Set up the appropriate SLES 10 SPx & OES2 SPx media as network installation sources (for an "offline" upgrade).
After completing the tasks outlined above, proceed as follows:

Beginning with OES2 SP2 the option for an online upgrade exists.  The VM must be at OES2 SP1 and subscribed to both OES & SLES update channels to use this option. 
Be aware that this method has proven subject to failure due to Internet or back-end update server issues.  If the VM is backed up there is nothing to lose.  Just make sure to choose the "Move to OES2 SPx" option and NOT the "Move to SLES SPx option if you choose this method.

See Section 5.4.5, Using the Patch Channel to Upgrade (Online) in Novell Documentation for details.

Otherwise, proceed as follows for an "Offline" upgrade:

On a SLES 11 SP1 Host:

1.  Shut down the VM to be upgraded.
2.  BACK IT UP?  Again, a failed upgrade will require a re-install of the VM.

3.  Open Virtual Machine Manager
4.  Select "Create a Virtual Machine"
5.  Select the "I need to upgrade an existing operating system." option .
6.  Select "Novell Open Enterprise Server 2 (Linux)"
5.  Select the correct "Managed Virtual Machine"& the path to the network installation source for the SLES 10 SPx media 
6.  Follow the instructions in TID 7002118:  How to upgrade to OES2 SP1  starting at section 5.4.3, selecting the Installation Mode Options to complete the installation.  Note:  Using physical media is not an option for the OES2 SPx add-on product source in an OES2 VM.  Point to a network installation source.

On a SLES 10 SP4 Host:

Method 1:  (easiest)
As root user, run vm-install --upgrade.  Then follow the steps outlined for a SLES 11 SP1 host beginning at step 4.


Method 2:  (hardest)
See the online Novell Documentation @  
Section 10.5: Upgrading an OES 2 Linux VM Guest to OES2 SP3

Method 3:  (unsupported)
1.  Shut down the VM to be updated.
2.  View or print the VM configuration file located at etc/xen/vm/vm_name.
3.  On the Host, use Virtual Machine Manager to create a new virtual machine.
4.  Choose the default selection to install an operating system.  Select Novell Open Enterprise Server 2 (Linux) as the base configuration.
5.  In the Summary screen, give the VM a temporary name.  Then modify the following settings for the new virtual machine to be the same as the settings specified in the original VM’s configuration file. 
  •        Network MAC address (under the Network Adapters section)
  •        Memory size (under the Hardware section)
  •        Virtual disk size (under the Disks section)
6.  While in the Disks section, make sure to select or specify the virtual machine's already-created disk or disk image as the disk for this temporary VM. For example, if the OES2 virtual machine was using /var/lib/xen/images/oes2/disk0 as its disk, the temporary virtual machine should specify the same disk.  Do not add any additional disks at this time.  Only the disk containing the system files.
7.  Now open the Operating System Installation section and specify the virtual machine operating system installation source as the SLES 10 SPx network install source.
8.  While in the Operating System Installation section, add the following argument in Additional Arguments:
      root=/dev/xvda2
where /dev/xvda2 is the path and drive designation for the partition that contains the virtual machine's /  (root) directory and files.
9. Click OK to create the temporary virtual machine and start the SLES 10 SPx  & OES2 SPx installation program.
  •       A new window displaying the installation program will open.
  •       If the new window does not display, select the temporary virtual machine in Virtual Machine Manager and click Open.
10. Follow the instructions in TID 7002118:  How to upgrade to OES2 SP1  starting at section 5.4.3 Selecting the Installation Mode Options to complete the installation.  Note:  Using physical media is not an option for the OES2 SPx add-on product source in an OES2 VM.  Point to either a network installation source.
11. Once the update has completed, shut down this temporary vm.
12. In virt-manager, open the updated vm image using the original vm name.  Then delete the entry for the temporary vm used to perform the update.  Note:  Deleting an entry in virt-manager does not delete the image associated with it;  It only deletes the configuration information in the xenstore database.

At this point a functional, updated VM should exist.  Do not delete the actual back-up image that was created until a full validation/test of the updated VM has been completed.  If the update has failed for any reason, the original image can always be used either to attempt another update or to run the original VM until the problem can be sorted out.

Prior to re-staring the vm, verify the dom0 (Host) has been fully updated.  The host computer must be running software that is at, or more recent than, the software planned for the virtual machine update.  If fully virtualized (FV)  VMs are part of this XEN system, update the VMDP drivers for each FV VM prior to re-booting the XEN host.

Additional Information

If the graphical environment is not available (virt-manager) the upgrade can be completed using the basic concepts outlined in TID 3564240: XEN:  How to boot SLES para-virtual DomU's into the Rescue System for disaster recovery.  DISCLAIMER:  If attempting this method it is imperative that a backup of the original image is created for recovery purposes.  This TID will be updated with appropriate steps for a "manual" updated at a later time.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7002177
  • Creation Date:12-DEC-08
  • Modified Date:30-APR-12
    • NovellOpen Enterprise Server
    • SUSESUSE Linux Enterprise Server
      SUSE Linux Virtual Machine Driver Pack

Did this document solve your problem? Provide Feedback