IBM Power 595, Технический обзор и введение

Страница: 139 / 188

Chapter 3. Virtualization
127
– SUSE Linux Enterprise Services 10 (SLES 10) Service Pack 1 or later
Previous versions of AIX and Linux for Power can participate in Inactive Partition Mobility, if
the operating systems support virtual devices and IBM System p POWER6 processor-based
systems.
Source and destination system requirements
The source partition must be one that only has virtual devices. If any physical devices are in
its allocation, they must be removed before the validation or migration is initiated.
The Hypervisor must support the Partition Mobility functions, also called migration process.
POWER 6 processor-based hypervisors have this capability. If migrating to a POWER6
processor-based server (other than a 595 server), the server 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 firmware instructions note any incompatibilities.
The Virtual I/O Server on the source system provides the access to the clients resources and
must is identified as a Mover Service Partition (MSP). The Virtual Asynchronous Services
Interface (VASI) device allows the mover service partition to communicate with the hypervisor.
It is created and managed automatically by the HMC and is configured on both the source
and destination Virtual I/O Servers designated as the mover service partitions. Other
requirements include:
The time of day setting must be the same on each server.
Systems should not be running on battery power.
Shared access to external storage (external hdisk with reserve_policy=no_reserve) must
exist.
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 a live partition mobility operation.
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 any items that would cause
the migration to fail. The HMC controls all phases of the migration process.
For more information about Live Partition Mobility and how to implement it, refer to PowerVM
Live Partition Mobility on IBM System p , SG24-7460 which can be found at:
http://www.ibm.com/redbooks
3.10 AIX 6 workload partitions
Workload partitions is a software-based virtualization feature of AIX V6 that provides the
ability to run multiple applications within the same instance of an AIX operating system. Each
workload partition (WPAR) runs in separate application space which provides security and
administrative isolation between the applications. You can control processor and memory
allocations for each WPAR.
Multiple WPARs can be created within a single AIX 6 instance which is running on a
stand-alone server, logical partition, or shared processor pool partition. Workload partitions
(WPARs) 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.