Sorry for not clarifying but this occurred after I rebooted after creating and activating the public, internal zone (as per the instructions).
Basically, after following the directions to the end (activating public, internal part) the zones all activate fine. After rebooting, the zones will not autoboot and errors occur in the public, internal workspace claiming no containers were found. > Andy Ying wrote: > > I'm trying to set up trusted extensions using this > tutorial: > > > > > http://opensolaris.org/os/community/security/projects/ > tx/TX_opensolaris_2008_11/ > > > > It seems that after rebooting the machine, the tx > zones don't seem to autoboot because when my labeled > desktop complain about not finding the appropriate > container. The zone configuration file has the > autoboot property as true which makes me believe that > the zones are extremely slow when booting up. > > > > Is there a way to resolve this issue? Thanks. > > > > I am running OpenSolaris 2008.11 on a 64-bit VMWare > Server 1.0.8 guest. > > > When you first reboot your system after running: > > svcadm enable -s labeld > re are no zones, so you should expect to be informed > that that there > are no matching containers. > > Are you still getting this message after installing > your zones? Try > assuming the root role and bringing up a Zone Console > via txzonemgr. Do > you see a login prompt? Hit return, if not. Perhaps > the zone is waiting > for you to complete the initial sysidtool setup. > > --Glenn > > _______________________________________________ > security-discuss mailing list > security-discuss at opensolaris.org -- This message posted from opensolaris.org
