Chapter 5 Upgrading Oracle VM

Table of Contents

5.1 Upgrading Overview
5.2 Upgrading Oracle VM Manager
5.2.1 Post-upgrade Steps
5.3 Upgrading Oracle VM Server for x86
5.3.1 Upgrading Oracle VM Server Using a Yum Repository
5.3.2 Upgrading Oracle VM Server Using the CD
5.3.3 Upgrading Oracle VM Server Using Multipath SANs

Oracle VM Release 3.x is not backwardly compatible with Oracle VM Release 2.x. If you are using Oracle VM Release 2.x you cannot upgrade to Release 3.x. You must reinstall your Oracle VM Servers and Oracle VM Manager. You can, however, reuse your virtual machine templates from Oracle VM Release 2.x by importing them into Oracle VM 3.x.

For information on repository migration from Oracle VM Release 2 to Oracle VM Release 3, see the My Oracle Support website at: https://support.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1366216.1

There is no provision for upgrading releases where an Oracle Database XE has been used as a backend repository for Oracle VM Manager. Oracle VM Manager no longer supports Oracle Database XE as a backend repository and there is no way to migrate to the new MySQL database backend supported in Oracle VM 3.2. If you are willing to migrate your Oracle Database XE to a supported Oracle Database such as Oracle Database SE or Oracle Database EE, you will be able to perform an upgrade using the Custom installation process.

The upgrade procedures discussed in this chapter refer to upgrades between Oracle VM 3.x releases, for example, upgrading from Oracle VM Release 3.0.1 to 3.0.3, or from Release 3.0.3 to 3.1.1 This chapter outlines the upgrade process for all the components of Oracle VM when upgrading to minimize down time and make sure the upgrade process is performed in the correct order.

Note

Generally, there is no need to perform incremental upgrades between releases; that is, you can skip releases as long as you upgrade from Oracle VM 3.x to 3.x. For example, you can upgrade from Release 3.0.2 to 3.1.1. The exception to this is if you are running Oracle VM Release 3.0.1, where you must first upgrade to Release 3.0.2 or 3.0.3 before upgrading to Release 3.2. Upgrades from Release 3.0.3 to Release 3.2 and from Release 3.1.1 to Release 3.2 have been successfully tested and are fully supported.