This discussion is archived
2 Replies Latest reply: Jun 22, 2012 8:17 AM by 935139 RSS

Sol10U10  Jumpstart configuration running on VMware (ESX Server 3.5)

931193 Newbie
Currently Being Moderated
Hi all,

I'm trying to setup my jumpstart lab using a bunch of  VMware (ESX Server, 3.5.0-317866) virtual machines.
I played a little bit to try to set up such a configuration.
I found official documentation and advices around on the web.
The config seems now matching all the bestpractices and suggestions I found but.....
once booting the client I had a sort of panic.

A weird panic....after the GRUB entry is selected the client seems to start showing the Solaris info correctly
but just after the "solaris info" tag is printed the console shows:

panic[threadID_NUMBER]:


and nothing else. And the systems seems stuck there.

Below a summary of the configuration and the setup I did.
Any help/advice would be really appreciated.

Regards,
francesca

=======
CONFIG
=======


1) Jumpstart Server:ESX Server, 3.5.0-317866 virtual machine running on running sol10U10

IP 10.33.199.144
net 10.33.199.0

2) Jumpstart Client :ESX Server, 3.5.0-317866 virtual machine to be installed with sol10U10

hostname x86_client1
IP 10.33.199.145
net 10.33.199.0
MAC address: 00:50:56:84:63:2c

3) HW: intel based PC (Intel Xeon 2.4ghz)




I setup of jumpstart/boot/dhcp server following documentation provided by : http://www.oracle.com/technetwork/systems/articles/jumpstart-x86-x64-jsp-138116.html
(I used dhtadm and pntadm instead of the dhcpmanager GUI)


The final config show the following setup:


/export/jumpstart contents:
-----------------------------------------

drwxr-xr-x 5 root root 512 May 8 09:55 Solaris10_811_x86
drwxr-xr-x 2 root root 512 May 8 09:35 boot
drwxr-xr-x 2 root root 512 May 8 13:49 config

boot directory is empty.


/export/jumpstar/config contents:
-------------------------------------------------


-r--r--r-- 1 root root 183 May 8 13:07 any_machine
-r-xr-xr-x 1 root root 64357 May 8 11:54 check
-rw-r--r-- 1 root root 219 May 8 13:14 example.sysidcfg
-rw-r--r-- 1 root root 60 May 8 13:42 rules
-rw-r--r-- 1 root root 85 May 8 13:49 rules.ok
-rw-r--r-- 1 root root 175 May 8 13:20 sysidcfg
-r--r--r-- 1 root root 135 May 8 13:49 x86_machine

where:

bash-3.2# more /export/jumpstart/config/rules
hostname x86_client1 - x86_machine -
any - - any_machine -

bash-3.2# more /export/jumpstart/config/sysidcfg
system_locale=C
timezone="GMT+1"
terminal=ansi
security_policy=NONE
timeserver=localhost
network_interface=primary
{protocol_ipv6=no
netmask=255.255.255.0}
name_service=NONE



x86_client1 name resolved thru /etc/hosts and mac address listed in /etc/ethers of course.




dhcptab entries with my macros and symbols:
------------------------------------------------------------------------


Name Type Value
==================================================
0100505684632C Macro :BootFile="0100505684632C":BootSrvA=10.33.199.144:
PXEClient:Arch:00000:UNDI:002001 Macro :BootFile="SUNW.i86pc":BootSrvA=10.33.199.144:
SbootFIL Symbol Vendor=SUNW.i86pc,7,ASCII,1,0
SbootURI Symbol Vendor=SUNW.i86pc,16,ASCII,1,0
SjumpsCF Symbol Vendor=SUNW.i86pc,14,ASCII,1,0
SsysidCF Symbol Vendor=SUNW.i86pc,13,ASCII,1,0
SinstPTH Symbol Vendor=SUNW.i86pc,12,ASCII,1,0
SinstNM Symbol Vendor=SUNW.i86pc,11,ASCII,1,0
SinstIP4 Symbol Vendor=SUNW.i86pc,10,IP,1,1
SrootPTH Symbol Vendor=SUNW.i86pc,4,ASCII,1,0
SrootNM Symbol Vendor=SUNW.i86pc,3,ASCII,1,0
SrootIP4 Symbol Vendor=SUNW.i86pc,2,IP,1,1



