On Thu, 18 Feb 2010 19:58:11 +0100, Christine Tran <christine.t...@gmail.com> 
wrote:

> On Sat, Feb 13, 2010 at 3:10 AM, Frank Batschulat (Home)
> <frank.batschu...@sun.com> wrote:
>>
>> a '-x nodataset' option for 'clone' like in 'install' is unlikely going to 
>> happen, in
>> fact I will remove the '-x nodataset' option for 'install' completely soon 
>> in OSOL build 135
[...]
> I have created test ipkg type zones on this laptop before, I have not
> done an upgrade but I've allowd Package Manager to update packages as
> far as it's abled.  You say you will remove -x nodataset option,
> implying it hasn't been done yet, but here's what happened this

the '-x nodataset' option does only apply to the 'native' brand (ie. Solaris 
10, SX-DE)
(see native(5)) - it is not available to the 'ipkg' brand nor is it available
for the solaris8, solaris9 and solaris10 brands.

> morning when I tried to create a new zone.
>
> r...@fiat~> cat /etc/release
>                        OpenSolaris 2008.11 snv_101b_rc2 X86
>            Copyright 2008 Sun Microsystems, Inc.  All Rights Reserved.
>                         Use is subject to license terms.
>                            Assembled 19 November 2008
>
> r...@fiat~> zonecfg -z pink
> pink: No such zone configured
> Use 'create' to begin configuring a new zone.
> zonecfg:pink> create
> zonecfg:pink> set zonepath=/zone/pink
> zonecfg:pink> add net
> zonecfg:pink:net> set physical=e1000g0
> zonecfg:pink:net> set address=192.168.20.1/24
> zonecfg:pink:net> end
> zonecfg:pink> verify
> zonecfg:pink> commit
> zonecfg:pink> info
> zonename: pink
> zonepath: /zone/pink
> brand: ipkg
> autoboot: false
> bootargs:
> pool:
> limitpriv:
> scheduling-class:
> ip-type: shared
> net:
>       address: 192.168.20.1/24
>       physical: e1000g0
>       defrouter not specified
> zonecfg:pink> exit
> r...@fiat~> zoneadm -z pink install -x nodataset
> Error: no zonepath dataset.

thats one of the problems that may arise, since the
'-x nodataset' option is really handled inside zoneadm.c:install_func()
and not in the brand specific code that is executed later.

zoneadm did honoured this option, but the 'ipkg' brand
specific code that will be executed _after_ zoneadm.c:install_func()
barfs.

> OK, I will create a dataset:
>
> r...@fiat~> zfs list
> NAME                      USED  AVAIL  REFER  MOUNTPOINT
> rpool                    26.4G  71.5G    72K  /rpool
> rpool/ROOT               19.8G  71.5G    18K  legacy
> rpool/ROOT/opensolaris   19.8G  71.5G  19.6G  /
> rpool/dump               1.97G  71.5G  1.97G  -
> rpool/export             2.70G  71.5G    19K  /export
> rpool/export/home        2.70G  71.5G    19K  /export/home
> rpool/export/home/ctran  2.70G  71.5G  2.70G  /export/home/ctran
> rpool/swap               1.97G  73.5G  3.81M  -
> r...@fiat~> zfs create rpool/pink
> r...@fiat~> zfs set mountpoint=/zone/pink rpool/pink
> r...@fiat~> zfs list
> NAME                      USED  AVAIL  REFER  MOUNTPOINT
> rpool                    26.4G  71.5G    74K  /rpool
> rpool/ROOT               19.8G  71.5G    18K  legacy
> rpool/ROOT/opensolaris   19.8G  71.5G  19.6G  /
> rpool/dump               1.97G  71.5G  1.97G  -
> rpool/export             2.70G  71.5G    19K  /export
> rpool/export/home        2.70G  71.5G    19K  /export/home
> rpool/export/home/ctran  2.70G  71.5G  2.70G  /export/home/ctran
> rpool/pink                 18K  71.5G    18K  /zone/pink
> rpool/swap               1.97G  73.5G  3.81M  -
>
> Try to install again
>
> r...@fiat~> zoneadm -z pink uninstall
> Are you sure you want to uninstall zone pink (y/[n])? y
> cannot open 'rpool/pink/ROOT': dataset does not exist
> Error: no active dataset.
> cannot open 'rpool/pink/ROOT': dataset does not exist
> cannot open 'rpool/pink/ROOT': dataset does not exist
> cannot open 'rpool/pink/ROOT': dataset does not exist
> Error: destroying ZFS dataset.

more follow up problems that result from the fact that
zoneadm honoured the '-x nodataset' option when it really must not.

---
frankB
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to