The difference between LPAR (PR/SM-based virtualization) and z/VM virtualization on IBM Z comes down to where virtualization happens and how deep it goes. They are actually complementary layers, not competitors.

🔷 1. Big Picture

• LPARs → Hardware/firmware-level partitions
• z/VM → Software hypervisor running inside an LPAR

👉 Think of it as:

Hardware → PR/SM → LPAR → z/VM → Virtual Machines

🔷 2. LPAR (PR/SM Virtualization)

🔹 What it is

• Created by PR/SM (firmware hypervisor)
• Each LPAR behaves like a separate physical server

🔹 Characteristics

• Very low overhead
• Strong hardware isolation
• Limited number (tens of LPARs typically)

🔹 Resource Model

• CPU: Dedicated or shared
• Memory: Fixed or dynamically adjusted
• I/O: Direct hardware access via channel subsystem

👉 OS runs directly:

• z/OS
• Linux on Z
• z/VM

🔷 3. z/VM (Software Virtualization)

🔹 What it is

• A full operating system + hypervisor
• Runs inside an LPAR

🔹 What it does

• Creates hundreds to thousands of virtual machines
• Each VM runs its own OS (usually Linux)

🔹 Characteristics

• Slightly higher overhead than LPAR
• Extremely flexible and scalable

🔷 4. Key Architectural Differences

🔷 5. CPU & Memory Handling

🔹 LPAR

• Allocates real hardware resources
• Near-native performance

🔹 z/VM

• Overcommits resources:
  • CPU sharing across many VMs
  • Memory overcommit + paging

👉 Enables massive consolidation

🔷 6. I/O Virtualization

🔹 LPAR

• Direct I/O via channel subsystem
• Near-native speed

🔹 z/VM

• Uses:
  • Virtual devices
  • Minidisks
  • Virtual networking

👉 Slight overhead but highly flexible

🔷 7. Typical Deployment Pattern

Most real systems use both together:

IBM Z Hardware
   ↓
PR/SM → LPAR 1 (z/OS)
     → LPAR 2 (z/OS)
     → LPAR 3 (z/VM)
                 ↓
            1000+ Linux VMs

👉 This gives:

• Stability (LPARs)
• Scalability (z/VM)

🔷 8. Use Case Differences

🔹 LPAR is used for:

• Core banking systems
• DB2 / transaction processing
• High-security workloads

🔹 z/VM is used for:

• Linux server consolidation
• Private cloud environments
• Dev/test environments

🔷 9. Performance Perspective

• LPAR → Best performance, lowest latency
• z/VM → Slight overhead but massive density

👉 Trade-off:

• Performance vs scalability

🔷 🔥 Simple Analogy

Think of a building:

• LPAR = Separate apartments (solid walls, fully isolated)
• z/VM = Rooms inside one apartment (flexible, many occupants)

🔷 🚀 Bottom Line

✔ LPAR (PR/SM)

• Hardware-level virtualization
• Maximum performance and isolation

✔ z/VM

• Software-level virtualization
• Massive scalability and flexibility

✔ Together

• Form a layered virtualization model unique to IBM Z