I assume you did not have any zones at all until after the reboot that comes after svcadm enable -s labeld, and each zone has a label?
And each zone already had a console at first zone boot, so that you could perform hit f2 once to accept the nfsv4 configuration, then the zone reboots right away? And the Activate Workspace directions at the end worked OK? >Date: Wed, 03 Dec 2008 16:25:06 -0800 (PST) >From: Andy Ying <yying2 at uiuc.edu> >Subject: OpenSolaris 2008.11 Trusted Extension Zones >To: security-discuss at opensolaris.org >Delivered-to: security-discuss at opensolaris.org >X-Original-To: security-discuss at opensolaris.org >X-Antispam: No, score=0.0/5.0, scanned in 0.059sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ >List-Unsubscribe: <http://mail.opensolaris.org/mailman/listinfo/security-discuss>, <mailto:security-discuss-request at opensolaris.org?subject=unsubscribe> >List-Id: OpenSolaris Security Discussions <security-discuss.opensolaris.org> > >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. >-- >This message posted from opensolaris.org >_______________________________________________ >security-discuss mailing list >security-discuss at opensolaris.org @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Jan Parcel, Sustaining, Trusted OE Internal Trusted Support Pages: http://trusted.sfbay
