Ed:

Did you run add_install_client from snv_114 with the -p and -c option:

# pwd
/export/nv/solarisdvd.nvx_dvd/latest/Solaris_11/Tools
#
# ./add_install_client -d -e 0:14:4f:28:43:34 -p 
ins3525-svr:/export/profile/nevadaprofile -c 
ins3525-svr:/export/profile/nevadaprofile i86pc
cleaning up preexisting install client "0:14:4f:28:43:34"
To disable 0:14:4f:28:43:34 in the DHCP server,
   remove the entry with Client ID 0100144F284334

If not already configured, enable PXE boot by creating
a macro named 0100144F284334 with:
   Boot server IP (BootSrvA) : 10.6.35.8
   Boot file      (BootFile) : 0100144F284334
# more /tftpboot/menu*0100144F284334
default=0
timeout=30
min_mem64 1024
title Solaris_11 Jumpstart
        kernel$ /I86PC.Solaris_11-1/platform/i86pc/kernel/$ISADIR/unix -B 
install_config=10.6.35.8:/export/profile/nevadaprofile,sysid_config=10.6.35.8:/export/
profile/nevadaprofile,install_media=10.6.35.8:/export/nv/solarisdvd.nvx_dvd/latest
        module$ /I86PC.Solaris_11-1/$ISADIR/x86.miniroot
#

We did not have any problems with jumpstart with snv_114 at all and it 
works fine.

If you want to use jumpstart, you should not use -s option though.

There are sigificant changes between snv_97 and snv_114. If you want to 
jumpstart snv_114, you have to use add_install_client from snv_114 with 
jumpstart.




Ed Spencer wrote:
> On Fri, 2009-05-29 at 16:26, Mike Gerdts wrote:
>> On Tue, May 26, 2009 at 2:15 PM, Ed Spencer <Ed_Spencer at umanitoba.ca> 
>> wrote:
>>> I'm having difficulties with jumpstart and nv114. Actually I have had 
>>> difficulties since
>>> nv97 which was the last build in which I was able to do a jumpstart install.
>>>
>>> I'm installing on a VMWare ESX virtual machine.
>>>
>>> I'll illustrate my problems with a simple network boot example.
>>>
>>> I select this entry from my menu.lst file:
>>> title S11_nv114 Network boot text console single user (VGA)
>>>        kernel I86PC.S11_nv114/platform/i86pc/kernel/unix -s
>>>        module /I86PC.S11_nv114/x86.miniroot
>>>
>>> And this is what happens:
>>> .........................................................................
>>> Booting 'S11_nv114 Network boot text console single user (VGA)'
>>>
>>> kernel I86PC.S11_nv114/platform/i86pc/kernel/unix -s
>>>   [Multiboot-elf, <0xc00000:0x109d4:0x0>, <0x400000:0xd68d4:0x0>, 
>>> <0x800000:0x
>>> 9518:0x3e1d0>, shtab=0xc11370, entry=0xc00000]
>>> medule /I86PC.S11_nw114/x86.miniroot
>> Is that "module" or "medule"?
> Sorry its "module". Its vmware so I HAD TO "type" the output from the 
> console. 
> 
> I've tried many iterations of the commands in the menu.lst including
> using the kernel$ and module$ and adding $ISADIR. 
> What seems to be happening is the kernel loads but when x86.miniroot
> begins to load I get "Error 25: Disk Read Error".
> 
> Ed  
>> -- 
>> Mike Gerdts
>> http://mgerdts.blogspot.com/


Reply via email to