Latest Entries »

When working with Oracle databases, it is highly recommended to use physical volumes attached to your virtual machines instead of shared virtual disks due to degraded performance when using virtual disks. Unfortunately, within the Oracle VM Manager you cannot add physical volumes to your virtual machine unlike shared virtual disks. In order to add physical disks to a virtual machine you must modify a VM’s vm.cfg file located under /OVS/running_pool/<vm_name>/. This directory contains a System.img file, a vm.cfg file, and a vm.cfg.orig file. An example of a basic vm.cfg file created by the OVM Manager looks like the following:



One of new distinct features that you will find within Oracle VM Manager 2.2 is the ability to prioritize your CPU usage across your different VMs running within your Oracle VM host. Instead of writing an article on the new feature set, I found a great oracle vm blog article written by Honglin Su that describes just that. A link to the blog can be found at

Before creating virtual machine, one must create a server pool. Creation of the server pool can be found on my blog via this post or search via my blog  for “Creating a Server Pool via Oracle VM Manager”.

The steps on creating a Virtual Machine are as follows:

1. Select the ‘Virtual Machines’ tab and click ‘Create Virtual Machine’ located on the right corner.

2. Select the appropriate creation method to be used to create your virtual machines. For the purposes of this blog, we will be selecting the ‘Create from installation media’ radio button and click Next.

3. Select the appropriate Server Pool to be used and modify the ‘Preferred Server’ section from Auto to Manual if this particular virtual machine needs to run on a particular server located within your server pool. If not, please leave Auto as the default and click Next.
NOTE: Changing from Auto to Manual will disable high availability for that particular virtual machine, not recommended.

4. Select the appropriate virtualization method for your particular VM. Within our best practice configuration we used the Paravirtualized virtualization method for optimal performance.
NOTE: When using the ‘Fully Virtualized’ method, you must first register and activate your ISO Files located under the Resources -> ISO Files section. The ISO files can be registered using an external source such as HTTP server or you can copy each of your ISO files to the /OVS/iso_pool/<name_of_iso_dir>/ and select the appropriate server pool to discover and register these ISO files.
NOTE: When using the ‘Paravirtualized’ method, please make sure to extract all of the files found within your OS distribution ISOs and place them within your HTTP or FTP server.

5. Enter the virtual machine information with the specifications required for your particular VM and click Next.

6. Verify that the information is correct and click Finish.

Creation of virtual machines is the most elemental function you will use within your Oracle VM Manager. However, in order to create virtual machines, a server pool must be created  to host your virtual machines. A server pool can be thought of as a container in which to hold one or more physical servers. Once a server pool is created, virtual machines can be hosted by one of the physical servers within the server pool. Virtual Machines by default are hosted in a round-robin fashion making sure the servers within your pool are properly load balanced. However, if there is a particular need for a VM to be hosted on a particular server within your server pool you can manually set this feature using the ‘Preferred Server’ section when creating a virtual machine. Manually assigning a VM to a particular server is not recommended because you will lose high availability.

The steps to create a Server Pool are as follows:


Oracle VM uses Oracle VM Server (OVS) repositories to store resources such as virtual machines, templates, ISO images, and shared virtual disks. Once a storage repository has been created and initialized, it will create storage repository directories to store these resources. One of these sub-directories is the running_pool directory which will contain your virtual machines. Via your Server Pool Master you will create an OVS repository following the steps below.


The Oracle® Cluster File System (OCFS2) is the file system used for setting up the Oracle® VM Server (OVS) repository partition for shared disk access across all your OVM Server nodes. OCFS2 uses a heartbeat mechanism across all your OVM nodes via the network to maintain data consistency.

In order to setup your OCFS2 repository, the setup of the o2cb cluster service must be done on all your OVM Servers. From each node, run the following setup script using the command and insert the following inputs:

service o2cb configure

Load O2CB driver on boot (y/n) [y]: y
Cluster stack backing O2CB [o2cb]: o2cb
Cluster to start on boot (Enter “none” to clear) [ocfs2]: ocfs2
Specify heartbeat dead threshold (>=7) [100]: 100
Specify network idle timeout in ms (>=5000) [30000]: 30000
Specify network keepalive delay in ms (>=1000) [2000]: 2000
Specify network reconnect delay in ms (>=2000) [2000]: 2000

 Oracle VM’s architecture provides the same native bonding module that is found in all Enterprise Linux 5.x distributions. Although bonding has several different modes which include modes such as the round robin policy and load balancing policy, the active-backup policy (mode 1) is the preferred mode for Oracle RAC interconnects. The active-backup policy has only one active slave and the remaining are passive slaves. One of the other slaves will become active, if and only if, there is a failure with the current active slave within the bond.

In order to setup bonding within the OVM environment, the first step is to stop any guest VMs that are currently running. Once you have stopped all guest VMs, you must stop all network bridges within your OVM environment using the following command

/etc/xen/scripts/./network-bridges stop
The network-bridges script controls the creation of your network bridges for each physical NIC. The default behavior of OVM is to create a xen bridge for each physical NIC.
In the following example, we will start configuring our bond0 device and enslave two NIC adapters (eth1 and eth2) to our bond device.