Start with your current Linux Power model
Choose the generation, then the exact model and machine type. The model guide connects configuration questions to the installed-release branch and the separate workload migration plan.
| Current system | Main planning boundary |
|---|---|
| Power 11: find the exact model | Use a Power 11-enabled distribution and installation level for the exact server and I/O arrangement. RHEL, SLES and Ubuntu have separate release and certification rules. |
| Power 10: find the exact model | Power 10 meets the processor baseline for RHEL 10 and SLES 16. Exact model support, release level and virtualization requirements still apply; a generation-wide CPU baseline is not a complete certification. |
| Power 9: find the exact model | Power 9 meets the RHEL 9 processor baseline but not the Power 10 baseline for RHEL 10 or SLES 16. Canonical supports Power 9 in Ubuntu 22.04 LTS and later eligible releases. |
| Power 8: find the exact model | RHEL 9 requires Power 9 or later; RHEL 10 and SLES 16 require Power 10 or later. Canonical identifies Ubuntu 20.04 LTS as its last Power 8 release. Check eligible RHEL 8 or SLES 15 configurations in the model maps. |
| Power 7: find the exact model | Separate an older ppc64 installation from the ppc64le packages used on newer servers. Current vendor processor requirements can rule out the desired release on Power 7. |
| Power 6: find the exact model | Power 6 Linux planning starts with the installed distribution, kernel and architecture. Modern ppc64le media should not be treated as an in-place upgrade of an older big-endian installation. |
| Power 5: find the exact model | Treat a Power 5 Linux workload as a legacy release and architecture assessment. Identify the actual distribution and byte order before choosing modern installation media. |
Start with the Linux release you run
Use the full installed level rather than estimating it from the server age. Match it to the application’s supported target before choosing the hardware.
| Installed release or family | What the guide helps you decide |
|---|---|
| RHEL 10 | Which hardware and software prerequisites apply, and whether the change can stay on this server. |
| RHEL 9 | Which hardware and software prerequisites apply, and whether the change can stay on this server. |
| RHEL 8 | Which hardware and software prerequisites apply, and whether the change can stay on this server. |
| RHEL 7 | Which hardware and software prerequisites apply, and whether the change can stay on this server. |
| SLES 16 | Which hardware and software prerequisites apply, and whether the change can stay on this server. |
| SLES 15 | Which hardware and software prerequisites apply, and whether the change can stay on this server. |
| SLES 11 / 12 | Which hardware and software prerequisites apply, and whether the change can stay on this server. |
| Ubuntu LTS | Which hardware and software prerequisites apply, and whether the change can stay on this server. |
| ppc64, ppc64le and byte order | Which hardware and software prerequisites apply, and whether the change can stay on this server. |
Keep Linux upgrade work separate from the workload move
| Task | Useful next step |
|---|---|
| More processor, memory or I/O capacity | Measure the bottleneck and qualify resources for the installed system. |
| A Linux release or maintenance upgrade | Confirm supported software steps and the server that can run the target. |
| Moving to another system | Qualify the destination and plan transfer, rehearsal, cutover and rollback. |
Linux release upgrades and workload moves have different prerequisites. A distribution change or byte-order change may call for a new installation and a supported application/data transfer.
Discuss your current Linux system with Midland · Plan a Linux workload migration
Sources and release checks
Guidance checked October 21, 2026. Midland catalog identities stay with their exact model. Hardware eligibility, software maintenance and application certification need separate checks for the installed configuration.