Troubleshooting and Gotchas in Oracle VM Manager 2.1.2

0
113
3 min read

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
details.

Failed

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/
deployApp.sh

Aborting installation. Please check the environment and rerun
runInstaller.sh.

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:

Troubleshooting and Gotchas in Oracle VM Manager 2.1.2

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:

Troubleshooting and Gotchas in Oracle VM Manager 2.1.2

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:

Troubleshooting and Gotchas in Oracle VM Manager 2.1.2

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:

Troubleshooting and Gotchas in Oracle VM Manager 2.1.2

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:

Troubleshooting and Gotchas in Oracle VM Manager 2.1.2

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.

xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64

So if your CPU does not support HVM, use the PVM (Paravirtualized Method) to create your VM.

LEAVE A REPLY

Please enter your comment!
Please enter your name here