Problem with zone creation in Solaris 10 6/06

Hi,

I have configured and installed a non-global zone following the example given in the guide http//www.sun.com/software/solaris/howtoguides/posgresqlhowto.jsp. My zone has the following configuration:

# zonecfg -z pg_zone

zonecfg:pg_zone> info

zonepath: /export/zones/pg_zone

autoboot: true

pool:

fs:

dir: /pg_log

special: /dev/dsk/c1d0s0

raw: /dev/rdsk/c1d0s0

type: ufs

options: []

net:

address: 192.168.10.100/24

physical: bge0

zonecfg:pg_zone> exit

The installation completed but I got the following errors:

# zoneadm -z pg_zone install

Preparing to install zone <pg_zone>.

Creating list of files to copy from the global zone.

Copying <130101> files to the zone.

Initializing zone product registry.

Determining zone package initialization order.

Preparing to initialize <1059> packages on the zone.

Initialized <1059> packages on zone.

Zone <pg_zone> is initialized.

Installation of these packages generated errors: <SUNWgnome-a11y-libs-share>

Installation of <63> packages was skipped.

The file </export/zones/pg_zone/root/var/sadm/system/logs/install_log> contains a log of the zone installation.

When examined the logs there were several messages like this:

SUNW_PKG_THISZONE=true in the pkginfo file.

*** package <SUNWamutl> was not installed:

The package <SUNWamutl> is registered to be installed in the

global zone only. The package may have been installed in the global

zone using the pkgadd '-G' option, or the package may contain a

request script, or the package may directly set the package attribute

SUNW_PKG_THISZONE=true in the pkginfo file.

*** package <SUNWiimdv> was not installed:

The package <SUNWiimdv> is either not fully installed in the

global zone, or the package contains a request script. Only packages

that are fully installed in the global zone and that do not contain a

request script can be installed when a new zone is created. If this

package does not contain a request script, you can correct this

problem by removing and reinstalling the package in the global zone.

And when I try to boot the zone I get this error:

# zoneadm -z pg_zone boot

zoneadm: zone 'pg_zone': "/usr/lib/fs/lofs/mount -o zonedevfs /export/zones/pg_zone/dev /export/zones/pg_zone/root/dev" failed with exit code 33

zoneadm: zone 'pg_zone': call to zoneadmd failed

Any suggestion how to solve this problem?

thanks

[2713 byte] By [payn] at [2007-11-26 10:28:30]
# 1
Perhaps removing the offending packages, then installing them with the -G option, then try to create a new zone, see how it goes?
HenryC at 2007-7-7 2:33:34 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 2
Did you perform "zonecfg -z pg_zone ready" command before performing "zonecfg -z pg_zone boot" ?
wangzh at 2007-7-7 2:33:34 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 3

To answer your question wangzh: Yes I did. I actually followed exactly the procedure on the how-to-uides: http://www.sun.com/software/solaris/howtoguides/containersLowRes.jsp.

I think the problem here might reside in the script supplied in the solaris distribution for creating zones. For example, in the default configuration script, the package directories /lib /platform /var and /usr are by default set to be automatically imported. But when I try to create a zone using these defaults settings, it ends up with an mounting error that prevents the installation of the zone. only when I remove manually those directories from the configuration then the installation continues.

And during the installation process there are number of packages that are by default imported via the installation script and this is some of those packages that cause the errors here. I also tried to exclude the offending packages as suggested by henryC but I couldn't find all of them and the creation still fails at the booting.

payn at 2007-7-7 2:33:34 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 4
I wrote my own scripts.ftp://ftp.warthog.com/pub/warthog/Solaris/makezone.kshIf you want to dabble with one-command destroying, have a go at destroyzone.ksh in the same location.
WRWindsor at 2007-7-7 2:33:34 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 5

Finally, I could locate all the offending packages. They all are from the Sun Java Enterprise System suite installation. So I completely uninstalled these components . After that my zone creation went smoothly.

So my advice is: DO NOT install SJES on your system until you finish creating your zones, unless you do not want to use the zones in your solaris installation.

WRWindsor: thank you for your link. I will consider try to execute your script later and give you a feedback.

However I encountered another problem with the network configuration of the zone. The booting rejected the network address I assigned to the zone with a message saying that this address is already in use by the global zone. So I skipped the step of the network configuration. But the question remains: is there a way to share the same network address between global and non-global zones? May be by using the pooling feature...or by configuring a VLAN?

Any suggestion?

payn at 2007-7-7 2:33:34 > top of Java-index,Solaris Operating System,Solaris 10 Features...