/tftboot contents:

lrwxrwxrwx 1 root root 26 May 10 15:09 0100505684632C -> pxegrub.I86PC.Solaris_10-1
dr-xr-xr-x 5 root root 512 May 8 09:55 I86PC.Solaris_10-1
lrwxrwxrwx 1 root root 26 May 10 14:59 SUNW.i86pc -> pxegrub.I86PC.Solaris_10-1
drwxr-xr-x 3 root root 512 May 10 14:59 boot
-rw-r--r-- 1 root root 362 May 14 12:36 menu.lst.0100505684632C
lrwxrwxrwx 1 root root 26 May 10 15:09 nbp.0100505684632C -> pxegrub.I86PC.Solaris_10-1
lrwxrwxrwx 1 root root 26 May 10 14:59 nbp.SUNW.i86pc -> pxegrub.I86PC.Solaris_10-1
-rwxr-xr-x 1 root root 140144 May 10 14:59 pxegrub.I86PC.Solaris_10-1
-rw-r--r-- 1 root root 179 May 10 15:09 rm.0100505684632C
-rw-r--r-- 1 root root 146 May 10 14:59 rm.SUNW.i86pc
  • 1. Re: Sol10U10  Jumpstart configuration running on VMware (ESX Server 3.5)
    YTC1 Newbie
    Currently Being Moderated
    Have you tried it with a non VMware client ? ie a physical box/laptop.

    If not, please do.

    If that works then the VMware settings can be looked at (as I suspect that is the most likely place).
  • 2. Re: Sol10U10  Jumpstart configuration running on VMware (ESX Server 3.5)
    935139 Newbie
    Currently Being Moderated
    Firstly, the good news is that your Jumpstart and DHCP configuration is working exactly as it should. In other words, if you got to the point where the client booted grub, and you were able to select the Solaris to install, and Solaris started.... then you've exercised pretty much everything the Jumpstart needs to do.

    Just to simplify, you didn't need the PXE macro, as you created a client specific macro.

    PXEClient:Arch:00000:UNDI:002001 Macro :BootFile="SUNW.i86pc":BootSrvA=10.33.199.144:

    and you didn't need to do the Vendor Symbol stuff, as this was for pre-grub based Solaris installations.
    SbootFIL Symbol Vendor=SUNW.i86pc,7,ASCII,1,0
    SbootURI Symbol Vendor=SUNW.i86pc,16,ASCII,1,0
    SjumpsCF Symbol Vendor=SUNW.i86pc,14,ASCII,1,0
    SsysidCF Symbol Vendor=SUNW.i86pc,13,ASCII,1,0
    SinstPTH Symbol Vendor=SUNW.i86pc,12,ASCII,1,0
    SinstNM Symbol Vendor=SUNW.i86pc,11,ASCII,1,0
    SinstIP4 Symbol Vendor=SUNW.i86pc,10,IP,1,1
    SrootPTH Symbol Vendor=SUNW.i86pc,4,ASCII,1,0
    SrootNM Symbol Vendor=SUNW.i86pc,3,ASCII,1,0
    SrootIP4 Symbol Vendor=SUNW.i86pc,2,IP,1,1

    I'm puzzled that you don't have a macro for the network saying something like:
    10.33.199.0 Macro :Subnet=255.255.255.0:Router=10.33.199.1:Broadcst=10.33.199.255

    However, I don't think any of the above are a problem yet.

    Could you show the contents of menu.lst.0100505684632C as this will show the boot arguments that were used.

    Could you also confirm whether your guest has been configured as a 32 or 64 bit? (I think this creates a subtle difference in the boot args in menu.lst.

    Have you tried manually installing the guest to ensure that the guest is actually properly configured to be able to run Solaris?

    Mike

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points