What is LDOM (Logical Domain)?
While Exadata uses KVM for virtualization, the SPARC world has its own specialized partitioning technology: LDOM (Logical Domain), officially known as Oracle VM Server for SPARC.
LDOM is a firmware-based virtualization layer that allows you to carve a single physical SPARC server into multiple independent virtual machines. Unlike standard virtualization, it leverages the Hypervisor built directly into the server's firmware, providing a "bare-metal" feel with almost zero performance overhead.
In an LDOM environment, not all virtual machines are created equal. Each domain is assigned a specific "role":
Control Domain (The Manager): This is the primary domain (usually named primary) where you install the Logical Domains Manager. It’s the "boss" that allocates CPUs, memory, and I/O to all other domains.
Service Domain (The Provider): This domain provides virtual services (like virtual disks or network switches) to other domains.
I/O Domain (The Owner): This domain has direct "ownership" of a physical PCIe slot or network card. By giving a VM direct access to the hardware, you get the fastest possible performance.
Guest Domain (The Worker): This is where your actual applications and databases live. It doesn't "own" hardware; it consumes the virtual resources provided by the Service and I/O domains.
SPARC processors (like the T-series and M-series) are designed for massive multi-threading. LDOM allows you to assign resources at the individual CPU thread level. Because the SPARC hypervisor is so thin, the Guest OS thinks it is running on real hardware, allowing it to execute instructions at native speed.
One of the "superpowers" of LDOMs is the ability to add or remove CPUs and Memory while the Guest OS is still running. If your database needs more power for an end-of-month report, you can "hot-add" CPU threads from the Control Domain without a reboot.
Just like VMware, LDOMs support Live Migration. You can move an entire running database instance from one physical SPARC server to another across the network with zero downtime for the users.
Many people get confused between LDOMs and Solaris Zones. Here is the simple breakdown:
| Feature | Solaris Zones | LDOM (Oracle VM for SPARC) |
| Virtualization Type | OS-level (Container) | Hardware-level (Virtual Machine) |
| Kernel | Shares the host kernel | Each has its own independent kernel |
| Isolation | High | Extreme (Hardware-enforced) |
| Patching | Usually must match host | Patch each LDOM independently |
| OS Support | Only Solaris | Solaris (various versions) |
Hard Partitioning (Licensing): This is the #1 reason for many Oracle customers. Oracle recognizes LDOMs as a "Hard Partition," meaning if you have a 32-core server but only assign 8 cores to an LDOM, you only have to pay for 8 cores of Oracle Database licenses.
Consolidation: You can run a legacy Solaris 10 database in one LDOM and a modern Solaris 11 app in another, all on the same SPARC M8 server.
Security: Because each LDOM has its own kernel, a "Kernel Panic" or a security breach in one domain cannot affect any other domain on the same physical box.
LDOMs turn a single massive SPARC server into a flexible cloud-like environment. They provide the perfect balance between the flexibility of a virtual machine and the uncompromising speed of the SPARC processor.