4.7 Running Oracle VM Manager as a Virtual Machine

The Oracle VM Manager does not necessarily have to run on a separate physical server in your environment. You can save on your resources by turning theOracle VM Manager into a virtual machine. As a result, it benefits from all the typical advantages of virtualization: hardware consolidation, high availability, live migration and so on. Because the Oracle VM Manager is not tied to one physical server, it leaves more physical resources for other applications, and at the same time it can be hot-cloned, backed up and migrated without downtime to other hardware when server maintenance is required.


If you intend to virtualize Oracle VM Manager, you should ensure that it does not run on top of the same platform that it is managing. This can cause problems if the virtual machine where Oracle VM Manager resides happens to go down, as you are not able to easily restart the virtual machine. Typical deployments where the Oracle VM Manager is virtualized have two distinct Oracle VM environments configured, where Oracle VM Manager runs on a virtual machine in each environment to manage the other.

The procedure to turn Oracle VM Manager into a virtual machine starts with a regular installation, either on a physical server or using a virtualization tool such as Oracle VM VirtualBox. Using this installation you set up the bare minimum to run a virtual machine: one Oracle VM Server, one NFS storage server and the default management network should suffice. Once the environment is up and running, you install a virtual machine on your environment and let it take over the role of the Oracle VM Manager instance that it should replace. This section explains the steps to reach that final result.


This procedure is not intended for the reconfiguration of an Oracle VM environment in use. If you wish to run Oracle VM Manager as a virtual machine, run this procedure as part of the setup, with a minimal install, before any significant configuration has taken place.

To run Oracle VM Manager as a Virtual Machine in the virtualized environment:

  1. In environment A, install Oracle VM Manager on a physical server, according to the instructions in Section 4.4, “Installing Oracle VM Manager”.

  2. Discover at least two Oracle VM Servers for your environment, create a clustered server pool, use the default management network and set up the minimum storage required: a server pool file system and a storage repository for the VM resources. To do so, follow the instructions in the Oracle VM User's Guide.

  3. Create a new virtual machine that complies with the Oracle VM Manager hardware requirements as described in Section 4.3.1, “Hardware Requirements”. Make sure that the new virtual machine has HA (high availability) enabled.

  4. Install the operating system (Oracle Linux) and make sure that the virtual machine complies with all software requirements for Oracle VM Manager, as described in Section 4.3.2, “Software Requirements”.

  5. On this new virtual machine, install Oracle VM Manager according to the instructions in Section 4.4, “Installing Oracle VM Manager”. Run the installer with the --uuid option to install this new Oracle VM Manager instance with the same UUID as one running on a physical server in environment B.


    If you intend to run the Oracle VM Manager database on a separate virtual machine, make sure that the database is up and running before you install the Oracle VM Manager virtual machine.

    • Copy the UUID of the Oracle VM Manager instance in environment B from the file /u01/app/oracle/ovm-manager-3/.config.

    • After mounting the Oracle VM Manager install dvd on the file system of your virtual machine, run the installer as follows: ./runinstaller.sh --uuid <original_manager_uuid>. Select your preferred installation type, as you would with a regular install.

  6. Stop the Oracle VM Manager instance in environment B.

  7. From the new Oracle VM Manager virtual machine in environment A, rediscover the Oracle VM Servers and storage from environment B. Refresh the storage repository to make sure that all your VM resources reappear for environment B.

Oracle VM Manager is now running as an HA VM in environment A, to manage Oracle VM deployment running in environment B. If the Oracle VM Server hosting the Oracle VM Manager VM fails, the VM will be brought up automatically on a different Oracle VM Server in environment A, and you will continue to be able to access it to manage environment B.

At this point, the Oracle VM Manager instance responsible for environment A is still running on a physical server. You can just as equally create a virtual machine in environment B, and set up a new Oracle VM Manager instance running with the same UUID to take over this responsibility. In this way, the two Oracle VM Manager instances can take advantage of the HA functionality provided by a clustered server pool. Each Oracle VM Manager instance runs in one environment to manage the other.