It is not practical for each zone to have its own X server. The X server
runs in the global zone, and can be accessed from non-global zones. You
can also run Xnest in a non-global zone, but the actual
keyboard/mouse/display are still under the control of the global zone.
When Trusted Extensions is enabled, the global zone X server isolates
the clients connected from different zones so that they cannot interfere
or interact with each other. For example cut and paste between zones in
not allowed by default. OpenGL and 3D operations will work if they don't
require that the client has access to the hardware.
Trusted Extensions also supports Sun Ray software with zones. All the X
servers (per DTU) run in the global zone, but the window manager (CDE)
or panel manager (JDS) has been extended to understand zones and
associate workspaces with zones.
Amir Javanshir wrote:
> Hi all,
> One of our partners who develops a PLM software (using OpenGL and 3D
> accelerator cards), asked me a couple of tricky questions concerning
> Solaris zones.
> First of all, we agree that Solaris zones (by extension the
> containers) are really useful on the server side, for consolidation
> means. However does it really make sense to use zones on a graphical
> workstation ? What benefit would there be there ? (The only one I can
> see is to have two different versions of a software on the same
> Now the tricky questions:
> * In case of the sparse root zone many libraries are shared
> between all the zones. What about the X11 libraries, colormap,
> pixmap ans so on ?
> * And in Whole Root Zones, do we get a different X server for
> each zone ?
> * Finally, lets say each zone has it's own X server, how can
> dirrerent zones deal with the 3D graphic card on the workstation
> (the XVR 2500 card for example) ?
> Putting it in other words, zones allow application to run in
> protected environments, knowing nothing of other zones, each one
> acting as if they are alones on the hardware. Can we guaranty
> this behavior also for 3D graphical applications (two zones
> running seamlessly different 3D applications, sharing the 3D card)
> Any help would be appreciated
> zones-discuss mailing list
zones-discuss mailing list