vPars in nPar, partition configuration lost concerning.

[Torsten.]

Normally the nPar boot disk is the same as the first vPar boot disk - same system, more resources in nPar mode.

You just need to boot "vmunix" instead of "vpmon" from ISL.

[stephen peng]

Steven,
>>The npar is normally configured to start up a system running vpmon, which starts up the vpar monitor.
I read from manual that system with vPars startup vpmon with "hpux /stand/vpmon", would this mean that the nPar also startup its os?


regards
Stephen

[stephen peng]

>>they are playing musical document locations.
agree with it very much!

[stephen peng]

>>You just need to boot "vmunix" instead of "vpmon" from ISL.
this completely get rid of one of my question!

regards
Stephen

[stephen peng]

why I concerned about nPar configuration lost was that if the first vPar contained two CPU from seperate CELLs and nPar lost its configuation, the nPar could only boot from monarch CELL so the vPar was not able to boot. am I wrong with it?

regards
Stephen

[Pete Randall]

>>I read from manual that system with vPars startup vpmon with "hpux /stand/vpmon", would this mean that the nPar also startup its os?

hpux is the "secondary system loader (SSL) utility for bootstrap" and, as such, it loads whatever it is told. You can have it load the VPAR monitor (vpmon) or you can have it load the hpux kernel.


Pete

[Steven E. Protter · Accepted solution]

Shalom again,

PSB


2. again in my mind, that nPar's boot disk should not be the same of those vPars, am I wrong? please explain this to me.

Same disk. You can boot in npar mode or vpar mode, but you use the same disk either way.

Changing modes requires a lengthy reboot on a superdome. If you want some assistance offline, see my ITRC profile.

SEP

[Torsten.]

The difference between booting nPars or vPars on a HP9000 is, if vpmon is booted, then you are in vPars mode.


Normally when you build a vPar environment, you install an OS on a nPar, define the vPars, boot the vpmon, then the vPars.

While doing this, the first installed OS (on nPar) is usually used for the first vPar.


But you can also define totally different vPars by not using the initial boot disk. This is up to you.

You can also boot any of the existing vPars boot disks in nPar mode - no problem.




But remember, all this is slightly different on a Integrity superdome, but totally different on a superdome 2.

[stephen peng]

I've got what I need in this thread!
thank you all!

regards
Stephen