Question : Solaris 10 zone fails to start up

I have a newly-installed Solaris 10 server where I can install zones and they work correctly.  I can create, install, boot, halt, etc. normally.

The company I'm working for requires a certain configuration (based on CIS benchmarks) on the servers for security reasons.  To help apply the required security settings, I was given a set of scripts that set permissions, disable services, modify configuration files, etc.  Once applied and following a reboot, the server still works fine, but the zones fail to start up.

I can type "zlogin -C myzone" and get to the console, but there is no output and it does not react to any of my input (and I've tried all kinds of input, including numbers, y/n, etc.).  I have to exit out using "~."

All of the verification methods for zones report normal.  I have no entries in /var/adm/messages (good or bad).  I have found no other log files with any information.

Based on some extensive web searches, I tried the following dtrace comamnd:
dtrace -qn 'proc:::exec-success { printf("%-14s %s\n",curthread->t_procp->p_parent->p_user.u_comm, curpsinfo->pr_psargs); }'
The output shows these messages repeated constantly and in quick succession:
init           INITSH -c exec /lib/svc/bin/svc.startd >/dev/msglog 2<>/dev/msglog </dev/consol
init           /etc/sulogin -
init           INITSH -c exec /lib/svc/bin/svc.startd >/dev/msglog 2<>/dev/msglog </dev/consol
init           /etc/sulogin -
init           INITSH -c exec /lib/svc/bin/svc.startd >/dev/msglog 2<>/dev/msglog </dev/consol
init           /etc/sulogin -
init           INITSH -c exec /lib/svc/bin/svc.startd >/dev/msglog 2<>/dev/msglog </dev/consol
init           /etc/sulogin -

The uncommented lines in the zone's inittab are as follows (which I have not modified):
smf::sysinit:/lib/svc/bin/svc.startd >/dev/msglog 2<>/dev/msglog </dev/console
p3:s1234:powerfail:/usr/sbin/shutdown -y -i5 -g0 >/dev/msglog 2<>/dev/msglog

The command "ps -efZ | grep myzone" shows the following:
  myzone    root   752   738   7 15:22:41 ?           1:28 /sbin/init
  myzone    root   738     1   0 15:22:41 ?           0:00 zsched
  global    root  9583   359   0 15:27:56 pts/1       0:00 grep myzone
  global    root   737     1   0 15:22:41 ?           0:00 zoneadmd -z myzone
  myzone    root  3106   752   0 15:27:04 ?           0:00 INITSH -c exec /lib/svc/bin/svc.startd >/dev/msglog 2<>/dev/msglog </dev/consol

The INITSH line sometimes shows up and sometimes not, but always with a new PID.

I've tried everything I can think of, but have not yet found anything that fixes the issue.  I'm going over the configuration scripts with a fine-tooth comb right now, but they are very long and involved.  I'd love any suggestions as far as what I should focus on, what the likely culprit is, etc.

Answer : Solaris 10 zone fails to start up

Run a scan with malwarebytes or norton.