As more and more users start to explore and use Oracle VM Manager, more troubleshooting and tweaks will come up. This is by no way an exhaustive list and is also not intended to be. Please do participate as much as possible in forums and contribute your tips and tricks with the community.
Oracle VM Manager login takes too much time
I have faced this issue very often and normally if you are unlucky you ought to get this type of error while installing. For instance this error message says nothing about the memory issue:
Failed at "Could not get DeploymentManager".
This is typically the result of an invalid deployer URI format being
supplied, the target server not being in a started state or incorrect
authentication details being supplied.
More information is available by enabling logging -- please see the
Oracle Containers for J2EE Configuration and Administration Guide for
Please see /var/log/ovm-manager/ovm-manager.log for more information.
Deploying application failed.
Please check your environment, and re-run the script:/bin/sh scripts/
Aborting installation. Please check the environment and rerun
But when you upgrade your VM Manager OS with more memory you'll be able to continue with the installation.
Sometimes, you may also get all kinds of errors, such as the following one:
Internal Exception: java.lang.OutOfMemoryError: Java heap space
And they clearly point to the memory issue. This suggests that your OC4J may need more memory.
Let's run the following commands to check the log information:
cat /var/log/ovm-manager/oc4j.log | grep "heap"
If your OC4J ran out of memory you would typically get that heapsize error. To fix this go back to the console and examine the values of the following OC4J_JVM_ARGS function in the /opt/oc4j/bin/oc4j configuration file:
Edit the following OC4J_JVM_ARGS="-XX:PermSize=256m -XX:MaxPermSize=512m function and give more memory to the OC4J.
Save the information and quit:
Restart the service OC4J:
service oc4j stop
service oc4j start
HVM guest creation fails
Normally there are many actions and functionalities within Oracle VM Manager that require the host to be truly HVM-aware, which means that 64-bit (preferably) Oracle VM Servers must be running with hardware virtualization support on the chipset level. Having said that, both Intel and AMD support it and it is highly unlikely that you will come across new machines that do not support that. However, always check the compatibility within a specific family and check whether the support is turned on or off.
Nonetheless, you could be using some reusable older hardware that may or may not support HW-assist virtualization.
If you are confronted with the following message:
"Error: There is no server supporting hardware virtualization
in the selected server pool. "
Then you'll have a reason to worry and check your hardware, and carry out the following commands on the VM Server that does not allow you to create a HVM:
Cat /proc/cpuinfo | grep –E 'vmx|smx'
Use the preceding command if your hardware is HVM-aware, then you should get some reply as shown in the following screenshot:
If you don't get a response, then you might have a problem. For instance we pick up another VM Server which we for sure know does not have a HVM support or HW-assist virtualization:
Also ensure that the virtualization support is enabled at the HW level in the BIOS. Then run the following commands to see if the Operating System supports HVM:
As you have seen in the preceding screenshot, we then quickly logged into the VM Server which we knew does not support HVM and did not get a reply from the 172.22.202.111 VM Server. Whereas, the x64 bit version with built-in, BIOS-enabled HVM support returns the values in the form of xen_caps.
So if your CPU does not support HVM, use the PVM (Paravirtualized Method) to create your VM.
Not enough disk space available for ISOs and Templates
You are naturally bound to run into these sorts of troubles. As more and more excitement seeps in and as you start installing all the versions of Windows and Linux machines to your Oracle IntraCloud farm, the more you are bound to run out of disk space. The kind of error you might run into would be very difficult to troubleshoot. I simply ran out of space when I was pushing VM templates to the Oracle VM Server.
In any case to resolve this you will need to reduce the consumed space by either cleaning up your repository farm or your disk space. Alternatively, you can also add another repository, obviously the other disk must be available to create the additional repository.
To add a new repository, simply run the following command on your VM Server:
/usr/lib/ovs/ovs-makerepo source shared description
Where, source is the block device or NFS path to the file system to be added. The shared parameter could carry a value of 0 or 1. If the value of the shared parameter is 0, it means that the disk will not be shared, whereas when the value is 1, it would imply that the repository will be shared. The description parameter is displayed in the Oracle VM Manager and must be a readable value for the functional users.
You get the value of the repository you just created upon running the following command:
The makerepo script identifies the file system or shared virtual disk as a repository. It also updates the repository configuration to enable it.
It is also a good habit to occasionally check the file system using the "df" command. This command greatly helps in understanding how our volumes are doing and what the usage and mountpoint is:
The df–h–T command helps us make the values more readable. If you type the df–help command, you will get more information on using the df command effectively.
The -h argument ensures that the values are readable to us in amounts of GBs or MBs and not blocks such as –T prints the file system type as well. We have all our VMs running on OCFS and that is one place you must watch out for constantly in case of oversubscription, usage, and disk contention.
This newly added repository will have the following directories created automatically: /OVS/seed_pool, /OVS/running_pool, and /OVS/iso_pool directories. Let's take a quick look at them:
As you can see in the preceding screenshot, it's not just the directories but the other necessary binaries as well that are placed at the same location by default. Here the repository is placed under the OVS and the large value is its UUID.
Cannot login to the VM remotely
Logging into the VM can be a problem, and the best way to solve is to get TightVNC viewer and also install the ovs-console plugin (rpm), when we went ahead to manage the VMs within the Oracle VM Manager.
I have the plugin working perfectly on my MacBook Pro, another Windows machine, and also within the Oracle VM Manager.
Normally, an installation of an older version of Oracle VM Manager and Server throws the following exception when freshly upgraded.
Shut down all the web pages and reload the page to bypass the error.
After the successful installation or correction of the VncViewer.class, you can log into the console:
Voila! You can now work remotely on WinXP running in your Oracle VM IntraCloud environment!
This article discusses troubleshooting in Oracle VM Manager 2.1.2
Oracle VM Manager is clearly an optimal, cost-effective IntraCoud environment which any organization can use to its advantage.
Oracle's own VM templates make a wonderful case to be tested while you can also go ahead and test all Windows flavors on it. There already are organizations choosing the Oracle VM platform, slowly and gradually. Oracle, with its careful and strategic investments in the Cloud Computing space and Virtualization, stands a better chance to go after the highly aspirational low-cost driven consumer market, and with Oracle VM Manager we have just begun scratching the surface of Oracle VM.
If you have read this article you may be interested to view :