Linux: Getting Started with Virtualization for Powerlinux Getting Started with Virtualization Using IBM Powervm

Linux Getting started with virtualization for PowerLinux

Linux Getting started with virtualization for PowerLinux Note Before using this information and the product it supports, read the information in “Notices” on page 25.

Second Edition (December 2012) © Copyright IBM Corporation 2011, 2012. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents

Getting started with virtualization using Step 1: Connecting to the web-based interface . . 13 IBM PowerVM ...... 1 Step 2: Mirroring the management partition . . 14 What's new in Getting started with virtualization Step 3: Configuring storage on the managed using IBM PowerVM ...... 1 system ...... 15 Installation roadmap for PowerLinux servers Configuring storage for environments with managed by IVM ...... 1 local storage ...... 15 Virtualization concepts ...... 4 Configuring storage environments with a SAN 16 PowerVM for specific Power Systems servers . . 4 Step 4: Configuring virtual Ethernet on the Logical partitioning ...... 5 managed system...... 16 Micro-Partitioning ...... 5 Configuring an HEA or IVE ...... 17 Active Memory sharing...... 7 Configuring an SEA ...... 17 Active Memory deduplication ...... 8 Step 5: Creating client logical partitions ....17 Virtual I/O Server ...... 8 Configuring storage for the installation media . . . 19 Live partition mobility ...... 9 Loading the IBM Installation Toolkit on a client System virtualization management .....10 logical partition ...... 20 Hardware Management Console .....10 Optional additional software for PowerLinux Integrated Virtualization Manager .....10 servers managed by IVM ...... 21 IBM Flex System Manager ...... 11 Related information for virtualization...... 22 Differences between Power Systems and x86 PDF file for Getting started with virtualization using environments ...... 11 IBM PowerVM ...... 22 Installation tools for PowerLinux servers with logical partitions...... 12 Notices ...... 25 Configuring the management partition and client Trademarks ...... 26 logical partitions...... 13

IBM® PowerVM® provides a secure virtualization environment for IBM PowerLinux and Power Systems™ servers running Linux. IBM PowerVM includes Integrated Virtualization Manager (IVM) for creating and managing virtual servers on your PowerLinux™ server.

Note: The information in this topic collection applies to IBM PowerVM for IBM PowerLinux, as well as IBM PowerVM Express Edition, IBM PowerVM Standard Edition, and IBM PowerVM Enterprise Edition.

You can create virtual servers, or client logical partitions, on your PowerLinux server. In each client logical partition, you can run one of the following Linux distributions: v Red Hat Enterprise Linux 6.1 v Red Hat Enterprise Linux 5.7 v SUSE Linux Enterprise Server 11 SP1 v SUSE Linux Enterprise Server 10 SP4 Not all client logical partitions have to run the same Linux distribution.

Then, you can optionally install and run one of the following open source workloads: v File and print server v Mail server v Network infrastructure server v Web server To quickly get started, you can use the installation roadmap to set up a simple configuration.

What's new in Getting started with virtualization using IBM PowerVM Getting started with virtualization using IBM PowerVM introduces the following new topics. Virtualization concepts

Virtualization concepts describes how PowerVM provides virtualization capabilities such as Micro-Partitioning®, Active Memory™ sharing, Active Memory deduplication, a Virtual I/O server for virtual networks and storage, and live partition mobility. Learn more...

Installation roadmap for PowerLinux servers managed by IVM You can quickly set up your IBM PowerLinux server or Power Systems server running Linux by following this installation roadmap through a simple setup.

The following figure shows the installation roadmap for PowerLinux servers that are managed by the Integrated Virtualization Manager (IVM). If you do not plan to use the IVM, see the Installation roadmap for PowerLinux servers (http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/topic/liaay/ install_no_ivm.htm).

