Summary: LDOM Questions

From: Adams Jonathan K NGA-EGMC USA CTR <>
Date: Fri Nov 13 2009 - 13:46:00 EST
Thanks to D. Magda & D. Ross-Smith:


Is it possible to fail-over LDOM between chassis?  I know this can be
accomplished with containers.

Sun Cluster 3.2 2/08 added support for LDoms as well:

You can do this in the latest versions.  What we've been hesitant to do
is implement it because of the perceived complexity compared to

> How does Windows fit into this: say we have a Blade container with a
> mix of AMD and SPARC systems.

You'll need to find a clustering solution for Windows, or have Windows
running as a VMware guest and use something like VMotion.

> Under what circumstances would one run Containers inside of a LDOM?

Each LDom on a physical host can run a different version of the Solaris
10 kernel (e.g., Update 6, Update 7, and Update 8). Within each OS
instance you can multiple zones, but each of those zones has to be at
the same kernel level, and generally the entire OS is at the same patch
level (i.e., all zones have the same patches).

So, if you have a bunch of software that needs version X of Solaris
patches, and a bunch that needs a different version of patching ("Y"),
you can theoretically do the following: set up one LDom at version X,
and create a zone for each application (to take advantage of resource
and security isolation). Then, set up an LDom with version Y and create
zones for those applications.

In this way you can have one physical machine that has multiple releases
of Solaris, and in each of those have multiple zones.

In reality though I think this would be fairly convoluted and hard to
keep track of. It would probably be logistically simpler if you some
machines / blades dedicated to only zones, and others only running
LDoms. You use more resources, but you can keep track where you know
some particular systems are for zones and others are for LDoms.
sunmanagers mailing list
Received on Fri Nov 13 13:47:28 2009

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:15 EST