Fresh install of Oracle VM Manager Template into Oracle VM Server

Question

Hi,
I am trying to install the Oracle VM Manager template and then
create an Oracle VM Manager client.
I have already done a 'fresh install' of Oracle VM Server.
I do not have another machine available to use to contain the
'Oracle VM Manager', therefore, I am attempting to install the
Oracle VM Manager template directly into an Oracle VM Manager Server and
run the client.
I am following the instructions of the Oracle VM Server Users Guide
in section 4.3.
When I extract the zip file contents into the
/OVS/seed_pool directory, I get the following files.
Deploy_Manager_Template.sh
OVM_EL5U3_X86_OVM_MANAGER_PVM.tgz
So far, so good.
Next, I used 'tar' to help me extract the directories of the .tgz file.
So far, so good.
Next, as instructed, I used 'python' and 'print randomMAC()' to create a new MAC address.
Inside the /OVS/seed_pool/OVM_EL5U3_X86_OVM_MANAGER_PVM/vm.cfg file
I modified the vif MAC address. I replaced the
xx:xx:xx with the 'last three' that were generated by the python randomMAC
function from above.
vif = [ 'mac=00:16:3E:<my generated numbers>', ]
So far, so good?
In the Oracle VM Server Users Guide in section 4.3.,
The next step, expains that I should run
xm create mv.cfg
I did this. When I ran this I received back the error.
Using config file "./vm.cfg"
Error disk is not accessible.
When I peek inside my vm.cfg file.
I see file references starting with the following
file:/OVS/running_pool/ ...
Of, course my running_pool directory is empty.
(Again, this is a fresh install of Oracle VM Server).
My first question is the following.
Sometime in this process was I supposed to run
the the following executable?
./Deploy_Manager_Template.sh
If so, should I have done this early?
Was the modification of the vif (of adding the MAC address
into the vm.cfg file, something I 'should have not done'
or 'something that could be ignored' because the
'./Deploy_Manager_Template.sh' would have done this for me?
My second question is the following.
Would the following process be 'more correct?'
..1 Not modify the vm.cfg' file.
..2 run ./Deploy_Manager_Template.sh.
..3 In the /OVS/running_pool/ directory find my
vm.cfg file of interest, then modify the vif with a new MAC address.
..4 In /OVS/running_pool/Change my current location to my directory of interest
run xm create vm.cfg (to run my Oracle VM Manager)?
Any help or ideas whould be appreciated.
Thank you very much,
AIM

Answer 1

Hi,
This is the README file for Oracle VM Manager 2.2.0
Readme for Media Pack B57738-01
Print: Access key=P Close: Access key=C
Oracle VM Templates for Oracle VM Manager 2.2.0 Media Pack v1 for x86 (32 bit)
=====================================================================
Template Version 2.3
Oracle VM Manager Version 2.2.0
This document contains:
1. Prerequisites for Oracle VM Manager virtual machine (VM) deployment
2. Oracle VM Manager Template description
3. Creating an Oracle VM Manager Virtual Machine from
Oracle VM Manager Template
4. Deployment Interview
5. Known Issues
For more information on Oracle VM Manager, please refer to
the "Oracle VM Manager Installation Guide" and the "Oracle VM Manager
User's Guide" available at:
http://download.oracle.com/docs/cd/E15458_01/index.htm
1. Prerequisites
================
- A new install of Oracle VM Server 2.2 that has NOT been managed by another
Oracle VM Manager. Manager Template 2.2 is intended to be installed on Oracle
VM 2.2 server. If you have a new Oracle VM 2.1.5 server and want to deploy
Oracle VM Manager template, please use the Oracle VM 2.1.5 Manager template.
Note: root access to the server's dom0 is required.
- It's highly recommended that you upgrade the default agent (ovs-agent-2.3-19)
to ovs-agent-2.3-27 or later. You can get the latest Oracle VM 2.2 packages
from Oracle's Unbreakable Linux Network (http://linux.oracle.com).
Note: Alternate location to get Oracle VM agent 2.3-27 is
http://oss.oracle.com/oraclevm/server/2.2/RPMS/ovs-agent-2.3-27.noarch.rpm
- A working directory of the Oracle VM Server 2.2 has at least 4GB free space
for downloading and installing the template. The working directory can be any
directory on the Oracle VM server except /OVS/running_pool.
Note: The /root partition of the default Oracle VM server install may not have
enough space to temporarily host the template installation. Please use other
directory that has sufficient free space.
- At least 15GB of free space in the cluster root storage repository. For storage
and repository configuration, please refer to Oracle VM 2.2 Server User Guide:
http://download.oracle.com/docs/cd/E15458_01/doc.22/e15444/storage.htm
and
http://download.oracle.com/docs/cd/E15458_01/doc.22/e15444/repository.htm
- At least 2GB of free memory on the Oracle VM Server
- A static IP address for the Oracle VM Manager
- If enabling HA (high availability) for the Oracle VM Manager,
mount a clustered OCFS2 or NFS filesystem on /OVS. If ext3 or a
local OCFS2 filesystem is used, enabling HA will cause the high availability
prerequisite checking to fail. The Oracle VM Manager configuration
process will exit without completing the configuration.
- The Oracle VM Manager will register the first VM that it detects.
To have Oracle VM Manager be the first VM registered,
make sure there are no virtual machine images besides the Oracle VM Manager
virtual machine in the /OVS/running_pool directory on the Oracle VM Server.
- A desktop or other system with a VNC Viewer installed
The steps below assume that the Oracle VM Server used is not currently
or was not previously managed by another Oracle VM Manager. If this is not
the case, the instructions below will ask user clean up Oracle VM Agent DB
before running the Oracle VM Manager.
2. Oracle VM Manager Template Description
=========================================
The Oracle VM Manager Template is distributed as one archive file which
includes:
File Version
OVM_EL5U3_X86_OVM_MANAGER_PVM.tgz 2.3
Deploy_Manager_Template.sh 2.3
The OVM_EL5U3_X86_OVM_MANAGER_PVM.tgz archive contains two disk images,
a VM configuration file and a readme file:
- Oracle Enterprise Linux 5.3 x86 system disk image
- Oracle VM Manager 2.2 disk image
- vm.cfg
- README
The system image is a JeOS (Just enough OS) installation of Oracle
Enterprise Linux 5.3. It is a smaller footprint install that contains
the only packages needed by Oracle VM Manager.
Oracle VM Manager is configured to use Oracle Database 10g
Express Edition (included).
Deploy_Manager_Template.sh is used to check the prerequisite and
create virtual machine.
During the first boot of the Oracle VM Manager virtual machine,
the Oracle VM Manager configuration process will create server pool
and import the Oracle VM Manager virtual machine.
Two OS user accounts are created by default:
user: root password: ovsroot
user: oracle password: oracle
The user 'oracle' belongs to the 'oinstall' and 'dba' groups.
The default vnc console password is 'oracle'
3. Creating the Oracle VM Manager virtual machine
=================================================
1) Download the Oracle VM Manager Template (V19215-01.zip)
from http://edelivery.oracle.com/oraclevm
2) Login to the Oracle VM Server's dom0 as 'root'
Copy V19215-01.zip to your working directory with at least 4GB free space.
You can choose any directory on OVM Server except /OVS/running_pool.
This zip file contains the archive file OVM_EL5U3_X86_OVM_MANAGER_PVM.tgz
and a deploy script Deploy_Manager_Template.sh
3) As root, run
# unzip V19215-01.zip
4) As 'root', run the deployment script:
# chmod 755 Deploy_Manager_Template.sh
# ./Deploy_Manager_Template.sh
The deployment script Deploy_Manager_Template.sh will complete the following
tasks:
a) prerequisite checking
b) uncompress OVM_EL5U3_X86_OVM_MANAGER_PVM.tgz file to directory
/OVS/running_pool. This directory will contain the files following files:
/OVS/running_pool/OVM_EL5U3_X86_OVM_MANAGER_PVM
|- System.img (OS image file)
|- Manager.img (Manager image file)
|- vm.cfg (VM configuration file)
|- README (Readme file)
c) generate and assign new MAC address to the virtual machine
d) interview the user for VM and VM Manager configuration parameters
(next section 'Deployment interview' provides the list of questions)
e) create and boot the virtual machine from the Oracle VM Server
command line
f) display the access information for Oracle VM Manager and Oracle VM
Manager VM
4. Deployment Interview
=======================
The deployment script will prompt a user to enter
a) Agent password
The agent password is required for the prerequisites check.
b) Storage configuration
Storage Source: NFS address, OCFS2 partition path
The script will automatically detect your cluster root storage repository
if you have configured it. Or it prompts users to input their storage source
and the script tries to set it up as cluster root.
NOTE: how to manually create your own storage repository in OracleVM server 2.2.x
1) Register your storage source. Example:
/opt/ovs-agent-2.3/utils/repos.py -n myhost:/mynfslocation
/opt/ovs-agent-2.3/utils/repos.py -n /dev/sdb3
Note that the storage source should have at least 15GB free space.
If the storage source is successfully registered, note down the uuid genereated
by the command above, such as:
51d4c69b-e439-41ac-8b31-3cc485c993b0 => /dev/sdb3
2) Mount your storage repository.
If the agent version is 2.3-27 or higher, execute:
/opt/ovs-agent-2.3/utils/repos.py -i
otherwise, complete the following commands:
[1] mkdir -p /var/ovs/mount/$(echo <uuid> | sed s/-//g | tr '[:lower:]' \
'[:upper:]')"
where '<uuid>' is the uuid noted down in step 2)
[2] mount your storage source to the directory made in step [1].
3) If /OVS exists, delete or move /OVS
mv /OVS "/OVS.$(date '+%Y%m%d-%H%M%S').orig"
create a symbolic link from storage repository to /OVS
ln -nsf /var/ovs/mount/<UUID>/ /OVS
c) Network configuration
Static IP address
Netmask
Default Gateway IP address
DNS Server IP address
Hostname
d) Password for database accounts:
'SYS' and 'SYSTEM' (the same password the same password is used)
'OVS'
'oc4jadmin'
'admin'
e) Web Service configuration (supported in template in version 1.2)
Web Service password (at least 6 characters)
Enable HTTPS or not
f) SMTP server (outgoing mail server SMTP hostname)
E-mail Address for account 'admin'
g) Data for the manager services configuration:
Oracle VM Server Pool Name
Oracle VM Server login user name
Oracle VM Server login password
Note that Oracle VM Manager is critical for managing Oracle VM Server Pools.
Do not pause, suspend or shutdown this virtual machine! Configuring
HA is recommended for this virtual machine so that Oracle VM will
automatically restart the Oracle VM Manager virtual machine if there
is a server crash.
5. Known Issues
===============
1) You may see messages on a virtual machine's console similar to these
when the virtual machine is booting up:
Fatal: No PCI config space access function found
rtc: IRQ 8 is not free.
i8042.c: No controller found.
These messages can be ignored.
2) Mail server check fails.
Bug #7140 in bugzilla.oracle.com
Oracle VM Manager installer only checks the default SMTP port 25 for the
mail server. If the SMTP port is not 25, the check fails, and you will
see the following message:
Mail server '<mail server hostname>' check failed, want to re-enter it(Y|n)?
You can enter 'n' to skip the mail server checking. You will also see the
send mail checking fails with following message:
Failed to send mail to '<Admin e-mail address>'
want to re-enter the e-mail address(Y|n)?
You can enter 'n' to skip the send mail checking.
3) OEL VM console may display error messages similar to those below:
BUG: warning at drivers/xen/fbfront/xenfb.c:143/xenfb_update_screen() (Not
tainted)
Call Trace:
[<ffffffff803aa461>] xenfb_thread+0x135/0x2c5
[<ffffffff8024874b>] try_to_wake_up+0x365/0x376
[<ffffffff8029ba6e>] autoremove_wake_function+0x0/0x2e
[<ffffffff8029b856>] keventd_create_kthread+0x0/0xc4
[<ffffffff803aa32c>] xenfb_thread+0x0/0x2c5
[<ffffffff8029b856>] keventd_create_kthread+0x0/0xc4
[<ffffffff802339c8>] kthread+0xfe/0x132
[<ffffffff80260b24>] child_rip+0xa/0x12
[<ffffffff8029b856>] keventd_create_kthread+0x0/0xc4
[<ffffffff802338ca>] kthread+0x0/0x132
[<ffffffff80260b1a>] child_rip+0x0/0x12
This will not cause any problems.
4) If you accidentally power off Oracle VM Manager virtual machine through
Oracle Manager UI, and restart the virtual machine from OVM server command
line, although Oracle VM Manager virtual machine is running normally,
the virtual machine status in Manager UI will stay in 'Shutting Down'.
This is expected, as the virtual machine status sync will only happen when
the virtual machine status is "Error" or "Powered Off".
To re-sync the virtual machine status, please complete the following steps:
1. Log on the Manager UI;
2. Navigate to the 'Virtual Machines' tab;
3. Select Oracle VM Manager virtual machine, "OVM_EL5U3_X86_OVM_MANAGER_PVM";
4. Choose 'Reset' from 'More Actions' dropdown list;
5. Click 'Go' button, the status will become "Running" after a while.
5) (Bug 9191053) For OVS agent version 2.3-19, the following High
Availability scenario will not work.
"If a Virtual Machine Server fails, all running virtual machines are
restarted automatically on another available Virtual Machine Server."
For OVS agent 2.3-19, Oracle VM Manager virtual machine will not be
automatically restarted on any other available Virtual Machine Server,
but on the original Virtual Machine Server when it becomes available again.
To fix the issue, please upgrade OVS agent to 2.3-27 or the latest version.