Re: [zones-discuss] How good is zonecfg/zoneadm's wildcard parsing?
Thanks Jerry. I double-checked this again and I think it definitely is a bug. Zoram Jerry Jelinek wrote: Zoram Thanga wrote: Hi, On an S10u4_07/SPARC machine. So I want to export a disk slice to my zone. I did thus zonecfg:paris add device zonecfg:paris set match=/dev/*dsk/c1t1d0s6 zonecfg:paris end I was hoping that this would create /dev/rdsk/c1t1d0s6 and /dev/dsk/c1t1d0s6 in the zone 'paris'. So I login to the zone, and # zonename paris # ls /dev/ | grep dsk *dsk dsk rdsk # Notice that a *dsk directory was created (WTF? :) # cd *dsk # ls -l crw-r- 1 root sys 32, 6 Jun 7 05:13 c1t1d0s6 So my disk slice went under /dev/*dsk/ in the zone! Meanwhile, the /dev/dsk and /dev/rdsk directories are empty: # cd /dev/rdsk # ls -l total 0 # # cd /dev/dsk # ls -l # total 0 # Is this expected behavior or what? ( I also succeeded in exporting device match=/dev/rdsk/c1t1d0s* as /dev/rdsk/c1t1d0s* in the zone :) I just verified this works fine on nv b65. When I get a chance I'll double check S10u4. It sounds like it is a bug there. Jerry -- Zoram Thanga::Sun Cluster Development::http://blogs.sun.com/zoram ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] create command question
Original Message Subject: [zones-discuss] create command question From: F.V.(Phil)Porcella [EMAIL PROTECTED] To: zones-discuss@opensolaris.org Date: Mon Jun 11 2007 19:17:21 GMT+0200 (MEST) ***Hi, ***I was hoping to get an answer a question about create vs create -b. ***In a previous post I was told to 'drop the create -b because it ***creates a 'whole root' zone. So, okay here is what happens when I do. ***The following is my session: zonecfg -z CIS2 zonecfg:CIS2 create zonecfg:CIS2 set autoboot=true zonecfg:CIS2 set zonepath=/zones/CIS2 zonecfg:CIS2 add inherit-pkg-dir zonecfg:CIS2:inherit-pkg-dir set dir=/opt zonecfg:CIS2:inherit-pkg-dir end zonecfg:CIS2 add net zonecfg:CIS2:net set address=156.12.1.129 zonecfg:CIS2:net set physical=eri0 zonecfg:CIS2:net end zonecfg:CIS2 verify zonecfg:CIS2 export -f /export/home/porc1276/CIS2-zone.cfg zonecfg:CIS2 *** If I look at the text file I just exported, the first line is create -b ***Does this mean I am creating a 'whole root' zone? no, create -b just tells you that you start with a blank configuration and then you can see that /lib, /platform, /usr and /sbin are inherited in order to create a sparse root zone. -- Renaud bash-3.00# more CIS2-zone.cfg create -b set zonepath=/zones/CIS2 set autoboot=true add inherit-pkg-dir set dir=/lib end add inherit-pkg-dir set dir=/platform end add inherit-pkg-dir set dir=/sbin end add inherit-pkg-dir set dir=/usr end add inherit-pkg-dir set dir=/opt end add net set address=156.12.1.129 set physical=eri0 end bash-3.00# ***Thanks, ***F.V.(Phil) Porcella ***PS This is a bit confusing and I would appreciate any help you can offer. This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] create command question
F.V.(Phil)Porcella wrote: ***Hi, ***I was hoping to get an answer a question about create vs create -b. ***In a previous post I was told to 'drop the create -b because it ***creates a 'whole root' zone. So, okay here is what happens when I do. ***The following is my session: zonecfg -z CIS2 zonecfg:CIS2 create zonecfg:CIS2 set autoboot=true zonecfg:CIS2 set zonepath=/zones/CIS2 zonecfg:CIS2 add inherit-pkg-dir zonecfg:CIS2:inherit-pkg-dir set dir=/opt zonecfg:CIS2:inherit-pkg-dir end zonecfg:CIS2 add net zonecfg:CIS2:net set address=156.12.1.129 zonecfg:CIS2:net set physical=eri0 zonecfg:CIS2:net end zonecfg:CIS2 verify zonecfg:CIS2 export -f /export/home/porc1276/CIS2-zone.cfg zonecfg:CIS2 *** If I look at the text file I just exported, the first line is create -b ***Does this mean I am creating a 'whole root' zone? No. Sorry for confusing you earlier, I missinterpretted you're earlier mail, I though it was a script you were using. zoencfg will always show the create -b, basically the default zone type is sparse, and we crate this by using the default blank template ( the -b bit ) then add teh inherited dirs to that to make it sparse, so zonecfg was correct and i missinterpreted it. bash-3.00# more CIS2-zone.cfg create -b set zonepath=/zones/CIS2 set autoboot=true add inherit-pkg-dir set dir=/lib end add inherit-pkg-dir set dir=/platform end add inherit-pkg-dir set dir=/sbin end add inherit-pkg-dir set dir=/usr end add inherit-pkg-dir set dir=/opt end add net set address=156.12.1.129 set physical=eri0 end bash-3.00# ***Thanks, ***F.V.(Phil) Porcella ***PS This is a bit confusing and I would appreciate any help you can offer. This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] zone install problem
Hi, we just received a couple of T1000's and i am trying to create a few zones on the boxes. after configuring the zone, i type the zone install command and receive the following error: [EMAIL PROTECTED] # zoneadm -z oracle-zone install Waiting for up to 300 seconds for zone administration commands to become available (another user is administering zones) ERROR: Unable to acquire zone administration lock for this system; please try ag ain later ERROR: cannot create zone boot environment oracle-zone zoneadm: zone 'oracle-zone': '/usr/lib/lu/lucreatezone' failed with exit code 94. i am the only person logged into the box. The install of the OS is the vanilla install that comes preloaded with the unit. zone config as follows: zonecfg:oracle-zone info zonepath: /export/zones/oracle-zone autoboot: true pool: inherit-pkg-dir: dir: /lib inherit-pkg-dir: dir: /platform inherit-pkg-dir: dir: /sbin inherit-pkg-dir: dir: /usr net: address: 10.84.18.187 physical: bge0 i have done the std google search...but to no avail. any assistance appreciated... Jim This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