Before you start, complete the following prerequisite tasks: 1. Understand the differences in configuration and terminology for Power Systems environments and x86 environments. For information, see “Differences between Power Systems and x86 environments” on page 11. 2. Learn about the tools used to install and configure the system, including IVM, IBM Installation Toolkit for PowerLinux, and the IBM Installation Toolkit Simplified Setup Tool. For information, see “Installation tools for PowerLinux servers with logical partitions” on page 12. 3. Learn about the open source workloads that you can configure with the Simplified Setup Tool. For information, see Open source workload overviews. 4. Understand the resource requirements for each open source workload. For information, see Minimum resource requirements for open source workloads. 5. Verify that the server hardware is installed and the serial console is cabled. For instructions, locate you hardware model in the IBM Systems Hardware Information Center (http://pic.dhe.ibm.com/ infocenter/powersys/v3r1m5/index.jsp?topic=/p7hdx/power_systems.htm).

2 Linux: Getting started with virtualization for PowerLinux 6. Verify that IVM is installed. For instructions, see Installing the Virtual I/O Server and enabling the Integrated Virtualization Manager on IBM Power Systems servers(http://pic.dhe.ibm.com/infocenter/ powersys/v3r1m5/topic/p7hch/iphchinstallvios.htm).

Procedure

Complete the following steps to set up an PowerLinux server that is managed by IVM: 1. Configure the management partition and client logical partitions. For instructions see, “Configuring the management partition and client logical partitions” on page 13. 2. Configure the virtual media library, add the installation media for IBM Installation Toolkit for PowerLinux, and import the installation media for the Linux distribution to the virtual media library. For instructions, see “Configuring storage for the installation media” on page 19. 3. Load the IBM Installation Toolkit for PowerLinux on a client logical partition. For instructions, see “Loading the IBM Installation Toolkit on a client logical partition” on page 20. 4. From the IBM Installation Toolkit for PowerLinux user interface, select the option to install Linux. Complete the wizard to install your Linux distribution and packages on the client logical partition. For instructions, see Install a Linux distribution (http://publib.boulder.ibm.com/infocenter/lnxinfo/ v3r0m0/topic/liaan/ppwelcomeinstalllinux.htm). When you encounter the Insert CD/DVD media page, complete the following steps to mount the Linux distribution media to the virtual optical device: a. In the navigation area of IVM, select View/Modify Partitions under Partition Management. The View/Modify Partitions page is shown. b. Select the client logical partition on which you plan to install Linux. c. From the Tasks menu, select Properties. The Partition Properties page is shown. d. Click the Optical/Tape Devices tab. e. Click Virtual Optical Devices to open the section. f. From the Current Media column of the virtual optical device, click Modify. The Modify Current Media page is shown. g. Select the Linux distribution media and click OK to mount the Linux distribution media to the virtual optical device. h. Click OK on the Optical/Tape Devices tab. i. In the Install Linux wizard in the IBM Installation Toolkit for PowerLinux, click Next on the Insert CD/DVD media page and finish the installation wizard. The IBM Installation Toolkit for PowerLinux installs Linux and restarts the client logical partition. When finished, the virtual terminal window shows a prompt to insert the IBM Installation Toolkit for PowerLinux media into the CD-ROM drive. 5. Determine whether you plan to run an open source workload in the client logical partition: v If yes, go to Step 6. v If no, install the software and applications that you want to run on the client logical partition and then go to Step 9. 6. Access the Simplified Setup Tool: a. In the navigation area of IVM, select View/Modify Partitions under Partition Management. The View/Modify Partitions page is shown. b. Select the client logical partition on which you installed Linux. c. From the Tasks menu, select Properties. The Partition Properties page is shown. d. Click the Optical/Tape Devices tab. e. Click Virtual Optical Devices to open the section. f. From the Current Media column of the virtual optical device, click Modify. The Modify Current Media page is shown.

Getting started with virtualization using IBM PowerVM 3 g. Select the IBM Installation Toolkit for PowerLinux media and click OK to mount the IBM Installation Toolkit for PowerLinux media to the virtual optical device. h. Click OK on the Optical/Tape Devices tab. i. In the virtual terminal window, press Enter to load the IBM Installation Toolkit for PowerLinux. j. When prompted, log in to the client logical partition. k. At the prompt, type welcomecenter and accept the licenses. l. Access the graphical user interface of the IBM Installation Toolkit for PowerLinux by typing the following address in a web browser: https://machineIP:4234

where machineIP is the IP address of the client logical partition. The Welcome Center page is shown in the browser. m. Click Utilities > Simplified Setup Tool. 7. Configure the open source workloads that you want to run. For instructions, see the following resources depending on the workload you want to configure: v Configuring the web server (http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/topic/ liaaz/installconfigwebserv.htm) v Configuring the mail server (http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/topic/ liaaz/configuringmailserver.htm) v Configuring the file and print server (http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/ topic/liaaz/installconfigfileprint.htm) v Configuring the network infrastructure server (http://publib.boulder.ibm.com/infocenter/lnxinfo/ v3r0m0/topic/liaaz/confignetworkinfra.htm) 8. Install and configure any additional management tools or virtualization capabilities. For information, see “Optional additional software for PowerLinux servers managed by IVM” on page 21. Related information: IBM PowerVM Virtualization Introduction and Configuration IBM PowerVM Virtualization Managing and Monitoring Integrated Virtualization Manager on IBM System p5

Virtualization concepts PowerVM provides a secure virtualization environment for the Power® platform. PowerVM for specific Power Systems servers PowerVM capabilities vary by PowerVM edition.

For more information about PowerVM editions, see the topic corresponding to your system in the Systems Hardware Information Center. POWER5 systems PowerVM Editions (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/iphb2_p5/ apv.htm) POWER6® systems PowerVM Editions Overview (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ arecu/arecupowervmeds.htm) POWER7 Systems™ PowerVM Editions overview (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ p7ecu/arecupowervmeds.htm)

4 Linux: Getting started with virtualization for PowerLinux PowerLinux systems PowerVM for IBM PowerLinux overview (http://pic.dhe.ibm.com/infocenter/powersys/ v3r1m5/topic/p7ecul/arecupowervmeds.htm) Logical partitioning Logical partitioning is the ability use a server as if it were two or more independent servers.

You can use logical partitioning to consolidate servers, share system resources, create mixed environments, and run integrated clusters.

Important logical partitioning concepts include: Sharing resources Although each logical partition acts as an independent server, the logical partitions on a server can share some kinds of resources with each other. Managed systems A managed system is a single physical server plus the resources that are connected to the physical server. Manufacturing default configuration The manufacturing default configuration is the initial single partition setup of the managed system as received from your service provider. Physical and virtual hardware resources When you create logical partitions on a managed system, you can assign the physical resources on the managed system directly to logical partitions. You can also share hardware resources among logical partitions by virtualizing those hardware resources.

For more information about logical partitions, see the topic corresponding to your system in the Systems Hardware Information Center. POWER5 systems Logical partition overview (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ iphb2_p5/iphatlparchoices.htm) POWER6 systems Logical partitioning (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/iphat/ iphatlparkickoff.htm) POWER7 Systems Logical partitioning (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/p7hat/ iphatlparkickoff.htm) PowerLinux systems Logical partitioning (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/p7hatl/ iphatlparkickoff.htm) Micro-Partitioning Micro-Partitioning distributes the processing capacity of one or more physical processors among one or more logical partitions. Micro-Partitioning significantly increases overall utilization of processor resources within a system.

You can use Micro-Partitioning to significantly increase utilization of processor resources in your system.

Important Micro-Partitioning concepts include: Processing units of capacity You can configure processing capacity in processor increments of 0.01. You must assign a

Getting started with virtualization using IBM PowerVM 5 minimum processing capacity to a micro-partition. The minimum processing capacity depends upon your hardware and firmware. The following list describes the processing capacity for different Power Systems servers: POWER5 and POWER6 0.1 processors POWER7® See Shared processors (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/ index.jsp?topic=/p7hat/iphatsharedproc.htm) PowerLinux See Shared processors (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/ index.jsp?topic=/p7hatl/iphatsharedproc.htm) For more information about processing capacity, see Use increased Micro-Partitioning limits on a Power system running Linux (https://www.ibm.com/developerworks/mydeveloperworks/ wikis/home?lang=en#/wiki/W51a7ffcf4dfd_4b40_9d82_446ebc23c550/page/Use%20increased %20Micro-Partitioning%20limits%20on%20a%20Power%20system%20running%20Linux). Capped and uncapped mode Capped and uncapped processing modes determine whether processing capacity can exceed entitled capacity when more resources are available in the shared-processor pool. Virtual processors A virtual processor is a representation of a physical processor that is presented to the operating system, which is running in a micro-partition. Virtual processor folding Virtual processor folding puts idle virtual processors into a hibernation state to conserve physical processor resources. Dedicated processors Dedicated processors are whole processors that are assigned to dedicated-processor logical partitions (LPARs). The minimum processor allocation for an LPAR is one whole processor; the maximum is the total number of installed processors in the server. Shared-processor pools Shared-processor pools aggregate processor resources. Shared-processor pools have different characteristics in POWER5 servers than in POWER6 servers and later. POWER5 servers support one shared-processor pool that is called the physical shared-processor pool. POWER6 servers and later support several shared-processor pools that are called multiple shared-processor pools. Shared dedicated capacity On POWER6 servers and later, you can configure dedicated-processor partitions as donating partitions, which donate unused cycles to the shared-processor pool.

For more information about Micro-Partitioning, see the topic corresponding to your system in the Systems Hardware Information Center. POWER5 systems Micro-Partitioning (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/iphb2_p5/ virtmicropart.htm) POWER6 systems Micro-Partitioning technology (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ arecu/iphb1microlpar.htm) POWER7 Systems Micro-Partitioning technology (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ p7ecu/iphb1microlpar.htm)

6 Linux: Getting started with virtualization for PowerLinux PowerLinux systems Micro-Partitioning technology (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ p7ecul/iphb1microlpar.htm) Active Memory sharing With Active Memory sharing, multiple logical partitions can share a common pool of physical memory. Physical memory can be assigned to multiple logical partitions in either a dedicated or shared mode.

You can use Active Memory sharing to create more logical partitions with the same amount of memory, or to decrease the overall system memory requirement.

Active Memory sharing requires POWER6 and later processor technology.

Important Active Memory sharing concepts include: Dedicated and shared-memory You can assign traditional dedicated memory to single logical partitions, and create a memory pool that can be shared among logical partitions. Shared-memory pool The shared-memory pool is a collection of physical memory blocks that are managed as a whole by the hypervisor. The memory in the pool is reserved upon creation, and no longer available for allocation to other dedicated memory partitions. The shared-memory pool is directly managed by the hypervisor for exclusive use by shared-memory partitions. Paging Virtual I/O Server You can configure the Virtual I/O Server to page memory dedicated to the shared-memory pool to a paging device. The paged memory is restored when the data is accessed again. Shared-memory partitions A shared-memory partition is an LPAR that uses memory from the shared-memory pool. A shared-memory partition must use: v Shared processors. v Virtual I/O. v Red Hat Enterprise Linux 6 or SUSE Linux Enterprise Server 11, kernel 2.6.27.25-0.1-ppc64 or later. Logical and physical memory You can configure the amount of logical memory available to a shared-memory partition. You can prioritize the probability that more physical memory is assigned to the partition. Memory classification Linux tags each logical memory page to indicate its importance. The hypervisor uses this information to prioritize the pages that have a lower effect on shared-memory partition performance.

For more information about Active Memory sharing, see the Active Memory Sharing topic for your system in the Systems Hardware Information Center. POWER6 systems http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/arecu/arecuams.htm POWER7 Systems http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/p7ecu/arecuams.htm PowerLinux systems http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/p7ecul/arecuams.htm

Getting started with virtualization using IBM PowerVM 7 Active Memory deduplication Active Memory deduplication reduces shared-memory overcommitment by eliminating memory pages in the same LPAR or across LPARs on the same server.

You can use Active Memory deduplication to minimize the existence of identical memory chunks in main memory space.

Active Memory deduplication requires POWER7 and later processor technology. Active Memory deduplication depends upon “Active Memory sharing” on page 7.

Important Active Memory deduplication concepts include: Active Memory deduplication Active Memory deduplication reduces identical pages that are stored in separate memory chunks into only one page. The reduction occurs even when the identical pages are in different shared-memory partitions. Hypervisor logical memory map The hypervisor logical memory map is a table within PowerVM that maps LPAR memory pages and physical pages. Copy-on write Copy-on-write is a PowerVM mechanism that tracks all deduplicated memory pages. When a shared-memory partition changes a deduplicated page, the hypervisor makes a copy of that deduplicated physical page. The hypervisor then gives the new copy back to the write-requesting shared-memory partition. Other shared-memory partitions continue to reference the deduplicated page. Deduplication table The hypervisor scans and creates signatures for all physical memory pages in a deduplication table. When it finds pages with the same signature, the hypervisor compares the pages to determine whether they are identical and can be deduplicated. Operating system collaboration Active Memory Deduplication works independently of the operating system. However, newer versions of the supported operating systems can collaborate with PowerVM by indicating the pages that are likely candidates for being deduplicated. Likely candidates are frequently text pages, which contain code instructions. The indication is a refinement of the memory classification that is performed by “Active Memory sharing” on page 7. Memory oversubscription Active Memory deduplication helps avoid physical memory overcommitment, which minimizes the amount of operating system and Active Memory sharing paging that occurs.

For more information about Active Memory deduplication, see the Power Systems Memory Deduplication (http://www.redbooks.ibm.com/abstracts/redp4827.html) IBM Redbooks® publication. Virtual I/O Server The Virtual I/O Server shares physical resources between supported Linux partitions. The Virtual I/O Server also provides features such as Active Memory sharing, Suspend/Resume, and live partition mobility.

Use the Virtual I/O Server to achieve more efficient utilization and flexibility of physical storage and network devices.

Important Virtual I/O Server concepts include:

8 Linux: Getting started with virtualization for PowerLinux Virtual storage The Virtual I/O Server allows virtualization of physical storage resources. Virtual storage devices are accessed by client partitions through virtual SCSI. Virtual networking The Virtual I/O Server allows shared access to external networks through the Shared Ethernet Adapter (SEA).

Additional Virtual I/O Server concepts apply to POWER6 and later processor technology: Virtual storage With N_Port ID Virtualization (NPIV), you can configure the managed system so that multiple logical partitions can access independent physical storage through the same physical Fibre Channel adapter. Virtual networking The Virtual I/O Server allows shared access to external networks through Internet Protocol version 6 (IPv6), Link Aggregation (or EtherChannel), Shared Ethernet Adapter failover, and VLAN. Shared-memory Shared-memory is physical memory that is assigned to a shared-memory pool and shared among multiple logical partitions. Paging VIOS partition A Virtual I/O Server logical partition that is assigned to the shared-memory pool provides access to the paging space devices for the logical partitions that are assigned to the shared-memory pool.

For more information about the Virtual I/O Server, see the topic corresponding to your system in the Systems Hardware Information Center. POWER5 systems Virtual I/O Server overview (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ iphb2_p5/iphb1_vios_virtualioserveroverview.htm) POWER6 systems Virtual I/O Server (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/iphb1/ iphb1kickoff.htm) POWER7 Systems Virtual I/O Server (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/p7hb1/ iphb1kickoff.htm) PowerLinux systems Virtual I/O Server (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/p7hb1l/ iphb1kickoff.htm) Live partition mobility With PowerVM live partition mobility, you can move a running logical partition from one system to another. Live partition mobility includes active partition mobility and inactive partition mobility.

With active partition mobility, you can move Linux logical partitions that are running, including the operating system and applications, from one system to another. The logical partition and the applications that are running on it do not have to be shut down.

With inactive partition mobility, you can move a powered off Linux logical partition from one system to another.

Getting started with virtualization using IBM PowerVM 9 For more information about live partition mobility for specific Power Systems servers, see Live partition mobility for Power Systems (http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/topic/liacd/ liacd-live-partition-mobility.htm). System virtualization management Depending upon your system, you can manage system virtualization with the Hardware Management Console (HMC), the Integrated Virtualization Manager (IVM), or the IBM Flex System Manager™ (FSM). Hardware Management Console The Hardware Management Console (HMC) is a system management appliance for Power Systems servers.

The Hardware Management Console provides a graphical user interface and a command-line interface for system virtualization management. You can use the Hardware Management Console to create and manage logical partitions, configure virtual resources for logical partitions, and manage the shared memory pool.

For more information about managing Power Systems server virtualization with the Hardware Management Console, see the topic corresponding to your system in the Systems Hardware Information Center. POWER5 systems v Partitioning with version 7 or later of the HMC (http://pic.dhe.ibm.com/infocenter/powersys/ v3r1m5/topic/iphat_p5/iphatlparwithhmcp6.htm) v Partitioning with version 6 or earlier of the HMC (http://pic.dhe.ibm.com/infocenter/ powersys/v3r1m5/topic/iphat_p5/iphatlparwithhmc.htm) POWER6 systems Partitioning with the HMC (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/iphat/ iphbllparwithhmcp6.htm) POWER7 Systems Partitioning with the HMC (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/p7hat/ iphbllparwithhmcp6.htm) PowerLinux systems Partitioning with the HMC (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/p7hatl/ iphbllparwithhmcp6.htm) Integrated Virtualization Manager The Integrated Virtualization Manager (IVM) is a system management application that is provided by the Virtual I/O Server for Power Systems servers that are without a Hardware Management Console (HMC).

The Integrated Virtualization Manager provides a graphical user interface and a command-line interface for system virtualization management. You can use the Integrated Virtualization Manager to create and manage logical partitions, configure virtual resources for logical partitions, and manage the shared memory pool.

For more information about managing Power Systems server virtualization with the Integrated Virtualization Manager, see the topic corresponding to your system in the Systems Hardware Information Center. POWER5 systems Partitioning with the Integrated Virtualization Manager (http://pic.dhe.ibm.com/infocenter/ powersys/v3r1m5/topic/iphch_p5/iphchkickoff.htm)

10 Linux: Getting started with virtualization for PowerLinux POWER6 systems Integrated Virtualization Manager (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ iphch/iphchkickoff.htm) POWER7 Systems Integrated Virtualization Manager (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ p7hch/iphchkickoff.htm) PowerLinux systems Integrated Virtualization Manager (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ p7hchl/iphchkickoff.htm) IBM Flex System Manager The IBM Flex System Manager is a system management appliance for IBM Flex System™. It provides system virtualization management through IBM VMControl.

VMControl is the single point of control for managing virtualized resources in one or more IBM Flex System Enterprise Chassis. With VMControl, you can deploy virtual appliances to create virtual servers that are configured with the operating system and software applications that you want. You can also group resources into system pools to centrally manage and control the different workloads in your environment.

For more information about managing IBM Flex System virtualization with VMControl, see Managing virtualized resources (http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/ com.ibm.acc.8731.doc/managing_virtualized_resources.html) in the IBM Flex System Information Center.

Differences between Power Systems and x86 environments Learn about the differences in configuration and terminology between Power Systems environments and x86 environments. Configuration differences

In x86 environments, it is common to set up and configure hardware RAID to protect the system from disk failures. Typically, configuring hardware RAID is one of the first steps in setting up x86 servers.

In Power Systems environments, it is common to protect the system against disk failures by mirroring the disks. You mirror the disks by running a command in the Integrated Virtualization Manager (IVM) after IVM is installed. If you want to set up RAID instead, you can use the IBM Installation Toolkit for PowerLinux or the IBM Standalone Diagnostics CD. However, setting up RAID might require that you reinstall IVM if IVM is already installed. Terminology differences

IVM uses Power Systems terminology, which is sometimes different from x86 terminology. The following table lists terms that are used in IVM environments, maps them to similar x86 terms, and provides a definition for the terms.

IVM term or concept x86 term or concept Definition managed system server or system A physical server that contains physical processors, memory, and I/O resources that is often virtualized into virtual servers, which are also known as client logical partitions. In this case, the managed system is the PowerLinux server.

Getting started with virtualization using IBM PowerVM 11 IVM term or concept x86 term or concept Definition management partition Virtual machine, virtual server, The logical partition that controls all management operating system, of the physical I/O resources on the VMWare Service Console, or KVM server and provides the user interface Host partition from which to manage all of the client logical partitions within the server. In this case, the logical partition in which IVM is installed. client logical partition or logical Virtual machine or virtual server The collection of processor, memory, partition and I/O resources that are defined to run Linux and its workload. POWER® firmware plus the Virtual x86 hypervisor The underlying software of IVM that I/O Server. The PowerVM hypervisor facilitates the sharing of physical I/O presents the virtual environment, but resources between client logical the Virtual I/O Server can optionally partitions within the server. In IVM provide virtual I/O to a client logical environments, the terms Virtual I/O partition. The Virtual I/O Server role Server and Integrated Virtualization is optional because the PowerVM Manager are sometimes used hypervisor can provide multiple interchangeably. partitions by presenting a partition and assigning physical I/O adapters.

Related information: SAS RAID controllers for Linux

Installation tools for PowerLinux servers with logical partitions Learn about the tools you can use to install and configure your PowerLinux system. Installation tools include the Integrated Virtualization Manager (IVM), the IBM Installation Toolkit for PowerLinux, and the IBM Installation Toolkit Simplified Setup Tool. IVM

IVM provides a web-based system management interface and a command-line interface that you can use to manage the PowerLinux system. With IVM, you can create logical partitions, manage virtual storage and virtual Ethernet, and view service information related to the server. IBM Installation Toolkit for PowerLinux

The IBM Installation Toolkit provides a set of tools that simplifies the installation of Linux. The IBM Installation Toolkit gives you access to the IBM value-added software necessary to fully use the capabilities of the Power platform. The IBM Installation Toolkit can also be used as a bootable rescue DVD to run diagnostic tools and repair previously installed operating systems. You can use the IBM Installation Toolkit for the following: v Install and configure Linux on a non-virtualized POWER server v Install and configure Linux on servers with previously configured logical partitions (virtualized servers) v Install IBM RAS Tools for Linux v Install IBM RAS Tools on a previously installed Linux system v Upgrade system firmware level on POWER servers v Perform diagnostics or maintenance operations on previously installed systems v Browse and search Linux documentation included on the IBM Installation Toolkit ISO image

12 Linux: Getting started with virtualization for PowerLinux v Migrate a LAMP server (software stack and application data) from a System x® server to a System p® server IBM Installation Toolkit Simplified Setup Tool

The Simplified Setup Tool guides you through the process of quickly and easily configuring one or more open source workloads on your PowerLinux system. The Simplified Setup Tool is included in the IBM Installation Toolkit. Related information: Integrated Virtualization Manager Installing Linux with the IBM Installation Toolkit

Configuring the management partition and client logical partitions You can mirror the management partition, configure virtual resources on the management partition, and create the client logical partitions.

This procedure provides a simple configuration that deploys many defaults. If you want to configure a more complex or advanced configuration, see the technical documentation for IVM located in the IBM Systems Hardware Information Center at the following website: http://pic.dhe.ibm.com/infocenter/ powersys/v3r1m5/topic/p7hch/iphchsettinguplpar.htm.

Before you start, ensure that you are the prime administrator (padmin). Step 1: Connecting to the web-based interface To connect to the web-based interface for the Integrated Virtualization Manager (IVM), you must verify the network connection and configure the TCP/IP connection.

To connect to the web-based interface, complete the following steps: 1. From the serial console, log in to the management partition with the padmin user ID. 2. When prompted, change the login password to a secure password that adheres to your local password-security guidelines. 3. Accept the license agreement with the license command. 4. Ensure that there is a network connection configured between the management partition and at least one of the physical Ethernet adapters on the managed system. With this connection, you can access the IVM interface from a computer that is connected to the physical Ethernet adapter. You cannot use the HMC1 and HMC2 ports to connect to the management partition. 5. Configure the TCP/IP connection for the management partition with the mktcpip command. For example: mktcpip -hostname fred -inetaddr 9.5.4.40 -interface en0 -start -netmask 255.255.255.128 \ -gateway 9.5.4.1 -nsrvaddr 9.10.244.200 -nsrvdomain austin.century.com 6. Open a web browser window and connect with the HTTP or HTTPS protocol to the IP address that you assigned to IVM in Step 5. For example, enter https://9.5.4.40 in your web browser. The Welcome window is shown. 7. Enter the default user ID of padmin, and enter the password that you defined in Step 2. The IVM interface is shown. 8. Verify that IVM has the latest fix packs and updates: a. In the navigation area, select Updates under Service Management. The Updates page is shown. b. View the current code level of IVM. c. Go to the website provided on the page to find the latest available updates and directions for how to apply the updates.

Getting started with virtualization using IBM PowerVM 13 Related information: license command mktcpip command Step 2: Mirroring the management partition To prevent potential downtime and data loss, add a second disk to the rootvg storage pool and mirror the two disks.

When you install Integrated Virtualization Manager (IVM), it automatically creates a storage pool called rootvg and assigns one physical volume to rootvg. IVM and any data that IVM uses initially is stored on the management partition (partition ID 1) on that physical volume. If that disk fails, you cannot manage your client partitions and suffer downtime and the loss of data. To prevent this kind of interruption to your business, you need to add a second disk to the rootvg storage pool and mirror the two disks.

To mirror the management partition, complete the following steps: 1. Add a new physical volume to the rootvg storage pool: a. In the navigation area, select View/Modify Virtual Storage under Virtual Storage Management. The View/Modify Virtual Storage page is displayed. b. Select the Storage Pools tab. c. From the Tasks menu, click Create Storage Pool. The Create Storage Pool page is displayed. d. Enter a unique name for the new storage pool. e. Select Logical volume based as the storage pool type. f. Select a physical volume for the storage pool and click OK. 2. Mirror the new volume: a. In the navigation area, select View/Modify Partitions under Partition Management. The View/Modify Partitions page is displayed. b. Select the management partition. c. From the Tasks menu, select Open terminal window. A virtual terminal window is shown.

Note: Because the applet has a digital signature, your browser might display a security warning and ask you to verify that you want to run the applet. d. Enter the password for your login ID from the current IVM session. A terminal session starts for the management partition. e. At the command prompt, run the extendvg command as follows: extendvg rootvg Physicalvolume

where Physicalvolume is the name of the volume that you just added to rootvg. f. At the command prompt, run the mirriorios command as follows: mirrorios Physicalvolume

where Physicalvolume is the name of the volume that you just added to rootvg.

Restriction: The mirrorios command mirrors only the rootvg storage pool. It does not mirror other volume groups or any virtual disks that are created on rootvg after it is initially mirrored. g. Verify that the mirrored physical volume is included in the bootlist by running the following command: bootlist -mode normal -ls 3. If the mirrored volume is not included in the bootlist, add it using the following command: bootlist -mode normal hdisk0 hdisk1

14 Linux: Getting started with virtualization for PowerLinux where hdisk0 and hdisk1 are the mirrored physical volumes. Step 3: Configuring storage on the managed system You can configure storage on the managed system to meet the storage needs of the logical partitions that you create.

For a simple setup, consider configuring storage for one of the following scenarios: Environments with local storage You can create a storage pool in addition to the default rootvg storage pool for regular data storage, and then assign the new storage pool as the default. When you create logical partitions, you can create virtual disks from the storage capacity of the storage pool, and assign the virtual disks to the logical partitions. Virtual disks allow you to specify more precisely the amount of storage that you assign to logical partitions. You can assign storage to logical partitions without regard to the actual capacities of the physical volumes that make up the storage pool. Table 1. Some benefits and drawbacks to using local storage Benefits Drawbacks

v Using local storage can reduce the amount of disks v Using local storage can cause some resource that are assigned to IVM because multiple client contention if the client logical partitions perform rapid logical partitions can access the same physical disk. I/O operations on the same physical disk. v You can create additional logical volumes as needed v Environments with local storage do not support Live and assign them quickly. Partition Mobility.

Environments with a storage area network (SAN) You can assign physical volumes directly to the logical partitions. A physical volume is an individual logical unit that is identified by a logical unit number (LUN). A physical volume can be a hard disk or a logical device on a SAN. Configure storage with a SAN if you plan to use Live Partition Mobility. Table 2. Some benefits and drawbacks to using SAN storage Benefits Drawbacks

v Using a SAN provides the client logical partition with v Managing a large quantity of disks on IVM and the direct access to a SAN physical volume. client logical partitions to which they are mapped can v Environments with a SAN support Live Partition become complex. Mobility. v If you need to boot IVM to the System Management Services (SMS) menu, IVM can take a long time to probe all of the disks. IVM might also identify several disks as root volume groups (look for the IVM name).

Generally, the physical volumes and virtual disks that you assign to a logical partition display as physical disk devices in the operating system interface of the logical partition. Related information: Live Partition Mobility Configuring storage for environments with local storage To create a storage pool for regular data storage, complete the following steps: 1. In the navigation area, select View/Modify Virtual Storage. 2. Select the Storage Pools tab. 3. From the Tasks menu, click Create Storage Pool. The Create Storage Pool page is displayed. 4. Enter a unique name for the new storage pool. 5. Select Logical volume based as the storage pool type.

Getting started with virtualization using IBM PowerVM 15 6. Select Assign as default storage pool. 7. Select one or more physical volumes for the storage pool and click OK. Configuring storage environments with a SAN 1. Obtain the world wide port name (WWPN) for each fibre channel adapter: a. In the navigation area, select View/Modify Partitions under Partition Management. The View/Modify Partitions page is displayed. b. Select the management partition. c. From the Tasks menu, select Open terminal window. A virtual terminal window is shown.

The output shows all of the adapters of the fcs type. f. Run the following command for each adapter: fcstat adaptername

where adaptername is the name of the adapter as identified in Step 1e. For example, fcstat fcs1. The output shows information about the adapter, including its world wide port name (WWPN). g. Record the WWPN of each adapter. 2. From the SAN tools, zone and assign storage to the WWPNs that you recorded in Step 1g. 3. From the command prompt of the IVM virtual terminal, run the following command for each adapter so that IVM recognizes the new LUNs that you assigned to the adapters: cfgdev -dev adaptername

where adaptername is the name of an adapter to which you assigned storage from the SAN. For example, cfgdev -dev fcs1. Step 4: Configuring virtual Ethernet on the managed system You can configure virtual Ethernet on the managed system to meet the networking needs of the logical partitions that you create.

For a simple setup, consider configuring one of the following types of virtual Ethernet: Host Ethernet Adapter (HEA) or Integrated Virtual Ethernet (IVE) An HEA is a unique Ethernet adapter that is built into the system. It provides the ability to partition a physical Ethernet port. An HEA can contain one or more physical ports and each physical port can be assigned to zero or more logical partitions. Table 3. Some benefits and drawbacks to using HEA or IVE Benefits Drawbacks v The initial setup of an HEA is easier than the initial v HEA does not support Live Partition Mobility. setup of an SEA. v HEA supports a limited number of client logical v HEA provides high performance. partitions. HEA supports up to 32 logical ports. IVM uses at least one logical port, so HEA supports up to 31 client logical partitions.

16 Linux: Getting started with virtualization for PowerLinux Configuring an HEA does not require configuration of the IVM management partition. You configure the HEA when you create the client logical partitions. Shared Ethernet Adapter (SEA) An SEA is a virtual Ethernet bridge that connects the virtual Ethernet networks on your managed system to physical Local Area Networks (LANs). For greater security, do not set up the physical Ethernet adapter that you use to connect to the management partition as a virtual Ethernet bridge. With this configuration, you can isolate the management partition from all external networks. (The management partition manages the virtual Ethernet networks on your managed system but does not participate in any virtual Ethernet networks.) Table 4. Some benefits and drawbacks to using an SEA Benefits Drawbacks

v An SEA supports an almost unlimited number of v The initial setup of an SEA is more complex than the client logical partitions. initial setup of an HEA. v An SEA provides fast communication between client v An SEA uses processor cycles in IVM for sending logical partitions. packets to the external LANs. v An SEA supports Live Partition Mobility.

Configuring an SEA requires some configuration of the management partition as described in the following procedure. Related information: Live Partition Mobility Configuring an HEA or IVE Configuring an HEA does not require configuration of the management partition. You configure the HEA when you create the client logical partitions. Proceed to “Step 5: Creating client logical partitions.” Configuring an SEA 1. Determine the type of physical Ethernet adapter that you plan to use as the SEA: v If standard Ethernet adapter, go to step 6. v If HEA, go to step 2. 2. In the navigation area, select View/Modify Host Ethernet Adapters. The View/Modify Host Ethernet Adapters page is shown. 3. Select the host Ethernet adapter that you want to use as the SEA. You must select an HEA that has only one connected partition, which is the management partition. 4. Click Properties. The Host Ethernet Adapter Physical Port Properties page is shown. 5. Select Allow virtual Ethernet bridging and click OK. 6. In the navigation area, select View/Modify Virtual Ethernet. The View/Modify Virtual Ethernet page is shown. 7. Select the Virtual Ethernet Bridge tab. 8. For Virtual Ethernet ID 1, select the physical Ethernet adapter you want to use as the SEA. 9. Click Apply. Step 5: Creating client logical partitions You can create client logical partitions on the managed system by using the Create Partitions wizard and then creating additional logical partitions based on existing logical partitions.

Before you create client logical partitions, complete the following preparation tasks: 1. Determine the minimum resource requirements for the Linux distribution that you plan to run in the client logical partition.

Getting started with virtualization using IBM PowerVM 17 2. Determine the minimum resource requirements for the workloads, or applications, that you plan to run in the client logical partition. To view the minimum resource requirements for the open source workloads, see ../liaay/resource_requirements.dita. 3. Determine the resource assignments for the client logical partition based on the following considerations: v The minimum resource requirements from Step 1 and Step 2. v The type and amount of data that the workloads, or applications, service.

To create client logical partitions, complete the following steps: 1. From the navigation area, select View/Modify Partitions under Partition Management. The View/Modify Partitions page is shown. 2. From the Tasks menu, select Create partition. The Create Partitions wizard is shown. 3. Complete the wizard Steps as follows. Take the defaults unless directed otherwise. a. In the Name Step, enter a unique name for the new logical partition. b. In the Memory Step, enter the amount of memory to assign to the logical partition based on what you determined in preparation step 3. c. In the Processors Step, enter the number of processors to assign to the logical partition based on what you determined in preparation step 3. d. In the Ethernet Step, your selection depends on your Ethernet configuration: v If you are using an HEA, make the following selections: 1) Select at least one HEA port. Each selection must show a state of Up for the Link State and show at least one or more Available Connections. 2) In the Virtual Ethernet Configuration table, select None for each Virtual Ethernet. v If you are using an SEA, make the following selections: 1) Clear all HEA ports. 2) In the Virtual Ethernet Configuration table, set an adapter to virtual Ethernet 1. e. In the Storage type Step, your selection depends on your storage environment: v If you are using local storage, select Create a virtual disk. v If you are using a SAN, select Assign existing virtual disks and physical volumes. f. In the Storage Step, your selections depend on your storage environment: v If you are using local storage, enter the size of the virtual disk based on what you determined in preparation step 3. v If you are using a SAN, select one or more physical volumes to assign to the logical partition. g. Click Finish. 4. From the navigation area, select View/Modify Partitions under Partition Management. The View/Modify Partitions page is shown and lists the new logical partition. 5. Determine whether you want to create additional logical partitions: v If yes, go to Step 6. v If no, you are finished with this procedure. Return to the Installation roadmap to finish configuring the system. 6. Determine whether the additional logical partitions have the same properties as the logical partition that you previously created (except for partition ID, partition name, and storage configuration): v If yes, go to Step 7. v If no, repeat this procedure and complete the Create Partitions wizard to create additional logical partitions. 7. Select the logical partition that you used the Create Partitions wizard to create. 8. From the Tasks menu, click Create based on. The Create Based On page is shown. 9. Enter a unique name for the new logical partition.

18 Linux: Getting started with virtualization for PowerLinux 10. If you are using local storage, select Create Virtual Disks. If you are using a SAN, leave this option cleared. 11. Click OK. The View/Modify Partitions page is shown and lists the new logical partition. 12. Return to the Installation roadmap to finish configuring the system.

Configuring storage for the installation media You can configure a virtual media library. Then, you can add the IBM Installation Toolkit for PowerLinux installation media and the Linux distribution media to the virtual media library.

Before you start, complete the following tasks: v Locate the DVDs of the Linux distribution that you plan to install on the client logical partition. v Download the ISO image of the IBM Installation Toolkit for PowerLinux. You can download the ISO image of the IBM Installation Toolkit for PowerLinux from the IBM Installation Toolkit for PowerLinux web page. Do not create a DVD. v Transfer the ISO image of the IBM Installation Toolkit for PowerLinux to the /home/padmin/ directory in IVM in binary mode by using SCP or FTP.

Important: Rename the ISO image so that the file name is less than 12 characters in length. For example, rename the file to toolkit.iso. For example: scp IBM_Installation_Toolkit.iso [email protected]:toolkit.iso

This example shows a command that transfers the IBM_Installation_Toolkit.iso file from a remote workstation to the /home/padmin/ directory in an IVM system with the host name myivm.mycompany.com. This example also renames the IBM_Installation_Toolkit.iso file to toolkit.iso.

To configure storage for the installation media, complete the following steps: 1. Create a media library: a. In the navigation area of IVM, select View/Modify Virtual Storage under Virtual Storage Management. The View/Modify Virtual Storage page is shown. b. Select the Optical/Tape tab. c. In the Virtual Optical Media section, click Create Library. The Create Media Library page is shown. d. Select the rootvg storage pool. e. Enter the size of the virtual media library and click OK. The media library must be large enough to store the ISO image of the IBM Installation Toolkit and the Linux distribution media. If you are unsure of what size to enter, then enter 10 GB. 2. Add the ISO image of the IBM Installation Toolkit to the virtual media library: a. In the Virtual Optical Media section of the Optical/Tape tab, click Add Media. The Add Media page is shown. b. Select Add existing file. c. Enter the directory path and file name of the ISO image of the IBM Installation Toolkit. For example, enter /home/padmin/toolkit.iso d. Click OK. 3. Add the Linux distribution media to the virtual media library: a. Insert the DVD for the Linux distribution into the DVD drive of the server. b. In the Virtual Optical Media section of the Optical/Tape tab, click Add Media. The Add Media page is shown. c. Select Import from physical optical device.

Getting started with virtualization using IBM PowerVM 19 d. Enter the name of the media. e. Select the optical device that contains the DVD of the Linux distribution. f. Click OK to import the Linux installation media to the virtual media library. 4. Return to the installation roadmap to finish configuring the system.

Loading the IBM Installation Toolkit on a client logical partition You can mount the ISO image of the IBM Installation Toolkit for PowerLinux to the virtual optical device, activate the client logical partition, configure the client logical partition to boot from the virtual optical device, and access the user interface of the IBM Installation Toolkit.

To load the IBM Installation Toolkit on the client logical partition, complete the following steps: 1. Create a virtual optical device for the client logical partition and mount the ISO image of the IBM Installation Toolkit to the device: a. In the navigation area of IVM, select View/Modify Partitions under Partition Management. The View/Modify Partitions page is shown. b. Select the client logical partition on which you want to load the IBM Installation Toolkit. c. From the Tasks menu, select Properties. The Partition Properties page is shown. d. Click the Optical/Tape Devices tab. e. Expand the Virtual Optical Devices section. f. Determine whether a device exists that has no current media. v If yes, go to Step 1g. v If no, click Create Device. A new virtual optical device is created and shown in the table. Go to Step 1g. g. From the Current Media column of the virtual optical device, click Modify to mount the ISO image of the IBM Installation Toolkit to the new device. The Modify Current Media page is shown. h. Select the ISO image of the IBM Installation Toolkit and click OK. i. Click OK on the Optical/Tape Devices tab. 2. Open a virtual terminal session to the client logical partition: a. From the View/Modify Partitions page, select the client logical partition on which you plan to load the IBM Installation Toolkit. b. From the Tasks menu, select Open terminal window. A virtual terminal window is shown.

Note: Because the applet has a digital signature, your browser might show a security warning and ask you to verify that you want to run the applet. c. Enter the password for your login ID from the current IVM session. A terminal session starts for the logical partition and the SMS menu is shown in the terminal window. 3. Activate the client logical partition: a. From the navigation area, select View/Modify Partitions under Partition Management. b. Select the client logical partition that you want to activate and click Activate. The Activate Partitions page is shown. Verify the partition ID, partition name, and the current state of the client logical partition. c. Click OK to activate the partition. The View/Modify Partitions page is shown and the logical partition state has a value of running. d. In the terminal window, enter the number 1 immediately after IBM flashes across the screen. This action boots the client logical partition to the Systems Management Services (SMS) menu. 4. Obtain the MAC address of the host Ethernet adapter (HEA) or shared Ethernet adapter (SEA) to which the client logical partition is connected:

20 Linux: Getting started with virtualization for PowerLinux a. In SMS, select Select Boot Options, and press Enter. b. Select Select Install/Boot Device, and press Enter. c. Select List All Devices and press Enter. d. Select the device number that corresponds to the HEA or SEA to which the client logical partition is connected, and press Enter. e. Select Information and press Enter. f. Record the MAC address of the adapter. g. Press Esc twice to return to the list of devices. 5. Use the MAC address that you obtained in Step 4 on page 20 to set up DHCP for the client logical partition. Then, return to this procedure and continue with Step 6. During startup, the IBM Installation Toolkit obtains a dynamic IP address for the client logical partition through DHCP. 6. Configure the client logical partition to boot from the virtual optical device that you created in Step 1 on page 20: a. From the list of all devices in SMS, select the device number that corresponds to the virtual optical device that you created in Step 1 on page 20 and press Enter. b. Select Normal Mode Boot and press Enter. c. Exit the SMS menu. The client logical partition loads the IBM Installation Toolkit, and the Welcome to the IBM Installation Toolkit screen is shown in the terminal window. 7. Record the machine IP address located at the top of the screen. 8. Type 1 to select the Wizard mode (performs installation) option. 9. You might be prompted to accept a self-signed SSL certificate and identity. Accept both to continue. 10. Press Tab several times to go to the license question and accept the licenses to continue. The IBM Installation Toolkit Welcome Center is shown in the terminal window. 11. Access the graphical user interface of the IBM Installation Toolkit by typing the following address in a web browser: https://machineIP

where machineIP is the IP address that you recorded in Step 7. The Welcome Center page is shown in the browser. 12. Return to the Installation roadmap to finish configuring the system.

Optional additional software for PowerLinux servers managed by IVM Learn about the optional additional software for PowerLinux servers, such as IBM Systems Director VMControl™ and Live Partition Mobility.

In addition to Linux and the open source workloads, you can install the following optional management tools and virtualization capabilities: IBM Systems Director VMControl IBM Systems Director VMControl is designed to simplify the management of workloads in your IT environment. Use IBM Systems Director VMControl Express® Edition, IBM Systems Director VMControl Standard Edition, and IBM Systems Director VMControl Enterprise Edition to manage virtual servers, virtual appliances, workloads, and system pools across multiple hardware platforms and virtualization environments from one location. For more information, see IBM Systems Director VMControl in the IBM Systems Director information center. Live Partition Mobility With Live Partition Mobility, a component of the IBM PowerVM Enterprise Edition hardware

Getting started with virtualization using IBM PowerVM 21 feature, you can move Linux logical partitions from one system to another. The mobility process transfers the system environment including the processor state, memory, attached virtual devices, and connected users. For more information, see Live Partition Mobility in the IBM Systems Hardware information center. Extreme Cluster Administration Tool (xCAT) xCAT is a scalable cluster management and provisioning tool that provides hardware control, discovery, and operating system deployment. For more information, see Extreme Cluster Administration Tool (xCAT) (http://xcat.sourceforge.net/).

Related information for virtualization IBM Redbooks publications, websites, and other information center topic collections contain information that relates to the Getting started with virtualization using IBM PowerVM topic collection. IBM information centers Linux information center Installing Linux with the IBM Installation Toolkit for PowerLinux (http:// publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/topic/liaan/powerpack.htm) Systems Director information center IBM Systems Director VMControl (http://pic.dhe.ibm.com/infocenter/director/v6r2x/topic/ com.ibm.director.vim.helps.doc/fsd0_vim_main.html) Systems Hardware information center v Integrated Virtualization Manager (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/ topic/p7hch/iphchkickoff.htm) v Integrated Virtualization Manager commands (http://pic.dhe.ibm.com/infocenter/powersys/ v3r1m5/topic/p7hcg/iphcgkickoff.htm) v Live Partition Mobility (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/p7hc3/ iphc3ivmkickoff.htm) v SAS RAID controllers for Linux (http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ arebk/sascontroller_kickoff.htm) IBM Redbooks and Redpapers v IBM PowerVM Virtualization Introduction and Configuration, SG24-7940 v IBM PowerVM Virtualization Managing and Monitoring, SG24-7590 v Integrated Virtualization Manager on IBM System p5®, REDP-4061 Websites

Hands-On Technical Product Demos for Integrated Virtualization Manager (IVM) (http://www.ibm.com/ developerworks/wikis/display/wikiptype/movies#Movies-sectionivm)

PDF file for Getting started with virtualization using IBM PowerVM You can view and print a PDF of this information.

To view or download the PDF version of this document, select Getting started with virtualization using IBM PowerVM (about 191 KB).

22 Linux: Getting started with virtualization for PowerLinux Saving PDF files

To save a PDF on your workstation for viewing or printing: 1. Right-click the PDF link in your browser. 2. Click the option that saves the PDF locally. 3. Navigate to the directory in which you want to save the PDF. 4. Click Save. Downloading Adobe Reader

You need Adobe Reader installed on your system to view or print these PDFs. You can download a free copy from the Adobe Web site (http://get.adobe.com/reader/).

Getting started with virtualization using IBM PowerVM 23 24 Linux: Getting started with virtualization for PowerLinux Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation Dept. LRAS/Bldg. 903 11501 Burnet Road Austin, TX 78758-3400 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

Trademarks IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® and ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.

26 Linux: Getting started with virtualization for PowerLinux

Printed in USA