Troubleshooting active partition mobility

Learn how to troubleshoot active partition mobility.

About this task

The following is a list of possible errors and ways to recover:

Table 1. Known problems and resolutions for active partition mobility
Problem	Solution
If the operating system running in the mobile partition does not explicitly support the processor version register of the destination server, and the processor determines that explicit support is required, then the processor will not allow the migration to proceed.	Either: Move the partition to another system. Update the operating system to a level that supports the target system processor version registers.
You receive an error concerning the operating system while attempting to migrate a partition.	Look in the operating system error logs for OS-related failures. Look in the HMC log for application-related failures.
You receive an HMC error concerning insufficient memory on the destination server. Note: Sufficient memory includes the amount of available memory on the server and the amount of available contiguous memory on the server. If the mobile partition requires more contiguous memory, making more memory available will not solve the problem.	Either: Move the partition to a different server. Make more memory available on the destination server. See Determining available memory on the destination serverfor instructions.
The HMC and managed systems lost their connection while the migration was in progress.	In the HMC navigation area, select Partition Migration. In the contents area, select either the source or destination system and select Recovery. From the Migration Recovery panel, click Recover.
While attempting to change resources dynamically, you receive an error that the Resource Monitoring and Control (RMC) daemon is not connected.	This error typically occurs when there is a network connection problem between the logical partitions and the HMC. To resolve this error, check your system network setup.