5.6 Upgrading Oracle VM Server for x86 from Release 3.3.x or Between 3.4.x Errata Releases

To upgrade Oracle VM Server from Release 3.3.x or from one Release 3.4.x to another Release 3.4.y, you can:

  • Configure a server update repository and use the Oracle VM Manager Web Interface. This upgrade method is recommended and allows you to upgrade multiple Oracle VM Servers.

  • Create a bootable disc from the Oracle VM Server ISO file and perform the upgrade. You should use this upgrade method only if it is not possible to perform the upgrade from Oracle VM Manager.

  • Reinstall Oracle VM Server.

Before you attempt to upgrade Oracle VM Server to Release 3.4, you must prepare your environment. See Section 5.2, “Preparing to Upgrade Oracle VM”.

5.6.1 Upgrading Oracle VM Server Through Oracle VM Manager

Upgrading Oracle VM Server through Oracle VM Manager requires you to set up a Yum repository that:

  • Mirrors the contents of the ovm34_x86_64_latest ULN channel. This ULN channel contains the packages required to upgrade Oracle VM Server to Release 3.4.

    As an alternative to mirroring the ULN channel, you can make the Oracle VM Server installation media available over the network.

  • Can contain additional packages such as third-party Oracle VM Storage Connect plug-ins.

After you set up a Yum repository, you add it as a server update repository in Oracle VM Manager. You can then upgrade each Oracle VM Server through Oracle VM Manager.

5.6.1.1 Creating the Yum Repository

You must create the Yum repository on a system that is accessible through HTTP or HTTPS.

You must create the Yum repository either by creating a mirror of the ULN channel or by copying the content of the Oracle VM Server installation media, as follows:

Creating a mirror of the ULN channel

Set up your Yum repository to mirror the following ULN channel: ovm34_x86_64_latest

The ovm34_x86_64_latest ULN channel contains the packages required to upgrade Oracle VM Server to Release 3.4.

For more detailed information about setting up a Yum repository to mirror a ULN channel, see the following document: http://www.oracle.com/technetwork/articles/servers-storage-admin/yum-repo-setup-1659167.html

Using the Oracle VM Server installation media
  1. Download the most recent Oracle VM Server installation ISO file.

  2. Create a folder to mount the ISO file, for example:

    # mkdir /tmp/ovs-mount
  3. Mount the ISO file, for example:

    # mount -o loop OVS-3.4.1.iso /tmp/ovs-mount
  4. Create a directory for repository access using any appropriate HTTP server, for example:

    # mkdir /var/www/repos
  5. Copy the mounted ISO folder to the directory using -r for recursive and -p for preserve, for example:

    # cp -rp /tmp/ovs-mount/* /var/www/repos/
  6. Check that the repository is accessible. You should access the repository on a different system, such as an instance of Oracle VM Server. To ensure the repository is accessible, download a small file such as repomd.xml as follows:

    # wget http://example.com/repos/Server/repodata/repomd.xml
Tip

Temporarily serve your repository with the Python SimpleHTTPServer module, as in the following example:

# cd /var/www
# python -m SimpleHTTPServer 80

5.6.1.2 Including Additional Packages

You can include additional packages for Oracle VM Server, such as a third-party Oracle VM Storage Connect plug-in, in the Release 3.4 update repository. These packages are then included in the upgrade for Oracle VM Server.

Note

Any additional packages that you add to the repository must be compatible with Oracle Linux 6.

Tip

If you are upgrading an Oracle VM Server that has unsigned packages installed, you should create a separate Yum repository where these packages can be hosted. When you add the repository to Oracle VM Manager as a server update repository you must ensure that the Package Signature Type option is set to None for this repository. This prevents an upgrade from failing due to unsigned packages that are not part of the base Oracle VM Server installation repository.

To add packages to the Yum repository, do the following:

  1. Download the packages from the appropriate vendors.

  2. Copy the packages into the Server/Packages directory in the Oracle VM Server 3.4 Update Repository, for example:

    # cp osc-sun7k.rpm /var/www/repos/Server/Packages/
  3. Change directory so that you run the following commands from the root, for example:

    # cd /var/www/repos/Server
  4. Find the repository configuration file:

    # find ./ -name "*comps-ovs-core.xml"
    ./repodata/3bbd98ef14e1e62734b8df6360825010001323218736-comps-ovs-core.xml
  5. Use the filename for the repository configuration to recreate the repository:

    # createrepo -g ./repodata/3bbd98ef14e1e62734b8df6360825010001323218736-comps-ovs-core.xml ./

5.6.1.3 Adding Server Update Repositories in Oracle VM Manager

After you set up the Yum repository, you must add it in the Oracle VM Manager Web Interface.

  1. Log in to the Oracle VM Manager Web Interface.

  2. Either create a global server update group or a server update group for a specific server pool, as follows:

    Creating a global server update group

    1. Select the Reports and Resources tab.

    2. Select the Server Update Groups subtab.

    3. Expand the Server Update Groups folder and then select GlobalX86ServerUpdateConfiguration.

    4. Expand the Server Update Groups folder, select GlobalX86ServerUpdateConfiguration, and then select Create New Server Update Repository.

    5. Create the server update group as described in Table 5.4, “Oracle VM Server 3.4 Update Repository.

    Creating a server update group for a specific server pool

    1. Select the Servers and VMs tab.

    2. Expand the Server Pools folder and then select an appropriate server pool.

    3. Edit the server pool and select the Override Global Server Update Group option and then select OK.

    4. Select the Server Update Repositories perspective and then select Create New Server Update Repository.

    5. Create the server update group as described Table 5.4, “Oracle VM Server 3.4 Update Repository.

