Category: Oracle VM Manager

At times debugging certain Oracle VM or Oracle VM Manager related issues is quite challenging. In today’s article I’d like to discuss the different log locations to better assist those in trying to solve a particular issue.

I will start off by discussing the Oracle VM Manager 2.2. The Oracle VM Manager has three main log files all located under the /var/log/ovm-manager directory. These files are the db.log, oc4j.log, and the ovm-manager.log
Continue reading


In today’s Oracle VM Manager there is no way of extending the disk size of a guest VM. However, via this tutorial I will show you how to extend the .img file.

PLEASE NOTE: It is highly recommended to make a backup of the disktoExtend.img file prior to trying the steps below.

Let us assume we have an Oracle VM guest which contains 3 files. The three files are the following: System.img, disktoExtend.img, and vm.cfg. Our guest VM is running RHEL/OEL.

[root@OVMSERVER]# ll
total 22000640
-rw-r--r-- 1 root root 26847313920 Oct 13 10:28 disktoExtend.img
-rw-r--r-- 1 root root 11630545920 Oct 13 09:57 System.img
-rw-rw-rw- 1 root root 459 Oct 13 10:27 vm.cfg

Continue reading

Ever had your virtual machine show an incorrect status such as ‘Shutting Down’ and just stay in that status indefinately? Well there is some good news, it’s an easy fix. There are a couple reasons this can occur. First, if you stopped your virtual machine from the OVM server instead of the OVM Manager this could cause the OVM Manager and OVM server to be out of  ‘sync’ when reporting the status of your virtual machine. In other cases, it could be a bug between the communication of the OVM Manager and Oracle VM server. In either case there are a few options in solving your issue.

In OVM Manager 2.1.*, you will need to manually update the Oracle VM Manager database status of your guest virtual machine.
Login as ‘oracle’ into your OVM Manager and follow the steps below.

$ export ORACLE_HOME='/usr/lib/oracle/xe/app/oracle/product/10.2.0/server'
$ export ORACLE_SID=XE
$ ${ORACLE_HOME}/bin/sqlplus system/oracle@XE
$ SQL> update ovs.ovs_vm_img t set t.status='Powered Off' where t.img_name like '<MY_VM_NAME>';
$ SQL> commit;
$ SQL> quit;

In Oracle VM Manager 2.2 and above, the process is quite simple. Oracle has introduced the ‘Reset’ option which will set the virtual macine guest to its correct state.
The steps are as follows:
1) Click on the Virtual Machines tab found on the top left corner.
2) Select the radio button of the appropriate virtual machine that has the incorrect status displayed.
3) Click on the ‘More Actions:’ drop down box and select the option ‘Reset’
4) Click the ‘Go’ button for the reset to take place.

Once the ‘Go’ button is selected, the virtual machine will reset and display the appropriate virtual machine status.

Hope you enjoyed this article and feel free to post any comments our questions.


In today’s topic, I’d like to discuss the process of backing up and restoring your Oracle VM Manager. Since the Oracle VM Manager is used to manage all your virtual machines and virtual machine resources, I thought it would be a good exercise to discuss the step-by-step process on backing up and restoring the OVM Manager environment. It is crucial to make backups of your Oracle VM Manager to ensure that you don’t lose any data from the Oracle VM Manager repository database that could cause you a headache in having to actively restore each virtual machine to a new Oracle VM Manager, one by one (not a fun exercise). The good news is Oracle has made the backup-restore process quite easy. In the example below, I will be backing up my original Oracle VM Manager, and restoring the content from my old server it into a new server all that has a fresh install of Oracle VM Manager.

Continue reading

One of the tougher aspects of Oracle VM is deciphering how to debug errors found in the logs within the Oracle VM Manager. Today I’d like to discuss an issue I’ve come across when trying to create a server pool within the Oracle VM Manager. The bug specifically consisted of my Oracle VM Manager not correctly entering the proper IP information within the /etc/hosts file of my Oracle VM Server host.


In one of my earlier posts, I discussed setting up a shared storage repository using OCFS2. Today, I’d like to discuss the steps involved in implementing additional repositories to your Oracle VM Server. One of the main reasons you would want to add an additional repository is the simple fact of not having additional space within your current OVS repository to host more virtual machines. In this tutorial, I’ll show you step by step on how to do just that.


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: