D Troubleshooting

This Appendix describes some problems you may encounter when using Oracle VM Manager, and explains how to resolve them. It includes the following topics:

• Log Files

• Cannot Log In to Oracle VM Manager

• Cannot Create a Virtual Machine from Installation Media

• Insufficient Space in Repository for Creating a Virtual Machine

• The Virtual Machine Stuck in a Status

• The Status of the Virtual Machine Is Error

• Cannot Access Virtual Machine Console

• Cannot Perform Live Migration

• Cannot Change CD in the Virtual Machine

• Cannot Import External Resources

• Remote Host Identification Error in Server Pool

Find additional information on the following Oracle support-oriented Web sites:

• Oracle MetaLink, available at http://metalink.oracle.com

• Oracle Virtualization Forum, available at http://forums.oracle.com/forums/forum.jspa?forumID=482

D.1 Log Files

Oracle VM Manager log files are stored in the directory:

/var/log/ovm-manager/

Table D-1, "Log Files" lists the log files it contains.

Table D-1 Log Files

Log File	Description
ovm-manager.log	The Oracle VM Manager installation log.
db.log	The Oracle Database log. When you install Oracle VM Manager on an existing database, the log information is stored here.
oc4j.log	The Oracle Containers for J2EE (OC4J) installation log. When oc4j.log exceeds 10 MB, a new log file oc4j.log.1. is generated to store the logs in oc4j.log. Subsequently, the oc4j.log is cleared to record new log information.
upgrade_oldversion_newversion.log.log	The Oracle VM Manager upgrading log.

D.2 Cannot Log In to Oracle VM Manager

It may take a very long time to log in, or it is stuck in the Login page. This may be caused by lack of memory for OC4J.

To solve this problem:

1. Log in to the computer where Oracle VM Manager is installed, and run the following command to check the log information:

   # cat  /var/log/ovm-manager/oc4j.log | grep "heap"
   

   If OC4J runs out of memory, the following information is displayed:

   Internal Exception: java.lang.OutOfMemoryError: Java heap space
   

2. Run the following command to restart OC4J:

   # service oc4j stop
   # service oc4j start
   

If OC4J runs out of memory, you need to increase the OC4J memory size. Follow these steps to do it:

1. View the OC4J configuration information:

   # vi /opt/oc4j/bin/oc4j
   

2. Locate the following line, and increase the memory size to an appropriate value, such as 512:

   OC4J_JVM_ARGS="-XX:PermSize=256m -XX:MaxPermSize=512m"
   

3. Restart OC4J:

   # service oc4j stop
   # service oc4j start
   

D.3 Cannot Create a Virtual Machine from Installation Media

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 Virtual Machine Server supports hardware virtualization.

Follow these steps to check:

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

2. Ensure that you have enabled hardware virtualization in the BIOS.

3. 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 6.3.2, "Creating a Virtual Machine From Installation Media".

D.4 Insufficient Space in Repository for Creating a Virtual Machine

A message similar to the following is displayed: "Error: The largest virtual disk that can be allocated is: 4815 MB."

To solve this problem, decrease the disk size of the virtual machine, or add a new repository. See Oracle VM Server User's Guide for information on creating a storage repository.

D.5 The Virtual Machine Stuck in a Status

For Oracle VM Manager Release 2.1.1 and Release 2.1.2 Users

To solve this problem, set the status to Powered Off, and delete the virtual machine directly. See Section 6.10.2, "Deleting a Stuck Virtual Machine" for more information.

For Oracle VM Manager Release 2.1 Users

To solve this problem, change the status manually as follows:

1. Make sure that the virtual machine in the target server has been shut down. Use xm list or virsh list to check the virtual machine name and ID.

2. If the virtual machine is running, use xm shutdown vm_id or virsh shutdown vm_id to shut it down, where vm_id refers to the virtual machine name or ID.

3. Use xm list or virsh list to check if the virtual machine has been shut down. If it is still running, use xm destroy vm_id, or virsh destroy vm_id to shut it down.

