zones created with blank templates do not boot properly

[Diego Lima]

After a fresh nexenta install I tried to create a zone with 'zonecfg -z myzone "create -b (...)" I could not boot the zone properly. The zone is installed and I am able to boot it, but trying to login with "zlogin -C myzone" hangs. I could then log in by issuing "zoneadm -z myzone reboot" into another pty - that caused the zlogin running to connect in maintenance mode. /lib/svc/bin/svc.startd was not running, though I could manually start it, and I could also install apache2 and start sshd.

Rebooting the zone would not start the services properly again. It only happens when creating zones with "create -b" or when I remove the inherited dirs manually - a zone created with inherited dirs worked perfectly.

[Diego Lima (diegolima)]

This is what happens (I have logged in the zone before booting it this time):

root@Wintermute:~# zlogin -C webzone
[Connected to zone 'webzone' console]
[NOTICE: Zone booting up]
SunOS Release 5.11 Version NexentaOS_20080131 32-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Mar 18 09:58:48 svc.startd[9627]: svc:/network/datalink-management:default: Method "/lib/svc/method/svc-dlmgmtd" failed with exit status 1.
Mar 18 09:58:49 svc.startd[9627]: svc:/network/datalink-management:default: Method "/lib/svc/method/svc-dlmgmtd" failed with exit status 1.
Mar 18 09:58:50 svc.startd[9627]: svc:/network/datalink-management:default: Method "/lib/svc/method/svc-dlmgmtd" failed with exit status 1.
Mar 18 09:58:50 svc.startd[9627]: network/datalink-management:default failed: transitioned to maintenance (see 'svcs -xv' for details)
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass):

[Tim Spriggs (tim-tajinc)]

The following configuration works under NCP2 with the latest nexenta-zones package.

create -b
set zonepath=/zones/fiji
set autoboot=false
set ip-type=shared
add net
set address={ipv4 address}
set physical=bge0
end

Using the above configuration as an example, there is one outstanding bug that can be worked around via the following immediately after the zone install:

vim /zones/fiji/root/etc/shadow

Edit the root entry and set the password field to NP. See other entries in the same file as a template. This will enable zlogin -z fiji to work.