POWER7 information

Live Partition Mobility pseudodevice

The vioslpm0 pseudodevice is created by default when you install Virtual I/O Server (VIOS) Version 2.2.2.0. You can use the attributes of the partition mobility pseudodevice to control active partition mobility operations. The pseudodevice saves the attributes that affect partition mobility operations.

Specifying the attributes for a partition mobility operation by using the VIOS
You can specify the attributes for a partition mobility operation by using the Virtual I/O Server (VIOS). The attributes that are specified are saved in the vioslpm0 pseudodevice.
Specifying the attributes for a partition mobility operation by using the HMC
You can specify the attributes for a partition mobility operation by using the Hardware Management Console (HMC).
NPIV LUN or disk level validation
With the Virtual I/O Server (VIOS) version 2.2.4.0 or earlier, partition mobility validation for N_Port ID Virtualization (NPIV) devices are checked only up to the port level. This resulted in the possibility of client failures if the actual disk mapped to the client on the source system were not properly mapped on the destination system. With the VIOS version 2.2.4.0, you can validate up to the disk mapping. To perform disk level validation, both the source and destination VIOS must be at level 2.2.4.0 or later, and the Hardware Management Console (HMC) must be at least at Version 7.4.4.
VIOS configuration options for partition mobility performance optimization
Partition mobility operations require a significant amount of system resources to achieve maximum performance while maintaining client stability. Configure the source and destination mover server partitions to have a similar amount of processing capabilities, because the overall performance of the migration is limited by the mover server partition that is configured with fewer processing capabilities.

Parent topic: Partition mobility environment

Send feedback Rate this page

Last updated: Sat, March 17, 2018