4. Log in as oracle (or root first, then su - oracle) to the computer where Oracle VM Manager is installed, and run the following commands to change the virtual machine status to Powered off in the Oracle XE database:

   export ORACLE_HOME='/usr/lib/oracle/xe/app/oracle/product/10.2.0/server' 
   export ORACLE_SID=XE 
   $ORACLE_HOME/bin/sqlplus / as sysdba 
   SQL> update ovs.ovs_vm_img t set t.status='Powered Off' where t.img_name like 'vm_name'; 
   SQL> commit; 
   SQL> quit
   

   vm_name refers to the virtual machine name.

5. Retry your operation, or delete the virtual machine directly.

For Oracle VM Manager Release 2.2 Users

Reset the virtual machine. See Section 6.4.5, "Resetting a Virtual Machine".

D.6 The Status of the Virtual Machine Is Error

To view more details, click the Virtual Machines tab, and then click the Show link of the virtual machine. Click the number after the Log item to display the error log. The error log information includes: time, log level, target, operation, and message. Alternatively, view the error log in the Administration tab. See Section 7.4, "Viewing Logs".

The following are some error log items and solutions:

• HVM guest support is unavailable: is VT/AMD-V supported by your CPU and enabled in your BIOS?

• Cannot find host server for vm('/OVS/running_pool/vm_name')

• Could not find '/OVS/running_pool/vm_name' in any storage repository

• /opt/ovs-agent-version/utils/rcp.py /OVS/running_pool/vm_name/ [e-mail]:/OVS/running_pool/vm_name password=>encounter 'permission denied'!

• xm create '/OVS/running_pool/vm_name/vm.cfg'=>Error: Domain 'vm_name' already exists with ID 'number'

• vm('/OVS/running_pool/vm_name') status ('RUNNING') not in ('DOWN', 'ERROR')

• No server selected to run vm('/OVS/running_pool/vm_name') memory=number

• xm create '/OVS/running_pool/vm_name/vm.cfg'=>Error: Device number (vif) could not be connected. Could not find bridge device null

• No pxe bootable vif found

• virt-install options=>mount: can't get address for host umount: /var/lib/xen/xennfs.mkvX0Q: not mounted ERROR: Unable to mount NFS location!

• winxp_build failed: global name 'xen_handle_vif_qos' is not defined

D.6.1 HVM guest support is unavailable: is VT/AMD-V supported by your CPU and enabled in your BIOS?

Possible Cause

The Virtual Machine Server does not support hardware virtualization.

Solution

Verify that the Virtual Machine Server supports hardware virtualization, and has hardware virtualization enabled in the BIOS. See Appendix D, "Cannot Create a Virtual Machine from Installation Media".

If the Virtual Machine Server does not support hardware virtualization, you can create the virtual machine from installation media.

D.6.2 Cannot find host server for vm('/OVS/running_pool/vm_name')

Possible Cause

• No Virtual Machine Server available to run the virtual machine.

• Insufficient memory on the Virtual Machine Server.

Solution

1. Make sure at least one Virtual Machine Server is available to run the virtual machine.

2. Make sure the Virtual Machine Server has sufficient memory to run the virtual machine. To release server memory:

   • Shut down other running virtual machines.

   • Decrease the virtual machine memory, and restart the virtual machine. See Section 6.7, "Editing a Virtual Machine".

D.6.3 Could not find '/OVS/running_pool/vm_name' in any storage repository

Possible Cause

The virtual machine has been removed from the Virtual Machine Server.

Solution

Remove the virtual machine in Oracle VM Manager, and create a new one.

D.6.4 /opt/ovs-agent-version/utils/rcp.py /OVS/running_pool/vm_name/ [e-mail]:/OVS/running_pool/vm_name password=>encounter 'permission denied'!

Possible Cause

You have entered an incorrect user name or password when creating the Utility Server.

Solution

Enter correct user name and password for the Utility Server. See Section 3.2, "Creating a Server Pool".

D.6.5 xm create '/OVS/running_pool/vm_name/vm.cfg'=>Error: Domain 'vm_name' already exists with ID 'number'

Possible Cause

The virtual machine is already started.

Solution

Use the command xm list to check the virtual machine status. Refresh the virtual machine periodically.