The following table describes the fields you need to specify to create a server update repository:

Table 5.4 Oracle VM Server 3.4 Update Repository

Field

Value

Notes

Name

3.4_ovs_repo

Specify a meaningful name for the server update configuration.

Repository Name

3.4_ovs_repo

Specify a meaningful name for the server update repository.

URL

http://example.com/repos/Server

Substitute this URL with the URL to your repository.

Enabled

Yes

This repository must be enabled.

Package Signature Type

GPG or None

If you want to verify the validity of packages provided by the repositories, set the signature type to use a GPG key. Alternatively, use NONE if there is no verification required.

Package Signature Key

http://example.com/repos/RPM-GPG-KEY-oracle

If you opted to verify the validity of packages provided by the repository, provide the verification signature for the repository. Substitute this URL with the URL to the verification signature for the repository. Note that this should be the GPG key provided for the Oracle Linux 6 repository.


For more information, see the following topics in the Oracle VM Manager User's Guide:

5.6.1.4 Upgrading Servers from Oracle VM Manager

After you set up the Yum repositories with the content to upgrade Oracle VM Server to Release 3.4 and create the server update repository, you can perform the upgrade from the Oracle VM Manager Web Interface, as follows:

  1. Log in to the Oracle VM Manager Web Interface.

  2. Select the Servers and VMs tab.

  3. Expand the Server Pools folder and then select an appropriate server pool.

  4. Select the Servers perspective.

    The Update Required column in the Servers perspective indicates if an update is available for each server within the server pool.

  5. Select each instance of Oracle VM Server that you want to update and then select Update Server.

  6. Click OK when prompted to confirm the server upgrade.

    Each Oracle VM Server is placed into maintenance mode and then upgraded. Any virtual machines running on an instance of Oracle VM Server are automatically migrated to another Oracle VM Server when it is put into maintenance mode. When the update is complete the Oracle VM Server is restarted and remains in maintenance mode.

    Note

    In certain cases, the automatic virtual machine migration may fail when the Oracle VM Server is placed into maintenance mode. For more information on the maintenance mode, see Edit Server.

  7. Edit each instance of Oracle VM Server to take it out of maintenance mode when the upgrade is complete.

5.6.2 Upgrading Oracle VM Server Using the ISO File

To upgrade the Oracle VM Server using the Oracle VM Server ISO file:

  1. Burn the Oracle VM Server ISO file to a bootable disc.

  2. Start the Oracle VM Server installer. The installer initially prompts you to test the installation media, configure the language and keyboard settings, and accept the EULA.

    For more information about starting the installer and the initial installation screens, see Section 2.1.2, “Installing Oracle VM Server From a DVD-ROM”.

  3. Proceed through the initial installation screens. When the installer detects the existing Oracle VM Server installation, the System to Upgrade screen displays.

System to Upgrade

On the System to Upgrade screen, do the following:

  1. Select Oracle VM Server 3.x (disk) to upgrade the existing installation.

    Select OK and press Enter.

Upgrade Boot Loader Configuration

On the Upgrade Boot Loader Configuration screen, do the following:

  1. Select one of the following:

    • Update boot loader configuration to update the existing boot loader.

    • Skip boot loader updating to make no changes to the boot loader and maintain your current configuration settings.

      Note

      If kdump settings were manually defined in the GRUB configuration before the upgrade, selecting this option ensures that these configuration settings are maintained after the upgrade.

  2. Select OK and press Enter.

Package Installation and Finishing the Upgrade

After you specify the options for the Oracle VM Server upgrade, the installer performs a dependency check and then begins the upgrade process. A progress bar displays the status of the package installation. The Finishing upgrade screen then displays.

When the upgrade is finished, the Complete screen displays. Do the following to complete the upgrade:

  1. Remove the Oracle VM Server installation disc from the drive.

  2. Select Reboot.

After Oracle VM Server reboots, the console displays.

The Oracle VM Server upgrade is complete.

A log of the install is located in /root/upgrade.log. If the upgrade is not successful, review this log file to identify any issues.

5.6.3 Reinstalling Oracle VM Server

To upgrade Oracle VM Server from Release 3.3.x to Release 3.4, you can reinstall Oracle VM Server.

Important

Reinstalling Oracle VM Server deletes all configuration settings.

Reinstall Oracle VM Server as follows:

  1. Migrate all virtual machines off the Oracle VM Server that you plan to upgrade. See Migrate or Move Virtual Machines in the Oracle VM Manager User's Guide.

  2. Unpresent all repositories from the Oracle VM Server. See Present or Unpresent Repository in the Oracle VM Manager User's Guide.

  3. Delete the Oracle VM Server from Oracle VM Manager. See Delete Server in the Oracle VM Manager User's Guide.

  4. Reinstall the Oracle VM Server with the Release 3.4 installation media. See Section 2.1.2, “Installing Oracle VM Server From a DVD-ROM”.

  5. Discover the Oracle VM Server with Oracle VM Manager and add it to the appropriate server pool after the installation is complete. See Discover Servers in the Oracle VM Manager User's Guide.

  6. Re-configure the Oracle VM Server environment to restore the settings for networks, storage, repositories, and so on.

  7. Test the networking and storage connections of the Oracle VM Server that you reinstalled. You should confirm that failover redundancy and performance function correctly. You should also perform some testing on virtual machines and applications on the Oracle VM Server to ensure that they also function as expected. If you can confirm that the reinstalled Oracle VM Server is working correctly and no performance issues exist, you should then proceed with the incremental upgrade and verification of other Oracle VM Server instances.