Jumpstart Solaris 8 vs. Solaris 10 (sparc)

Question

Hello Solaris Community.
I'm wondering if anyone else has seen this behaviour.
With Solaris 8, we've had a process in place for awhile now which has worked well. We've simply been creating compressed configuration tarfiles, parking them on an nfs share, then booting the Sun client from cd/dvd rom drive, using the appropriate obp command line:
boot cdrom - install nowin dhcp \
nfs://<nfsserver>/<path_to_compressed_config>/<config_tarball>
The machine would then go through the process of starting the kernel, grabbing an IP addres, grabbing the compressed config file, then kicking off the automated install. No need to mess with creating boot servers, etc.
With the inception of Solaris 10, however, this seems to have become broken. The system will start the kernel, obtain an IP address (with success), then promptly bust into an un-breakable loop of death. Here's the output:
.... [snip]
Configuring devices.
Trying DHCP on hme0
Success
Using DHCP for network configuration information.
<unknown>: warning: dhcpagent: daemonize: timed out awaiting adoption.
DHCP: using local media
/sbin/install-discovery: /usr/bin/loadkeys: not found
[ network/physical:default failed (see 'svcs -x' for details) ]
Feb 24 06:38:17 svc.startd[7]: svc:/network/loopback:default: Method "/lib/svc/method/net-loopback" failed with exit status 1.
[ network/loopback:default failed (see 'svcs -x' for details) ]
Feb 24 06:38:17 svc.startd[7]: svc:/system/filesystem/usr:default: Method "/lib/svc/method/fs-usr" failed with exit status 1.
Feb 24 06:38:18 svc.startd[7]: svc:/system/filesystem/usr:default: Method "/lib/svc/method/fs-usr" failed with exit status 1.
Feb 24 06:38:18 svc.startd[7]: svc:/system/filesystem/usr:default: Method "/lib/svc/method/fs-usr" failed with exit status 1.
[ system/filesystem/usr:default failed (see 'svcs -x' for details) ]
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login serice(s) cannot run
svc.startd: Could not exec() sulogin: No such file or directory
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
....... endless loop.
Something's obviously been modified for 10 -- has Sun removed the option for using compressed tar configuration files or something?
Thanks.

Answer 1

If you try to use slice1 as the root instead of Tools/Boot you get this error. You can still boot off the CD using slice1 as normal. We have modified the jumpstart to use this as well.
This works in the bootparams:
j197-svr root=jump8:/export/jump/slices.606/slice0.files/Solaris_10/Tools/Boot install=jump8:/export/jump/slices.606/slice0.files .....