Copyright © 2011, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices
This section describes some problems you may encounter when using Oracle VM Manager, and explains how to resolve them.
This section discusses changes you can make to configure the behavior of the Oracle VM Manager user interface.
It is likely that the default value for showLoginCoreServerUri is set to false. Check the Show Management Server URI checkbox in the Preferences Pane on the Tools and Resources tab in Oracle VM Manager.
See Section 3.10, “Changing Default UI Behaviour” for more information on Oracle VM Manager UI preferences.
On Storage Servers that have a very large number of file systems available, the UI may timeout while refreshing the list of available file systems, resulting in a 'No File Systems Available' message. This usually means that the timeout value is set too low for the number of file systems that the UI needs to refresh. Change the settings for the Refresh Timeout Value in the Preferences Pane on the Tools and Resources tab in the Oracle VM Manager user interface.
See Section 3.10, “Changing Default UI Behaviour” for more information on Oracle VM Manager UI preferences.
Oracle VM Manager error messages are displayed in the User Interface, in the Jobs tab, in the object's Events list and are also available in log files. Log files are stored in the following directory on the Oracle VM Manager host computer:
/u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/logs
There a few files of interest here:
access.log: Used to track HTTP access to the Web interface of the Oracle VM Manager and to the underlying WebLogic HTTP interface. This log can be used to track access and HTTP operations within Oracle VM Manager to help debug access issues and to audit access to the Oracle VM Manager
AdminServer.log: Used to track events within the underlying WebLogic framework, including events triggered by Oracle VM Manager. This log can be used to track a variety of issues within Oracle VM Manager including TLS/SSL certificate issues, server availability issues, and any actions performed within Oracle VM Manager which are usually identifiable by searching for items containing the string 'com.oracle.ovm.mgr'. Login failures resulting from locked accounts (as opposed to incorrect credentials) are also in this file.
AdminServer-diagnostic.log: Used to track exceptions within the underlying WebLogic framework, including particular events triggered by Oracle VM Manager such as login failures due to incorrect credentials. This log can be used to track Oracle VM Manager behavior that results in an exception or for login failure, which can be tracked by searching for the string 'An incorrect username or password was specified'.
Since log file format is determined by WebLogic, many of these files may be difficult to read. A log parsing tool is included with Oracle VM Manager to help extract useful information from the actual log files. The log parsing tool is named OvmLogTool.py and is located here:
/u01/app/oracle/ovm-manager-3/ovm_shell/tools
OvmLogTool.py can do 3 useful things:
convert and combine all the AdminServer log files into one easier-to-read file
create a filtered summary log file that only lists errors
tail the AdminServer log, applying the filtering on the fly
Usually analysis of the logs starts by generating an error summary log. The summary file can act as an index into the filtered file to investigate and analyze errors, providing you with timestamps an a shortened summary of each error that may need further investigation. To generate a summary log file, do the following:
# python OvmLogTool.py -s -o summary
processing input file: /u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/
logs/AdminServer.log00001
processing input file: /u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/
logs/AdminServer.log
This generates a file named summary in the
local directory. You can use this to look for
errors that occurred within Oracle VM Manager.
To get a full log of all events and errors within Oracle VM Manager you can do the following:
# python OvmLogTool.py -o filteredlog
processing input file: /u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/
logs/AdminServer.log00001
processing input file: /u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/
logs/AdminServer.log
This generates a file named filteredlog in
the local directory. You can use this to look for all
events that occurred within Oracle VM Manager.
Finally, you can use OvmLogTool.py to filter results on the fly while tailing the log:
# python OvmLogTool.py -t
tailing log file: /u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/
logs/AdminServer.logUse Ctrl+C to exit the program when you have finished tailing the log file.
A set of Oracle VM command line utilities are available for download. These Oracle VM utilities are a collection of command line scripts that allow you to perform a set of basic management tasks on Oracle VM Servers and virtual machines in an Oracle VM environment. These utilities are particularly useful to administrators who need to execute certain operations quickly and/or repeatedly. Using the command line scripts makes these tasks quicker and easier to perform. See the Oracle VM Utilities Guide for more information on these utilities.
A command line interface to Oracle VM Manager is also available which mirrors the user interface in functionality to enable ad hoc, scripted, and programmatic access to the Oracle VM environment. See the Oracle VM Command Line Interface User's Guide for more information on the command line interface.
If you launch the console of a virtual machine in Oracle VM Manager, and an error is displayed, you may not have installed the VNC viewer on the Oracle VM Manager host computer. To resolve this problem, install a VNC viewer on the Oracle VM Manager host. See Installing and Configuring Virtual Machine Console Utilities for more information.
You can also install a VNC viewer on the client accessing the Oracle VM Manager user interface. Oracle recommends you also install a VNC viewer on the Oracle VM Manager host computer so that if a client does not have a VNC viewer, this problem does not occur.
The following message is displayed: "Error: There is no server supporting hardware virtualization in the selected server pool."
To solve this problem, make sure the Oracle VM Server supports hardware virtualization.
Follow these steps to check:
Run the following command to check if hardware virtualization is supported by the CPU:
# cat /proc/cpuinfo |grep -E 'vmx|smx'
If any information that contains vmx or
smx is displayed, it means that the CPU
supports hardware virtualization. Here is an example of the
returned message:
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm
The /proc/cpuinfo command only shows virtualization capabilities starting with Linux 2.6.15 (Intel®) and Linux 2.6.16 (AMD). Use the uname -r command to query your kernel version.
Make sure you have enabled hardware virtualization in the BIOS.
Run the following command to check if the operating system supports hardware virtualization:
# xm info |grep hvm
The following is an example of the returned message:
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x
If the CPU does not support hardware virtualization, use the paravirtualized method to create the virtual machine. See Section 7.7, “Creating a Virtual Machine”.
To change the CD in a virtual machine:
Unmount the first CD:
# umount mount-pointSelect the second ISO file, and click Change CD.
Mount the second CD:
# mount /dev/cdrom mount-point
When creating a virtual machine from an Oracle VM
2.x template, the clone job fails
with the error:
OVMAPI_9039E Cannot place clone VM:template_name.tgz, in Server Pool: server-pool-uuid. That server pool has no servers that can run the VM.
This is caused by a network configuration inconsistency with the
vif = ['bridge=xenbr0'] entry in the virtual
machine's configuration file.
To resolve this issue, remove any existing networks in the virtual machine template, and replace them with valid networks which have the Virtual Machine role. Start the clone job again and the virtual machine clone is created. Alternatively, remove any existing networks in the template, restart the clone job, and add in any networks after the clone job is complete.
Copyright © 2011, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices