4405ch03 Virtualization.fm Draft Document for Review September 2, 2008 5:05 pm
88 IBM Power 570 Technical Overview and Introduction
The hypervisor must support the Partition Mobility functionality also called migration process.
POWER 6 processor-based hypervisors have this capability and firmware must be at
firmware level eFW3.2 or later. Source and destination systems could have different firmware
levels, but they must be compatible with each other.
The virtual I/O server on the source system provides the access to the clients resources and
must be identified as a Mover Service Partition (MSP). The VASI device , Virtual
Asynchronous Services Interface (VASI) allows the mover service partition to communicate
with the hypervisor; it is created and managed automatically by the HMC and will be
configured on both the source and destination Virtual I/O Servers designated as the mover
service partitions for the mobile partition to participate in active mobility. Other requirements
include a similar Time of Day on each server, systems shouldn’t be running on battery power,
shared storage (external hdisk with reserve_policy=no_reserve), and all logical partitions
should be on the same open network with RMC established to the HMC.
The HMC is used to configure, validate and to orchestrate. You will use the HMC to configure
the Virtual I/O Server as an MSP and to configure the VASI device. An HMC wizard validates
your configuration and identifies things which will cause the migration to fail. During the
migration, the HMC controls all phases of the process.
For more information about Live Partition Mobility and how to implement it, refer to IBM
System p Live Partition Mobility, SG24-7460.
3.3.5 PowerVM AIX 6 Workload Partitions
Workload partitions will provide a way for clients to run multiple applications inside the same
instance of an AIX operating system while providing security and administrative isolation
between applications. Workload partitions complement logical partitions and can be used in
conjunction with logical partitions and other virtualization mechanisms, if desired. Workload
partitions (WPAR) is a software-base virtualization capability of AIX V6 that can improve
administrative efficiency by reducing the number of AIX operating system instances that must
be maintained and can increase the overall utilization of systems by consolidating multiple
workloads on a single system and is designed to improve cost of ownership.
The use of workload partitions is optional, therefore programs will run as before if run in the
Global environment (AIX instance). This Global environment owns all the physical resources
(like adapters, memory, disks, processors) of the logical partition.
Workload partitions are separate regions of application space. and therefore they allow users
to create multiple software-based partitions on top of a single AIX instance. This approach
enables high levels of flexibility and capacity utilization for applications executing
heterogeneous workloads, and simplifies patching and other operating system maintenance
tasks.
There are two types of workload partitions:
System workload partitions - these are autonomous virtual system environments with their
own private root file systems, users and groups, login, network space and administrative
domain. It represents a partition within the operating system isolating runtime resources
such as memory, CPU, user information, or file system to specific application processes.
Each System workload partition has its own unique set of users, groups and network
addresses. It is integrated with he Role Based Access control (RBAC). Inter-process
communication for a process in a workload partition is restricted to those processes in the
Note Workload partitions are only supported with AIX V6.
To Next Page
Loading...
Need help?
General