Changes made to the vm.cfg configuration file are not reflected in Oracle VM Manager. For example, if you edit the HA setting in the vm.cfg to disable HA, and the virtual machine is stopped by any method other than using Oracle VM Manager, the virtual machine is restarted. Oracle VM Manager is not aware of the HA change in the virtual machine's configuration file.

When importing and deleting several templates concurrently, or when an Oracle VM Server is removed during the import of a template, a lock exception error may appear. However, the template upload often completes successfully despite the error message, but it does not appear in the list of available templates in the storage repository.

To resolve this problem, refreshing the storage repository is often sufficient, after which the uploaded template file appears in the list. In some cases the imported template turns out to be incomplete. In that case, you should delete the template and import the template again.

Starting a PVM virtual machine using PXE type boot with an invalid network URL causes the virtual machine status to be in progress indefinitely. To resolve this, abort the virtual machine start job. Edit the virtual machine and provide the correct URL.

Similarly, jobs may 'hang' or remain in progress every time a virtual machine is started or stopped. A virtual machine may be in an unresponsive state for a variety of reasons and consequently fail to respond to a start or stop request. The appropriate action in this case is to abort the job.

Creating a virtual machine using the Network method (PXE) does not proceed beyond pre boot, so the virtual machine is not created. This occurs for Oracle Linux 5.x virtual machines.

Creating hardware virtualized guests requires the Oracle VM Server has an Intel-VT (code named as Vanderpool) or AMD-V (code named as Pacifica) CPU. See the Oracle VM Installation and Upgrade Guide for a list of supported hardware.

Creating a PVM guest using local storage may take a very long time. This may be caused by write caching being turned off for the local disk.

Workaround: Enable write caching for the disk using the hdparam utility.

HVM virtual machines with Linux, Solaris or Windows guest operating system may experience kernel panic when the virtual machine is stopped and started several times.

Workaround: Set the Maximum Memory and the Memory fields to the same value in the Create/Edit Virtual Machine wizard.

When adding a new disk (whether it be a virtual disk, physical disk, or an ISO file) to a virtual machine, if you do not select the Disk Ordering tab in the Edit a Virtual Machine dialog box, the disk(s) are not added to the virtual machine.

Workaround: When adding a virtual disk, physical storage, or ISO file to a virtual machine using the Edit a Virtual Machine dialog box, first select the disk from the Disks tab, then select the Disk Ordering tab to order the new disk(s).

On an HVM guest, you can dynamically add and remove ISO files to CDROM slots to a running virtual machine, but you cannot change the disk order.

For hardware virtualized guests with paravirtualized drivers (PVHVM) changing the number of virtual CPUs is not supported. The guest will continue to display the virtual CPUs as originally defined.

When you launch the virtual machine console from Oracle VM Manager you may experience that the mouse pointer on your local machine and the mouse pointer in the virtual machine travel across the screen at different speeds.

If your guest virtual machine's operating system is Linux-based, the following workaround may reduce the mouse control issue. Enter the following on the guest's command line:

# xset m 1 1

When using a German keyboard with the Virtual Machine console, the key output is incorrect. Changing the keyboard setting for the server pool from en-us to de does not correct this issue. This is an issue with TightVNC.

Workaround: Configure RealVNC instead of TightVNC. See Installing and Configuring a VNC Viewer for information on configuring a VNC Viewer.

The Info tab for a virtual machine does not display the virtual machine's IP address. The IP address for a virtual machine is only displayed if the paravirtual drivers are installed.

Workaround: Install the Paravirtual drivers in the virtual machine's operating system. See Installing Paravirtualized Drivers for information on installing the Paravirtual drivers on Linux-based operating systems.

Windows Server 2008 Release 2 64-bit hardware virtualized guests fail to shut down cleanly. After the guest has been shut down, and started again, Windows reports that it was not shut down cleanly.

This is not an issue for Windows Server 2008 Release 2 32-bit hardware virtualized guests with paravirtualized drivers (PVHVM).

When you add a new disk to a virtual machine and refresh the device manager, the new disk is displayed with a yellow mark. This occurs in Microsoft Windows guests that have the Oracle VM Windows Paravirtual Drivers for Microsoft Windows Release 2.0.7 installed.

When you add a new disk to a virtual machine, the new disk is not automatically detected. This occurs in Microsoft Windows 2008 Release 2, 64-bit guests that have the Oracle VM Windows Paravirtual Drivers for Microsoft Windows Release 2.0.7 installed.

Workaround: After you add a new disk, scan for new hardware changes using Server Manager > Disk Drives > Scan for hardware changes.