The following error is displayed during installation of Oracle VM Manager if the prerequisite libaio package is not installed:
libaio is not installed...
To fix this error, install the libaio package. For information on how to install libaio, see Section 4.2.2.3, “Prerequisite Packages” in the Oracle VM Installation and Upgrade Guide.
The Oracle VM Manager installer may fail to install MySQL and displays the message:
Failed: The database instance is not available.
You can check the log file at
/tmp/ovmm-installer.selfextract_
for more detailed information.
id/ovm-manager-3-install-date.log
There are two workarounds to this issue.
Make sure that MySQL is not installed, or has installed correctly. Use the following command to check the status:
$ service ovmm_mysql status
If MySQL is running, run the Oracle VM Manager installation script to uninstall it, and reinstall Oracle VM Manager.
Make sure the computer's host name matches the host name in the
/etc/hostsfile. See Section 4.2.2.5, “Network” to configure the host name.
The Oracle VM Manager install may fail and display the following message:
Creating the Oracle VM Manager database schema ... Failed.
You can check the log file at
/tmp/ovmm-installer.selfextract_
for more detailed information.
id/ovm-manager-3-install-date.log
Possible workarounds for this issue are:
Make sure that MySQL has installed correctly. Use the following command to check the status:
$ service ovmm_mysql status
If MySQL is running, run the Oracle VM Manager installation script to uninstall it, and reinstall Oracle VM Manager.
Reinstall Oracle VM Manager.
If the operating system is a non-English character set or language, the Oracle VM Manager installer may display the following error:
Update default password failed.
Oracle VM Manager only supports the English language and character set.
You can check the log file at
/tmp/ovmm-installer.selfextract_
for more detailed information.
id/ovm-manager-3-install-date.log
To workaround this issue, set the character set to en_US.UTF-8:
Run the following command to check if the value of LANG is
en_US.UTF-8:# env|grep LANG
If the character set is not
en_US.UTF-8, change it toen_US.UTF-8:# export LC_CTYPE="en_US.UTF-8"
Reinstall Oracle VM Manager.
If the oracle user account is created using NIS-based authentication (Network Information Services), the Oracle VM Manager installation fails during the prerequisite check, and the following error is displayed:
Verifying installation prerequisites ... hardnofiles should be set to 8192 but was 0 Configuration verification failed ...
Or the installation may pass prerequisite check, but may fail later during the installation of the Application Development Framework:
Retrieving Oracle Application Development Framework (ADF) ... Unzipping Oracle ADF ... Installing Oracle ADF ... Installing Oracle ADF Patch...
To workaround this issue, disable ypbind service and create a
non-NIS-based oracle user account using
createOracle.sh on the host computer and
rerun the installer:
# /sbin/service ypbind stop # service ypbind status ypbind is stopped # ./createOracle.sh # ./runInstaller.sh
In some cases, it is not possible to successfully upgrade
Oracle VM Manager from Release 3.2.10 to Release
3.4.x and the installer output
indicates a failure running the
ovm_preUpgrade script, as in the following
example:
# ./runInstaller.sh Oracle VM Manager Release 3.4.xInstaller Oracle VM Manager Installer log file: /var/log/ovmm/ovm-manager-3-install-yyyy-mm-dd-xxxxxx.log Verifying upgrading prerequisites ... Starting Upgrade ... Reading database parameters from config ... Verifying configuration ... Upgrading from version 3.2.10 to version 3.4.xRunning ovm_preUpgrade script, please be patient this may take a long time ...time_stamp: All jobs in the job log will now be deleted.time_stamp: Deleting 183 jobs before upgrade.time_stamp: 183 jobs have been deleted. 4 jobs are still in the job log. Failure running the ovm_preUpgrade script, upgrade cannot continue!
This failure occurs because an instance of Oracle VM Server is in an
erroneous state. As a result, automatic discovery jobs fail and
then re-occur. These automatic discovery jobs prevent the
ovm_preUpgrade script from running
successfully.
To work around this issue, do the following:
Identify the instance of Oracle VM Server that is in an erroneous state.
Shut down or live migrate the virtual machines running on the instance of Oracle VM Server.
Stop the instance of Oracle VM Server.
Ensure that no pending jobs exist in Oracle VM Manager.
Run the script to upgrade Oracle VM Manager.