5.4.2 Upgrading Oracle VM Server using the UpgradeServers.py Script

Oracle VM Manager Release 3.3 includes a script that assists with the batch upgrade of multiple Oracle VM Servers. This script is required for the upgrade of servers from a release prior to Release 3.3, but is also the preferred method of upgrading servers through Release 3.3 errata updates, since it is capable of performing batch upgrades for whole server pools, or for lists of specified servers. The script is located on the Oracle VM Manager host at:


The script requires that the necessary Yum repositories are set up ahead of time with specific names. This set up is described in Section 5.4.1, “Preparing to Upgrade Oracle VM Servers from Release 3.2 or Earlier”. If you intend to use this script to perform a batch upgrade of your SPARC servers, make sure that the IPS repositories are properly set up, as described in Section 5.5, “Upgrading Oracle VM Agent for SPARC”.

When the script runs, the normal maintenance mode work is performed automatically in the background, so that virtual machines are automatically moved around to allow servers to be upgraded and rebooted, while minimizing potential downtime.

The script maintains a log file in the directory from which the script was run; it is named UpgradeServers.log. This file may be useful to debug upgrade issues.

Oracle VM Servers cannot be upgraded, using this script, if:

  • Oracle VM Manager is not running or has not yet been upgraded.

  • The Oracle VM Server is not owned by the Oracle VM Manager performing the upgrade.

  • The Oracle VM Server is not running.

  • The Oracle VM Server is at a version greater than or equal to the current Oracle VM Manager version.

  • The Oracle VM Server for SPARC version is prior to Release 3.3.

  • The Oracle VM Server has a critical error.


UpgradeServers.py [ -h | --help | ? ] [ { --host-name | -H } host ] [ { -P | --port } port ] [ { -u | --user-name } user ] [ { -l | --pools } pool ] [ { -v | --servers } server ] [ --noprompt ]


Using the UpgradeServers.py script with no options prompts you to enter the username and password for an instance of Oracle VM Manager on the localhost.

The following table shows the available options for this tool.



[ -h | --help | ? ]

Display the UpgradeServers.py command parameters and options.

{ --host-name | -H } host

The host name of the server running Oracle VM Manager. Usually, this script is run on the Oracle VM Manager host, so this option is not required. The default is localhost.

{ -P | --port } port

The port number for the Oracle VM Manager instance. The default is 7002.

{ -u | --user-name } user

The username to log into the Oracle VM Manager instance. You are prompted for the password for this credential.

{ -l | --pools } pool

The names or IDs of any server pools to upgrade. To specify multiple server pools, enter them in a comma separated list, with no spaces.

{ -v | --servers } server

The names or IDs of any Oracle VM Servers to upgrade. To specify multiple Oracle VM Servers, enter them in a comma separated list, with no spaces.


Do not prompt to continue the upgrade. If packages are missing, the upgrade exits immediately, see Section, “Non-native Packages”. Otherwise, the upgrade continues without prompting.

Example 5.2 Upgrading Oracle VM Servers in a server pool

Upgrading all Oracle VM Servers in two server pools, named pool1 and pool2 and prompting for required options:

$ ./UpgradeServers.py -l pool1,pool2

Example 5.3 Upgrading Oracle VM Servers

Upgrading three Oracle VM Servers named server1, server2 and server3, and suppressing all prompts (except errors and the password prompt):

$ ./UpgradeServers.py -v server1,server2,server3 -noprompt

Example 5.4 Upgrading Oracle VM Servers on a remote Oracle VM Manager

Upgrading Oracle VM Servers on a remote host that has an Oracle VM Manager instance:

$ ./UpgradeServers.py -H ovmmanager.example.com -u admin -v server1,server2,server3