LDOM vrs Container Post: 302172369

Sponsored Content

Operating Systems Solaris LDOM vrs Container Post 302172369 by System Shock on Monday 3rd of March 2008 02:21:20 PM

03-03-2008

Registered User

It is not "per processor" virtualization, as you can split a processor/core/threads into different domains, and still you create the LDOMs through software..

It'd take too much typing to properly explain the difference...

...in a nutshell,

LDOMs allow you to assign your hardware to different virtual hosts for exclusive use. Say you have a T5220 with an 8-core CPU. You could create 8 LDOMs and assign a core to each. Each core will be for the exclusive use of the domain you assigned it to, regardless of the load on the other domains. With zones/containers, all zones can use any CPU core/thread that they need when they need it. Limits can be set as far as how much CPU they use, but you cannot specify which CPU/core/thread they are to use.

With LDOMs you get an OBP per domain that can be configured independently from the others. Zones don't have OBPs.

You can "brand" a zone as a Solaris 8 or Solaris 9 zone (and I understand RHEL as well), running an instance of either OS on top of Solaris 10. This is useful in those cases when you are refreshing hardware but app vendors only support their apps on the older OSs. You can't "brand" an LDOM, but you can create a branded zone inside an LDOM.

Root on the global zone can see all of the file systems on each zone.
Root on the primary domain cannot see the files systens on the domains.

I hope this gives you a better idea.

System Shock

View Public Profile for System Shock

Find all posts by System Shock

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Swap vrs Paging

Can anyone explain the difference between Paging and Swap in unix. I know over the years that the term has almost become interchangable. However I have noticed in VMSTAT for a Solaris system that I am investigating that there is significant Paging but no Swapping and hence I am wondering do I...

2. Solaris

Solaris 8 Container Error

Log File: /var/tmp/server1.install.18730.log Source: /vmpool/tmp/server1.flar Installing: This may take several minutes... Postprocessing: This may take several minutes... Postprocess: ERROR: p2v module S40_setup_preload failed: 0 Postprocess: ERROR: Postprocessing failed. ...

3. Solaris

Solaris 6 container support

Is solaris 6 container support available ? Say, If I have a machine with Solaris 10 operating system.. Can i install Solaris 6 container on this machine, so that the machine will have Solaris 6 virtual environment... Does sun support Solaris 6 container ? Any ideas over this ?

4. Solaris

solaris zones vs container..

kindly share what are difference b/w solaris zones and containers....

5. UNIX for Advanced & Expert Users

mdadm container! How does it work

Hi everyone, I am not sure if I understand how mdadm --create /dev/md0 --level=container works? A device called /dev/md0 appears in /proc/mdstat but I am not sure how to use that device? I have 2 blank drives with 1 500GB partition on each. I would like to setup mirroring, but not in the...

6. Solaris

Container

Hi, Can any one let me know in detail what is container and how it is different from zones. and also any process to create a container

7. Ubuntu

Ping a container LXC

Hello, Please, I try to do ping 10.0.3.8 (ip of LXC container) from VMB but it didn't work ! Have you an idea please ? Here is an explanation of what I want do: (red arrow) http://imgur.com/2IzJvXO imgur: the simple image sharer Thanks a lot. Best Regards.

LEARN ABOUT DEBIAN

systemd-machine-id-setup

SYSTEMD-MACHINE-ID(1)					     systemd-machine-id-setup					     SYSTEMD-MACHINE-ID(1)

NAME

       systemd-machine-id-setup - Initialize the machine ID in /etc/machine-id

SYNOPSIS

       systemd-machine-id-setup

DESCRIPTION

       systemd-machine-id-setup may be used by system installer tools to initialize the machine ID stored in /etc/machine-id at install time with
       a randomly generated ID. See machine-id(5) for more information about this file.

       This tool will execute no operation if /etc/machine-id is already initialized.

       If a valid D-Bus machine ID is already configured for the system the D-Bus machine ID is copied and used to initialize the machine ID in
       /etc/machine-id.

       If run inside a KVM virtual machine and a UUID is passed via the -uuid option this UUID is used to initialize the machine ID instead of a
       randomly generated one. The caller must ensure that the UUID passed is sufficiently unique and is different for every booted instanced of
       the VM.

       Similar, if run inside a Linux container environment and a UUID is set for the container this is used to initialize the machine ID. For
       details see the documentation of the Container Interface[1].

OPTIONS

       This tool does not take any options or arguments.

EXIT STATUS

       On success 0 is returned, a non-zero failure code otherwise.

SEE ALSO

       systemd(1), machine-id(5), dbus-uuidgen(1)

AUTHOR

       Lennart Poettering <lennart@poettering.net>
	   Developer

NOTES

	1. Container Interface
	   http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface

systemd 							    10/07/2013						     SYSTEMD-MACHINE-ID(1)