Kelley Shaw wrote: >I tried this, and everything went haywire :( I couldn't even get windows to >come up in the global zone. > It should have worked. Make sure that the hostname specified in /etc/hostname.vni0 exists in /etc/hosts or /etc/inet/ipnodes, and that is specified as the loghost.
> I understand what you are saying in terms of the DISPLAY variable being > passed to the zones, but what I don't understand is how the virtual interface > (vni0) can be tied to the hostname of the system. > I do this all the time. Take a closer look at the laptop installation instructions. > My understanding of a virtual interface is that it is only reachable locally. > If vni0 is the configured interface for the IP associated with my hostname, > how will I communicate with other systems on the network? > You're right that the virtual interface can't be used externally. So the system will just select a real interface when it needs to communicate externally. > I'm guessing I configure a physical interface with a different name? My > networking skill are a bit lacking, so please excuse my ignorance! > > No problem. It's easy to get this messed up. Solaris doesn't have a simple way to select vni0 as your primary interface. >You mentioned that the DISPLAY variable being passed into the zones has no >route to my global zone. Is there a way to explicitly create routes so that >things work using my configuration? > > You shouldn't need to specify any routes to get the window system to work if you are using vni0. However, you may need to specify routes for the labeled zone interfaces since they are using different interfaces. Once you get the trusted desktop working, run netstat -r in a labeled zone to see if you are lacking a route. If so, you can set multiple default routes, one per interface, in the global zone. --Glenn
