Hi,
I recently tried to use zonemgr 1.8.1 to install a whole root zone (for a
database) on nv_98, and it errored out:
-bash-3.2# ./zonemgr-1.8.1.sh -a add -t w -n ultra1z3 -z "/zones" -P
"extrap01ate" -I "192.168.1.203|skge0|24|ultra1z3"
Checking to see if the zone IP address (192.168.1.203) is already in use...IP
is available.
On line 4 of /root/.zonemgr/zone1197:
remove inherit-pkg-dir: No such resource with that id
Error: Error configuring ultra1z3, return value: 0
Use -h flag to see proper usage or -l flag to see the license.
So, here's the zone spec:
-bash-3.2# more /root/.zonemgr/zone1197
create
set zonepath=/zones/ultra1z3
set autoboot=true
remove inherit-pkg-dir dir=/lib
remove inherit-pkg-dir dir=/usr
remove inherit-pkg-dir dir=/sbin
remove inherit-pkg-dir dir=/platform
add attr
set name=comment
set type=string
set value="Zone ultra1z3"
end
add net
set address=192.168.1.203/24
set physical=skge0
end
verify
commit
-bash-3.2#
It appears that something has changed since Sol10 (and maybe earlier versions
of OpenSolaris with the way the default zone spec is defined. Here is the
config from a sparse zone created with zonemgr using "-t s":
-bash-3.2# zonecfg -z ultra1z1 info
zonename: ultra1z1
zonepath: /zones/ultra1z1
brand: ipkg
autoboot: true
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
net:
address: 192.168.1.201/24
physical: skge0
defrouter not specified
attr:
name: comment
type: string
value: "Zone ultra1z1"
-bash-3.2#
So, two questions:
1) What has changed between Solaris 10 and nv_98 (relevant to this issue of
course)?
2) Since I don't have any inherit_pkg_dir entries when I use the "-t s"
argument, am I creating a full zone by default?
Thanks,
John
--
This message posted from opensolaris.org
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org
