Arun Gupta writes:
> Can you explain what is "exclusive stack instance" mean in this context ?

See the "ip-type" parameter in zonecfg(1M).

Zones can be created using one of two different networking models.  In
the default "shared" model, the zones are just given IP addresses on
links that are controlled by the global zone.  The non-global zone has
no control over its interfaces, and there's one instance of the IP
stack shared between the non-global zone and the global zone.  The
interfaces are configured by zoneadmd using parameters provided by

In the "exclusive" model, the global zone gives the non-global zone
access to individual links, which can be VLANs or separate NICs.  The
non-global zone then independently plumbs its own IP stack on top of
those links.  The global zone has no control over the addresses that
the non-global zone uses, and the non-global zone sets these.

With an "exclusive" stack instance, the non-global zone is able to
control most of the IP configuration aspects of the interface,
including using DHCP to configure the address.  (It's unable to supply
its own kernel modules, though, because there's still only one kernel
image on the system.)

> Will creating zones in a Virtual Box image qualify as that ?


James Carlson, Solaris Networking              <>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
zones-discuss mailing list

Reply via email to