This chapter describes the tasks to perform when configuring X2-4, X3-4, X4-4, or X5-4 Exalytics Machines for virtualization. The tasks include deploying Oracle Virtual Machine Server (Oracle VM Server) on the Exalytics Machine, configuring Oracle VM Server with Oracle Virtual Machine Manager (Oracle VM Manager), and deploying VM templates.
This chapter includes the following sections:
Section 5.1, "Configuring New Installations for Virtualization"
Section 5.2, "Configuring Existing Installations for Virtualization"
Section 5.3, "Upgrading Oracle VM Manager and Oracle VM Server to 3.2.9"
Section 5.4, "Upgrading to Oracle Exalytics Release 2 on a Virtualized Environment"
Section 5.5, "Installing and Configuring Application Software on Virtual Machines"
Note:
X5-4 servers are certified with Oracle VM 3.3.3, while all the earlier servers are certified only with Oracle VM 3.2.9.This section includes the following topics:
Before you virtualize an Exalytics Machine, review the following sections:
Section 5.1.1.2, "Prerequisites for Configuring Exalytics Machines for Virtualization"
Section 5.1.1.4, "Reconfiguring Existing RAID Configurations on the Exalytics Machine"
As you prepare to virtualize an Exalytics Machine, do the following:
Review the Oracle VM Release Notes, to ensure that you understand the differences between Oracle Virtual Machine and its documented functionality, and any other issues that apply to the current release.
Review Oracle VM Installation and Upgrade Guide for Release 3.2 and Oracle VM User's Guide for Release 3.2 to ensure that you understand how to install and configure Oracle Virtual Machine Server, set up networking, and create virtual machines.
Review Oracle Exalytics In-Memory Machine Owner's Guide to ensure that you have properly configured and commissioned the Exalytics Machine in your data center.
The following prerequisites must be met before you can virtualize an Exalytics Machine:
The Exalytics Machine has been racked and mounted in a data center.
Oracle Integrated Lights Out Manager (ILOM) 3.1.2.24 or later, is configured to be accessible from the network using the web interface.
All networking information such as host name, IP address, subnet, gateway, and DNS are available.
Spare, unassigned IP addresses are available for the server pool and for each virtual machine deployed on the Exalytics Machine.
A Linux environment is available to install Oracle VM Manager.
You have access to the internet from a computer (not necessarily the Exalytics Machine) to download required software.
If required, remove the existing partition on /dev/sdb which is mounted to /u01 from the Exalytics Machine. You cannot create a repository on a Oracle Virtual Machine disk which contains a partition.
Note:
Before removing the existing partition, remember to back up all data on sdb1. If you are removing the existing partition on a new machine, you do not need to back up your data.To remove existing partitions:
Log in as the root user, and enter the following command to run the disk partition utility:
# parted /dev/sdb
The output should look similar to the following:
GNU Parted 1.8.1 Using /dev/sdb Welcome to GNU Parted! Type 'help' to view a list of commands.
To display the existing partition, enter the following command:
# print
To remove the existing partition, enter the following command:
# rm 1
To confirm that the existing partition has been removed, enter the following command:
# print
The existing partition is removed.
This section consists of the following topics.
Section 5.1.1.4.1, "Reconfiguring Existing RAID Configurations on the X2-4 Exalytics Machine"
Section 5.1.1.4.2, "Reconfiguring Existing RAID Configurations on the X3-4 Exalytics Machine"
Section 5.1.1.4.3, "Reconfiguring Existing RAID Configurations on the X4-4 Exalytics Machine"
Section 5.1.1.4.4, "Reconfiguring Existing RAID Configuration on an X5-4 Exalytics Machine"
Section 5.1.1.4.5, "Resetting RAID Configuration (Optional)"
The X2-4 Exalytics Machine comprises six hard drives, each having a capacity of 600 GB. Two drives are configured as RAID1 and four drives are configured as RAID5. To optimize the use of the disk space, you must reconfigure the RAID1 and RAID5 configurations on the Exalytics Machine. Reconfigure RAID1 so that it consists of two virtual drives of 100 GB and 457 GB, and RAID5 consists of the remaining drives.
To reconfigure existing RAID configurations on the X2-4 Exalytics Machine:
Restart the Exalytics Machine using Integrated Lights Out Manager (ILOM).
Press Ctrl+Y and enter RAID CLI (Command Line Interface) as the Exalytics Machine is restarting.
Note:
The "Copyright LSI Logic Corporation" displays during the restart sequence when it is possible to enter the RAID CLI. Observe the screen carefully as the message displays for a very short time. This avoids restarting the machine again.Enter the following MegaRAID command to delete the existing RAID configuration:
# -CfgLdDel -LALL -a0
Enter the following command to create a RAID1 partition with two virtual drives of size 100 GB and 457 GB:
# -CfgLdAdd -r1[252:0, 252:1] WB Direct NoCachedBadBBU -sz102400 -sz467968 -a0
Enter the following command to create a RAID5 partition with the remaining drives:
# -CfgLdAdd -r5[252:2, 252:3, 252:4, 252:5] WB Direct NoCachedBadBBU -a0
In the left pane of the ILOM, expand Host Management, then select Power Control. In the Select Action list, select Power Cycle, then click Save.
The Exalytics Machine restarts.
The X3-4 Exalytics Machine comprises 6 hard drives, each having a capacity of 900 GB.Two drives are configured as RAID1 and four drives are configured as RAID5. To optimize the use of the disk space, you must reconfigure the RAID1 and RAID5 configurations on the Exalytics Machine. Reconfigure RAID1 so that it consists of two virtual drives of 100 GB and 657 GB, and RAID5 consists of the remaining drives.
To reconfigure existing RAID configurations on the X3-4 Exalytics Machine:
Restart the Exalytics Machine using Integrated Lights Out Manager (ILOM).
Press Ctrl+Y and enter RAID CLI (Command Line Interface) as the Exalytics Machine is restarting.
Note:
The "Copyright LSI Logic Corporation" displays during the restart sequence when it is possible to enter the RAID CLI. Observe the screen carefully as the message displays for a very short time. This avoids restarting the machine again.Enter the following MegaRAID command to delete the existing RAID configuration:
# -CfgLdDel -LALL -a0
Enter the following command to create a RAID1 partition with two virtual drives of size 100 GB and 657 GB:
# -CfgLdAdd -r1[252:0, 252:1] WB Direct NoCachedBadBBU -sz102400 -sz734688 -a0
Enter the following command to create a RAID5 partition with the remaining drives:
# -CfgLdAdd -r5[252:2, 252:3, 252:4, 252:5] WB Direct NoCachedBadBBU -a0
In the left pane of the ILOM, expand Host Management, then select Power Control. In the Select Action list, select Power Cycle, then click Save.
The Exalytics Machine restarts.
The X4-4 Exalytics Machine comprises six hard drives, each having a capacity of 1.2 TB. Two drives are configured as RAID1 and four drives are configured as RAID5. To optimize the use of the disk space, you must reconfigure the RAID1 and RAID5 configurations on the Exalytics Machine. Reconfigure RAID1 so that it consists of two virtual drives of 100 GB and 1000 GB, and RAID5 consists of the remaining drives.
To reconfigure existing RAID configurations on the X4-4 Exalytics Machine:
Restart the Exalytics Machine using Integrated Lights Out Manager (ILOM).
Press Ctrl+Y and enter RAID CLI (Command Line Interface) as the Exalytics Machine is restarting.
Note:
The "Copyright LSI Logic Corporation" displays during the restart sequence when it is possible to enter the RAID CLI. Observe the screen carefully as the message displays for a very short time. This avoids restarting the machine again.Enter the following MegaRAID command to delete the existing RAID configuration:
# -CfgLdDel -LALL -a0
Enter the following command to create a RAID1 partition with two virtual drives of size 100 GB and 1000 GB:
# -CfgLdAdd -r1[252:0, 252:1] WB Direct NoCachedBadBBU -sz102400 -sz999000 -a0
Enter the following command to create a RAID5 partition with the remaining drives:
# -CfgLdAdd -r5[252:2, 252:3, 252:4, 252:5] WB Direct NoCachedBadBBU -a0
In the left pane of the ILOM, expand Host Management, then select Power Control. In the Select Action list, select Power Cycle, then click Save.
The Exalytics Machine restarts.
The X5-4 Exalytics Machine comprises six hard drives, each having a capacity of 1.2 TB. Two drives are configured as RAID1 and four drives are configured as RAID5. To optimize the use of the disk space, you must reconfigure the RAID1 and RAID5 configurations on the Exalytics Machine. Reconfigure RAID1 so that it consists of two virtual drives and RAID5 consists of the remaining drives.
To reconfigure existing RAID configurations on the X5-4 Exalytics Machine:
Restart the Exalytics Machine using Integrated Lights Out Manager (ILOM).
At the prompt, Press Ctrl><R> for WebBIOS... , press Ctrl+Y to access the LSI MegaRAID utility as the Exalytics Machine is restarting.
Note:
Observe the screen carefully as the Press Ctrl><R> for WebBIOS... .message displays for a very short time. This avoids restarting the machine again.The Virtual Drive Management screen is displayed.
Delete the existing RAID configuration, by performing the following actions:
Select the first virtual drive and Press F2.
Select Delete VD.
At the prompt, Press Yes.
Repeat the above steps (a to c) to delete the second virtual drive.
Create a RAID1 partition of two virtual drive, by performing the following actions:
On the Virtual Drive Management screen, Press F2.
Select Create Virtual Drive.
The Create New VD screen is displayed.
In the RAID Level drop down field, select RAID1.
Under Basic Settings, in the Size field, enter 100.
Select Advanced.
The Create Virtual Drive-Advanced screen is displayed.
Select Initialize, and then select OK.
The "Initialization complete on VD 0" message is displayed.
Select OK.
The Virtual Drive Management screen displays the 100 GB virtual disk created.
To create the second virtual drive, select Drive Group: 0, RAID1, press F2, and then select Add New VD.
In the RAID Level drop down field, select RAID1.
Under Basic Settings, in the Size field, accept the default value, and select Advanced.
Select Initialize, and then select OK.
The "Initialization complete on VD 1" message is displayed.
Select OK.
The Virtual Drive Management screen displays the RAID1 partition created of two virtual drives.
Create a RAID5 partition with the remaining drives, by performing the following actions:
On the Virtual Drive Management screen, select LSI MegaRAID, press F2, and then select Create Virtual Drive.
The Create New VD screen is displayed.
In the RAID Level drop down field, select RAID5.
Select the four virtual drives (02, 03, 04, 05).
Note:
For each virtual drive, accept the default size of the drive.Select Advanced.
Select Initialize, and then select OK.
The "Initialization complete on VD 2" message is displayed.
Select OK.
The Virtual Drive Management screen displays the RAID5 partition created of four four virtual drives.
In the left pane of the ILOM, expand Host Management, then select Power Control. In the Select Action list, select Power Cycle, then click Save.
The Exalytics Machine restarts.
If you are on a virtual Exalytics virtualization and want to revert back to a nonvirtual Exalytics deployment, you must reset the RAID configuration by performing the following steps:
To reset RAID configuration:
Restart the Exalytics Machine using Integrated Lights Out Manager (ILOM).
Press Ctrl+Y and enter RAID CLI (Command Line Interface) as the Exalytics Machine is restarting.
Note:
The "Copyright LSI Logic Corporation" displays during the restart sequence when it is possible to enter the RAID CLI. Observe the screen carefully as the message displays for a very short time. This avoids restarting the machine again.Enter the following MegaRAID command to delete the existing RAID configuration:
# -CfgLdDel -LALL -a0
Enter the following command to restore the RAID1 partition to an Exalytics deployment:
# -CfgLdAdd -r1[252:0, 252:1] WB Direct NoCachedBadBBU -a0
Enter the following command to create a RAID5 partition with the remaining drives:
# -CfgLdAdd -r5[252:2, 252:3, 252:4, 252:5] WB Direct NoCachedBadBBU -a0
In the left pane of the ILOM, expand Host Management, then select Power Control. In the Select Action list, select Power Cycle, then click Save.
The Exalytics Machine restarts.
This section includes the following topics:
Section 5.1.2.1, "Installing and Configuring Oracle VM Server"
Section 5.1.2.2, "Installing and Configuring Oracle VM Manager"
Section 5.1.2.3, "Upgrading to Oracle Exalytics Release 2 on a Virtualized Environment"
This section includes the following topics:
To install Oracle VM Server 3.2.9:
Navigate to the Oracle Software Delivery Cloud web site at the following link:
In the Select a Product Pack list, select Oracle Business Intelligence.
In the Platform list, select Linux X86-64.
Click Go.
Select Oracle Exalytics Software Media Pack for Linux x86-64 (Release 2.0.0.0).
Click Continue.
Download and unzip the Oracle Exalytics Base Image 2.2.0.0.0 for Exalytics Oracle VM x86-64 (Part number V76307-01) to a local directory.
The zip file contains the following iso files:
Exalytics_2.2.0.0.0_X3-4_OVS3.2.9_751_<DATE>.iso: You use this iso file to install Oracle VM Server 3.2.9 on an X2-4 or X3-4 Exalytics Machine.
Exalytics_2.2.0.0.0_X4-4_OVS3.2.9_751_<DATE>.iso: You use this iso file to install Oracle VM Server 3.2.9 on an X4-4 Exalytics Machine.
On the Exalytics Machine, connect and log on to Oracle Integrated Lights Out Manager (ILOM).
Note:
If you are installing Oracle VM Server 3.2.9 on an X2-4 or X3-4 Exalytics Machine, you must use ILOM 3.1.2.24.d or later version. If you are installing Oracle VM Server 3.2.9 on an X4-4 or X5-4 Exalytics Machine, you must use ILOM 3.2.4.18 or later version.For the latest Exalytics certified ILOM versions, see the Oracle Exalytics Certification Matrix. The Oracle Exalytics Certification Matrix is located at:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
On the Summary Information screen, under Actions, click Launch to launch the Remote Console.
The ILOM remote console is displayed.
Depending on the Exalytics Machine configuration, perform one of the following actions:
For X2-4 or X3-4 machines, from the menu bar, select Devices, then CD-ROM Image to link the Oracle VM Server 3.2.9 image for X2-4 or X3-4 machine (Exalytics_2.2.0.0.0_X3-4_OVS3.2.9_751_<DATE>.iso) as a remote virtual CD-ROM in ILOM.
For X4-4 or X5-4 machines, from the menu bar, select KVMS, then Storage. Click Add to link to the Oracle VM Server 3.2.9 image for X4-4 or X5-4 machine (Exalytics_2.2.0.0.0_X4-4_OVS3.2.9_751_<DATE>.iso) as a remote virtual CD-ROM in ILOM. Click Connect.
In the left pane of the ILOM, expand Host Management, then select Host Control. In the Next Boot Device list, select CDROM, then click Save.
Restart the machine by expanding in the left pane of the ILOM, Host Management, then select Power Control. In the Select Action list, select Power Cycle, then click Save.
The Exalytics Machine restarts and displays the Oracle VM Server screen.
Press Enter to install Oracle VM Server.
The Oracle VM Server is installed on the Exalytics Machine. After Oracle VM Server is installed, the Exalytics Machine restarts automatically.
To install Oracle VM Server 3.3.3:
Navigate to My Oracle Support (MOS) and download the patch number 22546910.
Download the package and unzip to a local directory.
The downloaded zip file contains Exalytics_2.2.0.0.0_X5-4_OVS3.3.3_<DATE>.iso and a patch file p20431965_20001_Linux-x86-64.zip.
On the Exalytics Machine, connect and log on to Oracle Integrated Lights Out Manager (ILOM).
Note:
For the latest Exalytics certified ILOM versions, see the Oracle Exalytics Certification Matrix. The Oracle Exalytics Certification Matrix is located at:http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
On the Summary Information screen, under Actions, click Launch to launch the Remote Console.
The ILOM remote console is displayed.
From the menu bar, select KVMS, then Storage. Click Add to link to the Oracle VM Server 3.3.3 image for X5-4 machine (Exalytics_2.2.0.0.0_X4-4_OVS3.3.3<DATE>.iso) as a remote virtual CD-ROM in ILOM. Click Connect.
In the left pane of the ILOM, expand Host Management, then select Host Control. In the Next Boot Device list, select CDROM, then click Save.
Restart the machine by expanding in the left pane of the ILOM, Host Management, then select Power Control. In the Select Action list, select Power Cycle, then click Save.
The Exalytics Machine restarts and displays the Oracle VM Server screen.
Press Enter to install Oracle VM Server.
The Oracle VM Server is installed on the Exalytics Machine. After Oracle VM Server is installed, the Exalytics Machine restarts automatically.
Perform the following postinstallation steps to configure the network on Oracle VM Server.
Editing the /etc/sysconfig/network File
You edit the /etc/sysconfig/network file to add the hostname of the machine and gateway and netmask for the network.
To edit the /etc/sysconfig/network file:
Navigate to and open the /etc/sysconfig/network file in a text editor.
Change the HOSTNAME to the name of the machine.
Enter the GATEWAY and NETMASK for the network.
For example:
NETWORKING=yes
NETWORKING_IPV6=no
GATEWAY=xx.xxx.xxx.x
NETMASK=xxx.xxx.xxx.x
HOSTNAME=<name of the machine>
Save the file.
You configure bond0 by editing the ifcfg-bond0 file.
To edit the ifcfg-bond0 file:
Navigate to and open the /etc/sysconfig/network-scripts/ifcfg-bond0 file in a text editor.
Change the BOOTPROTO to static.
For example:
BOOTPROTO=static
Add the IP Address of the machine.
For example:
IPADDR=xx.xxx.xx.xxx
To edit the hosts file:
Navigate to and open the /etc/hosts file in a text editor.
Add the IP Address, host name, and alias for the host.
For example:
xx.xxx.xx.xxx exalyticsHost1.mycompany.com.exalytics Host1
Note:
Ensure the IP Address of the host is the same as the IP Address you entered in the ifcfg-bond0 file.To edit the resolve.conf file:
Navigate to and open the /etc/resolve.conf file in a text editor.
Enter the DNS Server name and the Search base.
For example:
nameserver xxx.xxx.xxx.xxx
search xxx.mycompany.com
Note:
You can create additional bonded ports from Oracle VM Manager after the server is registered. See "Creating a New Network Channel for Virtual Machines."Restarting the Exalytics Machine
To restart the Exalytics Machine:
In the left pane of the ILOM, expand Host Management, then select Power Control.
In the Select Action list, select Power Cycle, then click Save.
You upgrade the Exalytics Base Image for Oracle VM 2.2.0.0.0 by applying the patch on Oracle VM Server. The patch upgrades the Base Image to 2.2.0.0.0, installs Flash drivers and utilities.
To upgrade Oracle Exalytics Base Image for Oracle VM to 2.2.0.0.0:
Use the appropriate patch for the machines:
For X5-4 machine using Oracle VM Server 3.3.3, use the patch file p20431965_20001_Linux-x86-64.zip downloaded in Section 5.1.2.1.2, "Installing Oracle VM Server 3.3.3 on X5-4 Machines."
For X4-4 and earlier machines, navigate to My Oracle Support and download patch number 20431965: Patchset Upgrade Utility for Exalytics Base Image 2.2.0.0.0 Oracle VM for Linux x86-64. The patch contains the p2.6.39-400.248.3.el6uek x86_64.zip file. The zipped file contains Flash drivers and Flash configurator scripts.
Log on to the Exalytics Machine as the root user.
Extract the contents of the file into an appropriate directory on the Exalytics Machine.
Unzip the file into a temporary (/tmp) directory.
The following directory is created:
exalytics_ovs_server_base_image_upgrade_to_2.2.0.0.0.
Navigate to the directory by entering the following command:
# cd exalytics_ovs_server_base_image_upgrade_to_2.2.0.0.0
To upgrade the Base Image to 2.2.0.0.0 and to install Flash, enter the following command:
# ./update.sh
The output looks similar to the following:
current_kernel_version=2.6.39-400.215.9.el5uek
minimum_kernel_version=2.6.39-400.215.9.el5uek
OS Version check passed..
Update to 2.2.0.0.0.ovs-3.2.9 starting at DAY-DD-MM-YYYY HR:MIN:SEC
Removing unnecessary packages...
Skipping removing rpm kernel-ib-devel as it doesn't exist...
Skipping removing rpm kernel-ib as it doesn't exist...
Skipping removing rpm ibvf-config as it doesn't exist...
Removing RPM OpenIPMI-tools ...
Done
Running new install steps...
Preparing... ################################################## [100%]
exalogic.tools ################################################## [100%]
--------------------------------------------------------
Successfully installed exalogic.tools
--------------------------------------------------------
.....[exalogic.tools] := Post Transaction called...............
Running update...
Applying libibumad
Preparing... ################################################## [100%]
libibumad ################################################## [100%]
Preparing... ################################################## [100%]
libibmad ################################################## [100%]
Preparing... ################################################## [100%]
openib ################################################## [100%]
Preparing... ################################################## [100%]
opensm-libs ################################################## [100%]
opensm ################################################## [100%]
error: Failed dependencies:
infiniband-diags is needed by ovsvf-config-1.0-10.noarch
Preparing... ################################################## [100%]
infiniband-diags ################################################## [100%]
Preparing... ################################################## [100%]
exalytics-flash ################################################## [100%]
postInstall (exalytics-flash) 1 ...
[EXALYTICS_INFO:GENERAL] Updating exalytics-flash-config file to set FLASH_INSTALL_TYPE=OVS ...
postInstall (exalytics-flash) 1; done
Preparing... ################################################## [100%]
Installing....
Lib_Utils ################################################## [100%]
MegaCli ################################################## [100%]
Preparing... ################################################## [100%]
hesiod ################################################## [100%]
autofs ################################################## [100%]
sas_snmp ################################################## [100%]
Starting snmpd
Starting snmpd: [ OK ]
Registering Service lsi_mrdsnmpd
Starting LSI SNMP Agent
Starting LSI SNMP Agent:LSI MegaRAID SNMP Agent Ver 3.18.0.2 (Oct 30th, 2012) Started
[ OK ]
Preparing... ################################################## [100%]
policycoreutils-1.33.12-14.8.el5
oracle-hmp-libs ################################################## [100%]
oracle-hmp-hwmgmt ################################################## [100%]
/usr/sbin/semanage: SELinux policy is not managed or store cannot be accessed.
ipmiflash ################################################## [100%]
ipmitool ################################################## [100%]
mstflint ################################################## [100%]
oracle-hmp-snmp ################################################## [100%]
oracle-hmp-tools ################################################## [100%]
oracle-hmp-tools-biosconfig############################################# [100%]
oracle-hmp-tools
ubiosconfig ################################################## [100%]
QConvergeConsoleCLI ################################################## [100%]
Preparing... ################################################## [100%]
package glibc-common-2.5-123.0.1.el5_11.1.x86_64 is already installed
package glibc-2.5-123.0.1.el5_11.1.x86_64 is already installed
package glibc-2.5-123.0.1.el5_11.1.i686 is already installed
package nscd-2.5-123.0.1.el5_11.1.x86_64 is already installed
Removing bm flash scripts...
Running post install script...
Running post patch script
Setting SET_IPOIB_CM=yes
file /etc/sysconfig/network-scripts/ifcfg-bondib0 not found
/usr/lib/init-exalogic-node/init-ipoib.sh not exist in /etc/rc.local , nothing to delete
Completed post patch script
Enabling services...
Updating dom0 memory to 16G..
Copying Exa* files...
Updating imageinfo...
Image name in imageinfo is already uptodate
finished; DAY-DD-MM-YYYY HR:MIN:SEC
finished; DAY-DD-MM-YYYY HR:MIN:SEC
To verify that the upgrade was successful, enter the following command:
# imageinfo
The output looks similar to the following:
Exalytics 2.2.0.0.0.ovs-3.2.9 (build:r20150409.1) Image version : 2.2.0.0.0.ovs-3.2.9 Image build version : 20150409.1 Creation timestamp : 2015-04-22_11-30-58 Kernel version : 2.6.39-400.215.9.el5uek Image activated : 2015-04-22_11-30-58 Image status : SUCCESS
To verify that Flash is installed and the number of Flash cards installed, enter the following command:
# ddcli
For an X2-4 or X3-4 configuration, six Flash cards are displayed. The output looks similar to the following:
**************************************************************************** LSI Corporation WarpDrive Management Utility Version 107.00.00.04 (2012.06.05) Copyright (c) 2011 LSI Corporation. All Rights Reserved. **************************************************************************** ID WarpDrive Package Version PCI Address -- --------- --------------- ----------- 1 ELP-4x100-4d-n 08.05.01.00 00:11:00:00 2 ELP-4x100-4d-n 08.05.01.00 00:21:00:00 3 ELP-4x100-4d-n 08.05.01.00 00:31:00:00 4 ELP-4x100-4d-n 08.05.01.00 00:a1:00:00 5 ELP-4x100-4d-n 08.05.01.00 00:c1:00:00 6 ELP-4x100-4d-n 08.05.01.00 00:d1:00:00 Select the WarpDrive [1-6 or 0:Quit]: 0
Note:
For an X4-4 and X5-4 configuration, three Flash cards are displayed.You install and configure Oracle VM Manager, as described in the following sections:
Section 5.1.2.2.1, "Installing Oracle VM Manager 3.2.9 on Exalytics X2-4, X3-4, and X4-4 Machines"
Section 5.1.2.2.2, "Installing Oracle VM Manager 3.3.3 on Exalytics X5-4 Machines"
Section 5.1.2.2.4, "Creating Virtual Network Interface Controllers"
Section 5.1.2.2.5, "Creating Server Pools and Adding a Server"
Oracle recommends that you install Oracle VM Manager on a separate machine than the Exalytics Machine, preferably colocated geographically within Oracle VM Server.
To install Oracle VM Manager 3.2.9:
Download patch number 16410417 from the My Oracle Support web site at the following link:
Install Oracle VM Manager 3.2.9. For instructions, see Chapter 4, "Installing Oracle VM Manager" in Oracle VM Installation and Upgrade Guide for Release 3.2. The guide is located at:
Oracle recommends that you install Oracle VM Manager on a separate machine than the Exalytics machine, preferably colocated geographically within Oracle VM Server. OVM Manager 3.3.3 is only supported with X5-4 servers due to NVMe hardware incompatibility in OVM Manager 3.2.9.
To install Oracle VM Manager 3.3.3:
Download Oracle VM Manager patch number 20492250 from the following link:
http://www.oracle.com/technetwork/server-storage/vm/downloads/index.html
Unzip the downloaded file. It should contain the installer ISO file.
Mount the ISO file to a directory as the root user with the following command:
#mkdir /OVMCD
#mount –o loop ovmm-3.3.3-installer-OracleLinux-b1085.iso /OVMCD
Run the Oracle VM Manager installer using the following commands:
#cd /OVMCD
#./ createOracle.sh
#./runInstaller.sh
Install Oracle VM Manager 3.3.3. For instructions, see "Installing Oracle VM Manager" in Oracle VM Installation and Upgrade Guide for Release 3.2. The guide is located at:
Adding Oracle VM Servers to your Oracle VM Manager environment is known as discovering Oracle VM Servers. Discovering servers is the first step to configuring the virtualization environment.
To discover Oracle VM Servers:
Connect to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane, right-click Server Pools, and then select Discover Servers.
The Discover Dialog box is displayed.
Enter the following information for the server:
Oracle VM Agent Port. The default port number is 8899.
Oracle VM Agent Password. The default password is "oracle".
IP Address.
Click OK.
Oracle VM Server and its details, including number of processors, IP address, processor speed, RAM, networking ports and configuration are discovered and added to the Unassigned Servers folder.
For more information, see "Chapter 6, Managing Server Pools and Oracle VM Servers" in Oracle VM User's Guide for Release 3.2.
A Virtual Network Interface Controller (VNIC) is used by virtual machines as network cards. You create virtual network interfaces by defining a range of MAC addresses to use for each VNIC. Each MAC address corresponds with a single virtual Network Interface Controller (NIC), which is used by a virtual machine.
To create Virtual Network Interface Controllers:
Log on to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane, right-click Server Pools, and then select Create VNICs.
The MAC selector panel is displayed.
Click Next to retrieve the next available MAC addresses.
Select the number of addresses that you want to create, and click Create.
Note:
Select the number of addresses that corresponds to the number of virtual machines you are deploying.The VNICs are created and listed in the Virtual NIC table.
Click Close.
For more information, see "Chapter 7, Managing Virtual Machines" in Oracle VM User's Guide for Release 3.2.
A server pool consists of at least one Oracle VM Server. If you find a server pool does not have sufficient resources, such as CPU or memory, to run the virtual machines, you can expand the server pool by adding more Oracle VM Servers.
Before creating a server pool, you must have:
An IP address for the server pool
An IP address for each virtual machine
The password to access the Oracle VM Agent installed on Oracle VM Server
For information on creating server pools and adding servers, see "Chapter 6, Managing Server Pools and Oracle VM Servers" in Oracle VM User's Guide for Release 3.2.
Note:
When creating a server pool, you must deselect the Activate Cluster option.A repository stores Oracle VM resources, such as virtual machines, templates for creating virtual machines, virtual machine assemblies, and so on.
Note:
Oracle recommends that you create a repository on each physical disk available. Use the smaller repository to store Oracle VM templates and cloned virtual machines and the larger repository to store virtual drives that are assigned to the virtual machines.You use Oracle VM Manager to create and configure Exalytics repositories, and to present the repositories to Oracle VM Servers.
To create an Exalytics repository:
Log on to Oracle VM Manager.
Select the Repositories tab.
In the toolbar, click Create New Repository to display the Create a Data Repository dialog.
Perform the following actions:
In the Repository Name field, enter the name for the repository.
For Repository Location, select Physical Disk and click Search.
From the drop-down list, select a local storage array and select the smaller of the two storage drives.
Click OK.
Select the server pool for the repository.
Click Next.
The new repository is available to be presented to Oracle VM Server. To enable your Oracle VM Server to use the repository, you must present the repository to Oracle VM Server.
Select and move Oracle VM Server from the Servers field to the Present to Server(s) field and click Finish.
The repository is listed in the Repository tab.
For more information, see "Chapter 4, Managing Storage" in Oracle VM User's Guide for Release 3.2.
You create a VM Network channel in Oracle VM Manager to enable Oracle VM Guests in the server pool to communicate with each other and also to communicate with external networks. The VM Network channel instructs Oracle VM Servers to create a Xen bridge that controls network traffic to and from Oracle VM Guests.
A Server Management Network channel that enables communication between Oracle VM Manager and Oracle VM Servers is automatically created by Oracle VM Manager. You can use this existing Server Management Network channel to communicate with virtual machines, or create a new network channel.
Note:
Oracle recommends that you create a new network channel for the virtual machines.To create a VM Network Channel, follow the procedures described in one of the following topics:
Using the Existing Server Management Network Channel for Virtual Machines
For simple network deployments, you can use the default Server Management Network channel to communicate with virtual machines.
To use the Existing Server Management Network channel for Virtual Machines:
Log on to Oracle VM Manager.
Select the Networking tab.
Select the Server Management Network channel address.
Note:
The Server Management Network channel address is similar to the Gateway address you entered except the trailing digit at the end of the address is a zero. For example, if you entered 10.244.138.1 as the Gateway address, the Server Management Network channel address is displayed as 10.244.138.0.Click the Edit icon.
The Edit Network screen in displayed.
To enable the virtual machine to connect the Server Management Network channel, select Virtual Machine.
Click Next.
Accept the default server settings, and click Next.
Accept the default port settings, and click Next.
Click Finish.
The Virtual Machine column against the Server Management Network channel address displays a check mark indicating that the virtual machine is connected to the network.
Creating a New Network Channel for Virtual Machines
Before you can create a new network channel you must connect additional Ethernet cable to the Gigabit Ethernet connector ports and create a new bonded port through the Oracle VM Manager user interface.
Note:
The following procedure describes how to create and use a bonded port for the network channel. If you need to, you can use a single ethernet port for the channel instead of a bond. Oracle recommends using a bonded port.To create a new bonded port and network channel:
Log on to Oracle VM Manager.
Select the Servers and VMs tab.
To create a new bonded port, perform the following tasks:
In the left pane, expand Server Pools, and then select the Exalytics Machine on which the Oracle VM Server is running.
In the Perspective list, select Bond Ports.
Click Create Bond Port.
The Create Bond Port page is displayed.
In the Addressing list, select IP Address.
In the IP Address field, enter an IP address for the bond.
In the Mask field, enter a Netmask for the bond.
Leave the MTU field at the default number.
Enter a description for the bond.
In the Available Ports section, select the connected ports and move it to the Selected Ports section.
Click OK.
To create a new network channel, perform the following tasks:
Select the Networking tab.
Click Create New Network.
The Create Network page is displayed.
Select Create a network with bond/ports only, and click Next.
In the Name field, enter a name for the network.
Enter a description.
Select Virtual Machine, and then click Next.
In the Available Servers section, select the server on which the Oracle VM Manager is running, move it to the Selected Servers section, and then click Next.
In the Available Ports section, select the bonded port you created in Step 3, move it to the Selected Ports section, and then click Next.
The Ports page is displayed.
Confirm the settings on the Ports page and then click Finish.
For more information, see "Chapter 5, Managing Networks" in Oracle VM User's Guide for Release 3.2.
New customers must upgrade to Oracle Exalytics Release 2 (2.0.0.0) on the virtualized environment. For instructions, see "Upgrading to Oracle Exalytics Release 2 (2.2.0.0.0.ovs-3.2.9) on Virtual Deployments."
You use virtual templates to create virtual machines. The process of creating a virtual machine from a template is known as cloning. Before you create virtual machines, ensure that you have the following resources available:
A server pool
An Oracle VM Server
VM templates
The process of creating virtual machines from templates consists of the following steps:
Section 5.1.2.4.2, "Importing VM Templates into Oracle VM Manager"
Section 5.1.2.4.3, "Creating Virtual Machines from VM Templates"
To download VM templates:
Download and save the Exalytics Oracle Release 2 VM Template (2.2.0.0.0) for Exalytics Oracle VM x86-64, by performing the following steps:
Navigate to the Oracle Software Delivery Cloud web site at the following link:
In the Select a Product Pack list, select Oracle Business Intelligence.
In the Platform list, select Linux X86-64.
Click Go.
Select Oracle Exalytics Software Media Pack for Linux x86-64 Release: 2.0.0.0.
Click Continue.
Depending on the Linux operating system, perform one of the following actions:
To install VM template on a Linux 5 operating system, download the Oracle Exalytics Oracle VM Template 2.2.0.0.0.el5, Part Number: V76308-01.
To install VM template on a Linux 6 operating system, download the Oracle Exalytics Oracle VM Template 2.2.0.0.0.el6, Part Number:V76309-01
Save the template on a web server.
After downloading the templates, you import them into Oracle VM Manager.
To import VM templates into Oracle VM Manager:
Log on to Oracle VM Manager.
Select the Repositories tab.
In the left pane, select the Repository in which you want to store the template.
Select VM Templates.
In the toolbar, click Import VM Template to display the Import VM Template dialog.
Select the Oracle VM Server and enter the HTTP or FTP URL to the VM template that you downloaded on the web server.
Click OK to import the VM template.
After importing the template in Oracle VM Manager, you use the template to create a virtual machine.
Note:
Oracle recommends that you use Oracle VM Manager to create virtual drives of the sizes required for your system on the larger repository. Associate these virtual drives with the virtual machines deployed on your system. These virtual drives provide enough storage for installing the Exalytics software and the various files associated with the Exalytics Machine.Before you create virtual machines, keep the following guidelines in mind:
Ensure that Hyperthreading is disabled on Oracle VM Server.
Note:
Oracle recommends that Hyperthreading be disabled when creating new virtual machines.Maximum number of virtual machines you can create for a non-InfiniBand configuration on an X2-4, X3-4, X4-4, and X5-4 Exalytics Machine is ten.
Total virtual processors (vCPUs) you can assign on Oracle VM Server for an X2-4, X3-4, X4-4, and X5-4 Exalytics Machine is ten.
Total memory you can allocate on Oracle VM Server for an X2-4, X3-4, X4-4, and X5-4 Exalytics Machine is 16 GB.
Review Table 5-1 for the total vCPUs and memory you can allocate on all virtual machines and the maximum vCPUs and memory you can allocate to each virtual machine.
Table 5-1 Total and Maximum vCPUs and Memory Allowed For Virtual Machines
| System | Total vCPUs for all Virtual Machines | Maximum vCPUs for each Virtual Machine | Total RAM for all Virtual Machines | Maximum RAM for each Virtual Machine |
|---|---|---|---|---|
|
X2-4 |
40 |
28 |
984 GB |
800 GB |
|
X3-4 |
40 |
28 |
984 GB |
800 GB |
|
X4-4 |
60 |
28 |
1984 GB |
800 GB |
|
X5-4 |
72 |
28 |
1984 GB |
800 GB |
Note:
For the X2-4 and X3-4 Exalytics Machine, total memory on Oracle VM Server (16 GB) and all virtual machines (984 GB) cannot exceed 1000 GB. For the X4-4 and X5-4 Exalytics Machine, total memory on Oracle VM Server (16 GB) and all virtual machines (1984 GB) cannot exceed 2000 GB.To create virtual machines from a VM template:
Log on to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane toolbar, click Create Virtual Machine.
The Create Virtual Machine dialog is displayed.
Select Clone from an existing VM Template.
Perform the following actions:
In the Clone Count list, select the number of machines you want to clone.
In the Repository list, select a repository for the machine.
In the VM Template list, select the VM template from which you want to create the virtual machine.
Enter a name for the virtual machine.
In the Server Pool list, select a server pool.
Enter a description for the virtual machine.
Click Finish.
The virtual machine is created and is ready to be configured.
To configure and start a virtual machine, configure a network on a virtual machine, and configure SWAP on a virtual machine, see Section 5.6, "Maintaining Virtual Machines."
For more information, see "Chapter 7, Managing Virtual Machines" in Oracle VM User's Guide for Release 3.2.
If you are an existing customer running Oracle VM 3.0.3 or a later version, you must perform the following tasks:
Upgrade to Oracle VM Server 3.2.9 and Oracle VM Manager 3.2.9. See Section 5.3, "Upgrading Oracle VM Manager and Oracle VM Server to 3.2.9."
Upgrade to Oracle Exalytics Release 2 on the virtualized environment. See Section 5.4, "Upgrading to Oracle Exalytics Release 2 on a Virtualized Environment."
This section includes the following topics:
Note:
Oracle recommends that you use the same release version of Oracle VM Manager and Oracle VM Server. This section is applicable to Exalytics X2-4, X3-4 and X4-4 servers only.If you are a new or existing customer running Oracle VM Server 3.0.3 or later version, you must upgrade to Oracle VM Server 3.2.9. For instructions, see Section 3.5.2, "Upgrading Oracle VM Server 3.0.3 (Base Image 2.0.1.1) or Later Version to Oracle VM Server 3.2.9."
Note:
If you have already installed Oracle VM Manager 3.2.9, you can ignore this section.If you are an existing customer running Oracle VM Manager 3.0.3 or later version, you must upgrade to Oracle VM Manager 3.2.9. For instructions, see Section 3.5.1, "Upgrading Oracle VM Manager 3.0.3 or Later version to Oracle VM Manager 3.2.9."
Both new and existing customers must upgrade to Oracle Exalytics Release 2 on the virtualized environment. For instructions, see "Upgrading to Oracle Exalytics Release 2 (2.2.0.0.0.ovs-3.2.9) on Virtual Deployments."
Note:
If you are an existing customer and have already installed and configured software on the virtual Exalytics Machine, you can ignore this section.The process of installing Exalytics software on virtual machines is identical to installing the software on the non-virtual Exalytics Machine, except that the virtual machines cannot access the entire Exalytics memory. Keep in mind this limitation when setting kernel parameters related to shared memory or creating hugepages.
This section consists of the following topics:
Section 5.5.1, "Prerequisites to Installing and Configuring Exalytics Software on Virtual Machines"
Section 5.5.2, "Installing and Configuring Exalytics Software on Virtual Machines"
The following prerequisites must be met before installing the Exalytics software on the virtual machines:
You have created a virtual machine.
You have created a virtual disk and associated it with the virtual machine.
For more information on creating virtual machines and virtual disks, see "Chapter 7, Managing Virtual Machines" in Oracle VM User's Guide for Release 3.2.
This section consists of the following topics:
Section 5.5.2.2, "Modifying the Oracle User and Granting Permissions"
Section 5.5.2.3, "Installing Application Software Components"
Before you can install the Exalytics software, you create and mount a /u01 partition on the virtual disk.
Note:
The following procedure assumes the /u01 partition size of 1.6TB. Depending on your specific needs and configuration, you can use a different size for the /u01 partition.To create and mount a /u01 partition:
After logging in as the root user, configure the /u01 directory on the virtual disk using commands such as the following ones:
To create a partition, enter the following commands:
parted /dev/xvdb
GNU Parted 1.8.1
Using /dev/xvdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel msdos
(parted) mkpart primary 0 1600GB
(parted) print
Model: Xen Virtual Block Device (xvd)
Disk /dev/xvdb: 1600GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 1600GB 1600GB primary
(parted) quit
To create logical volume, enter the following commands:
lvm pvcreate /dev/xvdb1
Physical volume "/dev/xvdb1" successfully created
lvm vgcreate VolGroup01 /dev/xvdb1
Volume group "VolGroup01" successfully created
To view free extents on VolGroup01, enter the following commands:
vgs -o +vg_free_count,vg_extent_count
VG #PV #LV #SN Attr VSize VFree Free Ext
VolGroup01 1 0 0 wz--n- 1.46T 1.46T 381469 381469
lvm lvcreate --extents 381469 --name LogVol00 VolGroup01
Logical volume "LogVol00" created
To create a file system, enter the following command:
mkfs.ext4 /dev/VolGroup01/LogVol00
Add the following line to the /etc/fstab file:
/dev/VolGroup01/LogVol00 /u01 ext4 defaults 0 0
To mount the directory, enter the following commands:
mkdir /u01
mount /u01
Verify that the partition has been created by entering the following command:
df –lh
The Virtual Machine template contains "oracle" as the operating system user name. Associate the user name with the "oinstall" group and create a password for it.
The procedures throughout this section assume a user named "oracle" and a group named "oinstall".
Note:
To add a different user and group, enter the following commands as a root user:groupadd <name of the group>
useradd -g <name of the group> <name of the user>
To modify the Oracle user and grant permissions:
Log in as root user.
Enter the following commands to associate the user name "oracle" with the group "oinstall" and to create a password:
groupadd oinstall
usermod –g oinstall oracle
passwd oracle
Enter the following commands to grant permissions to the /u01 drive where the software is to be installed:
chown oracle:oinstall /u01
chmod 775 /u01
Start the VNC Server on the virtual machine.
The process of installing application software components on a virtual Exalytics Machine is similar to installing them on the non-virtualized Exalytics Machine. See Chapter 6, "Installing Software on an Exalytics Machine."
This section includes the following topics:
Section 5.6.1, "Viewing Virtual Machine Information and Events"
Section 5.6.5, "Increasing the Size of the Root Partition on a Virtual Machine"
You can view virtual machine details and jobs associated with the virtual machine.
To view virtual machine information details:
Log on to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane, select the server pool on which the virtual machine resides.
From the Perspective list, select Virtual Machines.
In the Management pane, select a virtual machine.
Click the expand arrow to the left of the selected virtual machine.
The following tabs are displayed:
Configuration: Displays general information about the virtual machine, such as the minimum and maximum memory and processors, operating system, domain type, high availability status, and so on.
Networks: Displays networks and VNICs used in the virtual machine.
Disks: Displays virtual and physical disks attached to the virtual machine.
To view virtual machine events:
Log on to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane, select the server pool on which the virtual machine resides.
From the Perspective list, select Virtual Machines.
In the Management pane, select a virtual machine.
In the toolbar, click Display Selected VM Events.
The Events dialog is displayed.
Review the jobs associated with the virtual machine.
For more information, see "Chapter 7, Managing Virtual Machines" in Oracle VM User's Guide for Release 3.2.
You start a virtual machine from Oracle VM Manager.
To configure and start a virtual machine:
Log on to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane, select the server pool on which the virtual machine resides.
From the Perspective list, select Virtual Machines.
In the Management pane, select a virtual machine, and from the toolbar click the Edit.
The Edit Virtual Machine dialog is displayed.
Select the Configuration tab.
Select the necessary configuration for the virtual machine, and click OK.
Select the Networks tab.
Select and assign a VNIC to the virtual machine, and click OK.
Select the Disks tab.
Select and allocate the virtual disk to the virtual machine.
Click OK.
From the toolbar, click Start.
The virtual machine starts.
Note:
When you start the virtual machine for the first time, the virtual machine takes approximately fifteen minutes to initialize.For more information, see "Chapter 7, Managing Virtual Machines" in Oracle VM User's Guide for Release 3.2.
After starting a virtual machine, you then configure the network on the virtual machine to enable it to access the network.
To configure a network on the virtual machine:
Log on to Oracle VM Server.
Enter the following command:
xm list
The Domain-0 and UUID number for the virtual machine are displayed.
Execute the following command:
xm console <UUID_NUMBER_FOR_VIRTUAL_MACHINE>
The console of the virtual machine is displayed.
Log in as root user with default password "ovsroot".
Enter the following command:
system-config-network
Edit the eth0 device by entering the following information:
IP addresses
Netmask
Gateway
DNS settings
Click Save and Quit.
Run the following command to reload the network configuration:
service network reload
Edit the /etc/hosts file to add the machine name and IP address.
Each VM guest is created with 1 GB of default swap space. To run Oracle Database In-Memory on an Exalytics Machine, you must increase the swap space to a minimum of 16 GB.
Note:
The following procedure describes how to increase swap space by creating a new virtual disk (/dev/xvdd) of 20 GB.To increase SWAP on the virtual machine:
Add a new virtual disk for the VM guest by performing the following actions:
Log on to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane, select the server pool on which the virtual machine resides.
From the Perspective list, select Virtual Machines.
In the toolbar, click Stop to stop the virtual machine.
Confirm that the virtual machine is stopped.
In the toolbar, click Edit.
The Edit Virtual Machine dialog is displayed.
Click the Disks tab.
Under Disk Type, select Virtual Disk.
Under Actions, click Add.
The Create Virtual Disk dialog is displayed.
In the Virtual Disk Name field, enter a name for the virtual disk, in the Size field, enter 20, and then click OK twice.
In the toolbar, click Start to start the virtual machine.
Add logical volume and create additional swap on the VM guest by performing the following actions:
Log on the Oracle VM Server.
To check details of the new virtual disk, enter the following command:
fdisk -l
The details of the new virtual disk are displayed. For example, if the new virtual disk is /dev/xvdd, an output similar to the following is displayed:
.... Disk /dev/xvdd: 21.4 GB, 21474836480 bytes 255 heads, 63 sectors/track, 2610 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
To create the new partition /dev/xvdd1, enter the following command as the root user:
# fdisk /dev/xvdd
Output similar to the following is displayed:
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. The number of cylinders for this disk is set to 2610. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
At the command prompt, enter n. For example:
Command (m for help): n
The following output is displayed:
Command action e extended p primary partition (1-4) p
At the Partition number prompt, enter 1. For example:
Partition number (1-4): 1
At the First cylinder (1-2610, default 1) prompt, press Enter to use the default value.
The following output is displayed:
Using default value 1
At the Last cylinder or +size or +sizeM or +sizeK (1-2610, default 2610) prompt, press Enter to use the default value.
The following is displayed:
Using default value 2610
At the command prompt, enter t. For example:
Command (m for help): t
The following is displayed:
Selected partition 1
At the Hex code (type L to list codes) prompt, enter 8e.
The following is displayed:
Changed system type of partition 1 to 8e (Linux LVM)
At the command prompt, enter w. For example:
Command (m for help): w
The following is displayed:
The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks.
To create the physical volume for the partition /dev/xvdd1, enter the following command:
# pvcreate /dev/xvdd1
To add the newly formatted disk to the existing volume group, enter the following command:
# vgextend VolGroup00 /dev/xvdd1
To create logical volume, enter the following command:
# lvcreate -L 20G VolGroup00 -n LogVol03
To format the logical volume for swap use, enter the following command:
# mkswap /dev/VolGroup00/LogVol03
To enable swap, enter the following command:
swapon /dev/VolGroup00/LogVol03
To verify the updated swap space, enter the following command:
# cat /proc/swaps
Output similar to the following is displayed:
Filename Type Size Used Priority /dev/mapper/VolGroup00-LogVol01 partition 1048572 0 -1 /dev/mapper/VolGroup00-LogVol03 partition 20971516 0 -2
Add the following line to the /etc/fstab file:
/dev/VolGroup00/LogVol03 swap swap defaults 0 0
Each virtual machine is created by default with a 10 GB root partition. If required, you can increase the size of the default logical volume VolGroup00-LogVol00 mounted at the root "/" directory of a virtual machine.
To increase the size of the root partition on the virtual machine:
Log in to the virtual machine as the root user.
To check the current physical volumes on the virtual machine, enter the following command:
# cat /proc/partitions
Output similar to the following is displayed:
major minor #blocks name 202 0 10485760 xvda 202 1 257008 xvda1 202 2 10225372 xvda2 252 0 7340032 dm-0 252 1 1048576 dm-1 252 2 102400 dm-2
Add a new virtual disk for the VM guest by performing the following actions:
Note:
The following procedure describes how to create a new virtual disk of 100 GB.Log on to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane, select the server pool on which the virtual machine resides.
From the Perspective list, select Virtual Machines.
In the toolbar, click Stop to stop the virtual machine.
Confirm that the virtual machine is stopped.
In the toolbar, click Edit.
The Edit Virtual Machine dialog is displayed.
Click the Disks tab.
Under Disk Type, select Virtual Disk.
Under Actions, click Add.
The Create Virtual Disk dialog is displayed.
In the Virtual Disk Name field, enter a name for the virtual disk, in the Size field, enter 100, and then click OK twice.
In the toolbar, click Start to start the virtual machine.
To check the current partitioning on the virtual machine, enter the following command:
# df -h
Output similar to the following is displayed:
Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00
6.8G 2.9G 3.7G 44% /dev/xvda1
244M 35M 197M 15% /boottmpfs
50G 0 50G 0% /dev/shm/dev/mapper/VolGroup00-LogVol02
97M 5.6M 87M 7% /shared_agent_instance_home
To check the new available physical volumes on the virtual machine, enter the following command:
# cat /proc/partitions
Output similar to the following is displayed:
major minor #blocks name 202 0 10485760 xvda 202 1 257008 xvda1 202 2 10225372 xvda2 202 16 104857600 xvdb 252 0 7340032 dm-0 252 1 1048576 dm-1 252 2 102400 dm-2
Note:
In the above example /dev/xvdb is the newly attached disk.To partition the newly attached disk, perform the following actions:
Enter the following command:
# fdisk /dev/xvdb
Output similar to the following is displayed:
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. The number of cylinders for this disk is set to 13054. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
At the command prompt, enter p. For example:
Command (m for help): p
The following output is displayed:
Disk /dev/xvdb: 107.3 GB, 107374182400 bytes 255 heads, 63 sectors/track, 13054 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System
At the command prompt, enter n. For example:
Command (m for help): n
The following output is displayed:
Command action e extended p primary partition (1-4) p
At the Partition number prompt, enter 1. For example:
Partition number (1-4): 1
At the First cylinder (1-13054, default 1) prompt, press Enter to use the default value.
The following output is displayed:
Using default value 1
At the Last cylinder or +size or +sizeM or +sizeK (1-13054, default 13054) prompt, press Enter to use the default value.
The following is displayed:
Using default value 13054
At the command prompt, enter t. For example:
Command (m for help): t
The following is displayed:
Selected partition 1
At the Hex code (type L to list codes) prompt, enter 8e.
The following is displayed:
Changed system type of partition 1 to 8e (Linux LVM)
At the command prompt, enter p. For example:
The following is displayed:
Disk /dev/xvdb: 107.3 GB, 107374182400 bytes 255 heads, 63 sectors/track, 13054 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/xvdb1 1 13054 104856223+ 8e Linux LVM
At the command prompt, enter w. For example:
Command (m for help): w
The following is displayed:
The partition table has been altered! Calling ioctl() to re-read partition table. WARNING: Re-reading the partition table failed with error 16: Device or resource busy. The kernel still uses the old table. The new table will be used at the next reboot. Syncing disks.
Restart the virtual machine by performing the following actions:
Connect to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane, expand Server Pools, and then select the server pool containing the virtual machine.
Right-click the virtual machine, and select Restart.
To create the physical volume, enter the following command:
# pvcreate /dev/xvdb1
Output similar to the following is displayed:
Writing physical volume data to disk "/dev/xvdb1" Physical volume "/dev/xvdb1" successfully created
To extend the volume group VolGroup00 to the physical volume /dev/xvdb1, enter the following command:
# vgextend VolGroup00 /dev/xvdb1
Output similar to the following is displayed:
Volume group "VolGroup00" successfully extended
To extend the logical volume LogVol00, enter the following command:
# lvextend -l +100%FREE /dev/VolGroup00/LogVol00
Output similar to the following is displayed:
Extending logical volume LogVol00 to 105.22 GB Logical volume LogVol00 successfully resized
To resize the file system, enter the following command:
# resize2fs /dev/VolGroup00/LogVol00
Output similar to the following is displayed:
resize2fs 1.39 (29-May-2006) Filesystem at /dev/VolGroup00/LogVol00 is mounted on /; on-line resizing required Performing an on-line resize of /dev/VolGroup00/LogVol00 to 28481536 (4k) blocks. The filesystem on /dev/VolGroup00/LogVol00 is now 28481536 blocks long.
To verify the resized root partition, enter the following command:
# df -h
Output similar to the following is displayed:
Filesystem Size Used Avail Use% Mounted on/dev/mapper/VolGroup00-LogVol00
106G 2.9G 97G 3% //dev/xvda1
244M 35M 197M 15% /boottmpfs
50G 0 50G 0% /dev/shm/dev/mapper/VolGroup00-LogVol02
97M 5.6M 87M 7% /shared_agent_instance_home