vpar can not boot !

[黄家团]

RX8640 VPAR A.05.03
HPUX> boot /stand/vpmon
> System Memory = 334 MB
loading section 0
.... (complete)
loading section 1
......................................................................................................... (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
......Launching /stand/vpmon
SIZE: Text:1563K + Data:53305K + BSS:10763K = Total:65633K

Console is on virtual console - via PCDP
Granule size in NVRAM (0 0) does not match database(128 128). Rebooting system.

[sujit kumar singh]

hi
need to check and correct module size as specified in NVRAM with that in /stand/vpdb
regards
sujit

[sujit kumar singh]

hi


boot in NPAR mode and change the granularity.


regards
sujit

[sujit kumar singh]

hi


what actually had happened, FW upgrade, RAM upgrade , VPDB chnage?

you can get help of commands vparenv and vparresouces to set this.

please have a look at the VPAR admin guide, page no:227-228


http://www.docs.hp.com/en/T1335-90098/T1335-90098.pdf

regards
sujit

[Vivek Bhatia · Accepted solution]

Hi,

Have a look at the information below.

Granule:
a. Smallest chunk of memory assignable to individual vPars
b. Granule size is defined at database (/stand/vpdb) creation time

Error:Granule size in NVRAM (0 0) does not match database(128 128). Rebooting system.

Run the below command to check the granule info on the server

# vparenv
vparenv: The next boot mode setting is "vPars".
vparenv: The ILM granule size setting is 128.
vparenv: The CLM granule size setting is 128.


The ILM and CLM granule size information specified by the system administrator is stored in the vParsdatabase when it is created. For A.04.xx and A.05.xx vPars releases, the default size is 128 MB for both ILM and CLM. On HP Integrity servers, the firmware also divides the memory into memory objects based on the granule size. Hence, to inform firmware, in addition to the vPars database, thegranule size information is also stored in non-volatile RAM (NVRAM). The following provides detailson how to configure granule size in the A.04.xx and A.05.xx vPars releases. As mentioned earlier, this configuration is not required in the A.01.xx, A.02.xx and A.03.xx vPars releases as the granulesize is fixed at 64 MB.

See the manual below to fix this issue.
http://www.docs.hp.com/en/9832/vParsMemMigration.pdf

Create the first partition and the vPars database and specify the ILM and CLM granule sizeusing the -g option. On HP Integrity servers, specify the y attribute to update the firmware NVRAM with the granule size.

# vparcreate â p -D -g ilm:[:y] â g clm:[:y] ..

Regards,
Vivek

[黄家团]

boot to npars
#vparenv -g ILM:128 -g CLM:128
#vaprenv -m vpars
#shutdown -ry 0
It is OK!

[Vivek Bhatia]

Hi,

yes you can try that.

Regards,
vivek

[黄家团]

Thanks! I test it ,and it work now!

[Vivek Bhatia]

Hi,

Dont forget to assign points to all who have replied to your questions.

Regards
Vivek Bhatia