topic Ignite-Cloning a System Changes Kernel Params? in Operating System - HP-UX

Ignite-Cloning a System Changes Kernel Params?

Alzhy — Thu, 12 Apr 2007 10:51:17 GMT

Is this supposedly the normal behaviour? We're at the latest C release.

Just noticed a clone I made, SHMMAX was set on the orginal machine at 32GB. The cloned machine now shows only 128MB... (0x8000000 bytes)

Re: Ignite-Cloning a System Changes Kernel Params?

Steven E. Protter — Thu, 12 Apr 2007 10:59:19 GMT

Shalom Nelson,

No that is not normal behavior.

Kernel parameters are preserved unless the target system can't meet the settings.

SEP

Re: Ignite-Cloning a System Changes Kernel Params?

Alzhy — Thu, 12 Apr 2007 13:03:03 GMT

Peace too SEP.

I just tried. It does appear it changes certain kernel params.

Anyone else?

Re: Ignite-Cloning a System Changes Kernel Params?

Aussan — Thu, 12 Apr 2007 14:17:44 GMT

are you cloning to a similar system?
if so ignite assumes it's the same system and does not rebuild the kernel, to change that you have to set the _CLONING_HP to true
in the additional tab in itool you'll see it

Re: Ignite-Cloning a System Changes Kernel Params?

Alzhy — Thu, 12 Apr 2007 14:22:14 GMT

Aussan,
Thanks for the tip...

Our reference system (where we make clones from) is a SuperDome vPar (128GB of Memory). The 2 clones I've done to rp8420 vPars (16GB and 4GB of memory).

So there is such an ignite param... Wil try it..

Thanks!