In IBM Power Systems, the hypervisor firmware—often called the Power Hypervisor (PHYP)—is the core control layer built directly into system firmware. It’s not a separate OS or software install; it runs below everything and manages how hardware is shared securely and efficiently across partitions.

🧠 What Hypervisor Firmware Does

The Power Hypervisor works with PowerVM to enable virtualization at the hardware level.

🔧 Key Roles of Hypervisor Firmware

1. Logical Partitioning (LPAR Creation & Isolation)

• Splits a physical server into multiple independent LPARs
• Each LPAR gets:
  • Virtual CPUs
  • Memory
  • I/O resources

👉 Ensures strict isolation:

• One partition cannot access another’s memory or CPU state

2. CPU Virtualization & Scheduling

• Manages physical CPU cores across partitions
• Supports:
  • Dedicated processors
  • Micro-partitioning (shared CPUs)

👉 Internally:

• Uses time-slicing and dispatch queues
• Allocates CPU cycles based on entitlement and priority

3. Memory Virtualization

• Allocates and protects memory per LPAR
• Maintains:
  • Page tables
  • Address translation

Supports advanced features:

• Active Memory Sharing (AMS)
• Memory overcommit

👉 Prevents cross-partition memory access

4. I/O Virtualization Coordination

• Works with VIOS (Virtual I/O Server) to provide:
  • Virtual disks
  • Virtual network adapters

Hypervisor role:

• Routes I/O requests from LPAR → VIOS → physical device
• Maintains secure mapping tables

5. Interrupt Handling

• Manages hardware interrupts across partitions
• Ensures:
  • Interrupts go only to the correct LPAR
  • No interference between workloads

6. Security & Isolation Enforcement

• Enforces hardware-level isolation
• Uses:
  • Privilege levels
  • Protected memory regions

👉 Even if an OS crashes or is compromised:

• Other partitions remain unaffected

7. Live Partition Mobility (LPM) Control

• Orchestrates migration between servers
• Handles:
  • Memory state transfer
  • CPU context transfer
  • Synchronization

👉 Ensures seamless migration without downtime

8. Dynamic Resource Management (DLPAR)

• Allows adding/removing:
  • CPU
  • Memory
  • I/O

👉 Done while the system is running, without reboot

9. Hardware Abstraction Layer

• Presents a virtualized hardware interface to each LPAR
• Each partition believes it owns:
  • CPUs
  • RAM
  • Devices

⚙️ How It Sits in the Stack

Applications
   ↓
Operating Systems (AIX, Linux, IBM i)
   ↓
PowerVM (management layer)
   ↓
👉 Power Hypervisor (Firmware)
   ↓
Physical Hardware (CPU, Memory, I/O)

🚀 Why Firmware-Based Hypervisor Matters

🔹 1. Near-Native Performance

• Runs directly on hardware (no host OS overhead)

🔹 2. High Reliability

• Part of system firmware → extremely stable
• Used in mission-critical environments

🔹 3. Strong Security

• Hardware-enforced isolation (not just software-based)

🔹 4. Scalability

• Supports hundreds of LPARs on a single system

⚠️ Key Difference from x86 Hypervisors

🧩 Simple Analogy

Think of the hypervisor firmware like a traffic controller built into the hardware itself:

• It decides who gets CPU time
• It ensures no collisions (isolation)
• It keeps everything moving smoothly—even during changes like migrations