D.6.6 vm('/OVS/running_pool/vm_name') status ('RUNNING') not in ('DOWN', 'ERROR')

Possible Cause

The status in Oracle VM Manager has not been synchronized with the status data in the database.

Solution

Shut down the virtual machine, and then restart it.

D.6.7 No server selected to run vm('/OVS/running_pool/vm_name') memory=number

Possible Cause

There is insufficient memory on this Virtual Machine Server.

Solution

Decrease the virtual machine memory, and then restart the virtual machine. Or shut down other running virtual machines to release more memory.

D.6.8 xm create '/OVS/running_pool/vm_name/vm.cfg'=>Error: Device number (vif) could not be connected. Could not find bridge device null

Possible Cause

No bridge for this virtual machine.

Solution

Select a bridge for the virtual machine. See Section 6.7.2, "Network".

D.6.9 No pxe bootable vif found

Possible Cause

Invalid VIF type for the virtual machine.

Solution

When starting a hardware virtualized machine through PXE, the VIF type must be Fully Virtualized (ioemu). Select a valid VIF type for the virtual machine. See Section 6.7.2, "Network".

D.6.10 virt-install options=>mount: can't get address for host umount: /var/lib/xen/xennfs.mkvX0Q: not mounted ERROR: Unable to mount NFS location!

Possible Cause

The resource location you entered is incorrect.

Solution

Delete the virtual machine, and create a new one. Make sure you enter a correct resource location when creating a paravirtualized machine.

D.6.11 winxp_build failed: global name 'xen_handle_vif_qos' is not defined

Possible Cause

Oracle VM Manager fails to detect the API xen_handle_vif_qos.

Solution

Upgrade both Oracle VM Manager and Oracle VM Server to Release 2.1.2 or above to support this feature.

D.7 Cannot Access Virtual Machine Console

If your operating system is Linux, and you are using Mozilla Firefox to access the virtual machine, download and install the Console Plug-in. See Section 6.5.1, "Installing the Console Plug-In".

If Oracle VM Manager is upgraded from the Release 2.1, rather than a fresh installation, you may encounter the following error when accessing the virtual machine console:

java.lang.ClassNotFoundException: VncViewer.class

This is caused by the delay in cache refresh. To solve this problem, shut down all the Web pages, and open a new one to access the virtual machine console.

D.8 Cannot Perform Live Migration

The following message is displayed: "Error: Server is not ready for live migration."

To solve this problem, you must use identical computers to perform live migration, that is, the computer make and model number must be identical.

D.9 Cannot Change CD in the Virtual Machine

To change the CD in a virtual machine:

1. Unmount the first CD:

   # umount mount-point
   

2. Select the second ISO file, and click Change CD.

3. Mount the second CD:

   # mount /dev/cdrom mount-point
   

D.10 Cannot Import External Resources

Cannot Import Due to Invalid URL

The following information is displayed: "The URL is invalid", or "The proxy URL is invalid".

To solve this problem, log in to the Virtual Machine Server, and run the following command to test the network connection:

# wget url

Here, url refers to the link for downloading the resource.

If the resource is on the Internet, you may need a proxy before running the wget command. Contact your network administrator to get the proxy, an then run the following commands to configure the proxy:

# export http_proxy=http://host:port/ 
# export ftp_proxy=http://host:port/

Here, host refers to the host name or IP address of the proxy server, and port refers to the port number of the proxy.

Cannot Import Due to NFS Disk

The following information is displayed: "Cannot obtain memory size from vm.cfg."

This error may occur when there are two or more Utility Servers in a server pool, and the disk is shared by the Network File System (NFS) mode.

To solve this problem, click the Next button periodically.

D.11 Remote Host Identification Error in Server Pool

If you reinstall the Oracle VM Server software, or change the root user's password of an Oracle VM Server in a server pool, communication from the server pool to that server may fail.

If you reinstall the Oracle VM Server software (not upgraded), the RSA key is likely to change, even if you use the same IP address and host name. You may see an error similar to:

REMOTE HOST IDENTIFICATION HAS CHANGED

or

Host key verification failed

Workaround: Remove the Oracle VM Server from the server pool, and add the Oracle VM Server again.