Understand option in vparecreate Post: 302434718

Sponsored Content

Operating Systems HP-UX Understand option in vparecreate Post 302434718 by DustBunny on Monday 5th of July 2010 02:11:56 AM

07-05-2010

Registered User

It means, you are setting granularity. However, the default value is the same value you are trying to specify.

Granularity refers to the unit size in which memory is assigned to all virtual partitions in a given vPars database (vpdb). Granularity reflects only the unit size of memory and not the amount of memory that is assigned.

The default granularity is 128 MB for ILM and 128 MB for CLM. However, you can specify your own granularity for CLM and/or ILM. Granularity has some specific restrictions and cannot be changed in a vPars database after they are set.

Integrity Systems.

There are two areas where granularity values are set:

The nPartition firmware, specifically the EFI variables in NVRAM (non-volatile RAM).
The vPars database.

In order for the virtual partitions in the vPars database to be able to boot, the granularity values in the vPars database must match the granularity values in the firmware.

On Integrity systems, memory is divided into the granules by the firmware; therefore, it is required that you set and match the corresponding EFI variables.

PA-RISC systems. There is only one area where granularity values are set: the vPars database.

For PA-RISC, there are no granularity values in the PA-RISC firmware. The memory is divided into the granules by the Monitor itself. Note that this means the update firmware option ([:y]) of vparcreate is ignored on PA-RISC.

Syntax works like this:

# vparcreate -p vpar1_name [-g ILM:unit[:y] ] [-g CLM:unit[:y] ]

Note the below:

If you specify the above command without the :y, vparcreate only writes the unit granularity value to the vPars database; it does not write the value to firmware.

If you specify the above command with the :y, vparcreate writes the unit granularity value to both the vPars database and to firmware.
When using this method, note that the -g option must be performed when creating the vPars database (in other words, when performing the initial vparcreate command). If you choose not to set a value, or if you set
the value incorrectly using the initial vparcreate command, you cannot adjust it later. You must re-create the vPars database.

-DB

DustBunny

View Public Profile for DustBunny

Find all posts by DustBunny

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

can't understand

how i can download this game n start it :S

2. What is on Your Mind?

dont understand

i'm trying to learn unix and i posted a question and what i was typing from school. i can't figure it out. how am i supposed to learn , when i get shutdown by an admin. for posting a homework question. doesn't make any sense. its a dumb rule. thanks for helping

3. UNIX for Dummies Questions & Answers

can't understand this at all.

Ok, i've been trying to write some shell scripts. nothing challenging, but just automating All of the tutorials i read say to start the file with #!/bin/bash or whatever your path to bash is. So i do it, and all of my scripts error out saying ./nameofscript:command not found when i...

4. Shell Programming and Scripting

option followed by : taking next option if argument missing with getopts

Hi all, I am parsing command line options using getopts. The problem is that mandatory argument options following ":" is taking next option as argument if it is not followed by any argument. Below is the script: while getopts :hd:t:s:l:p:f: opt do case "$opt" in -h|-\?)...

5. Shell Programming and Scripting

recently introduced to the newer option for find...does an older option exist?

To find all the files in your home directory that have been edited in some way since the last tar file, use this command: find . -newer backup.tar.gz Is anyone familiar with an older solution? looking to identify files older then 15mins across several directories. thanks, manny

6. Shell Programming and Scripting

can't understand!

Hi All, can you please help me to figured out what's the meaning of this. ${SERVER_DATABASE} -b << EOF 2>>/dev/null THanks,

7. Shell Programming and Scripting

Understand the importance of -depth option in find command.

Hi All, Can you please help me in understanding the importance of -depth of find. I am trying to execute below code.find . -mtime +5 -name "*" -depth -exec ls -l {} \; But it is throwing below error.find: warning: you have specified the -depth option after a non-option argument -mtime,...

8. UNIX for Dummies Questions & Answers

help me to understand this code

Hi guys can you please help me to understand this code . tmpArray=(${line//=/ }) Please next time open a new thread in the appropriate forum and use code tags

9. Solaris

Unrecognized option: sparc-sun-Solaris2.10/bin/as: unrecognized option `-m32'

Hi, I installed some packages required by an app built with python. But when I try python setup.py install, I get the following error: /opt/csw/lib/gcc/sparc-sun-solaris2.10/5.2.0/../../../../sparc-sun-solaris2.10/bin/as: unrecognized option `-m32' Could anyone tell me what's wrong...

LEARN ABOUT HPUX

vparenv

vparenv(1M)															       vparenv(1M)

NAME

       vparenv - display or set the environment for the next boot

SYNOPSIS

       mode] memtype:size]

DESCRIPTION

       The  command displays or sets appropriate firmware variables on Itanium-based platforms.  The variables manage the partition boot mode ( or
       CLM granularity and ILM granularity.  By default, the command displays the current settings of the partition boot mode and memory granular-
       ities.

       The  command  also  displays  the  maximum possible ILM granules for the system and the maximum possible CLM granules per cell.	Note: This
       information is displayed by the command only if the system has been switched to vPars mode atleast once after a system reset.  Users should
       consider  these maximums when specifying either granularity.  Care should be taken to choose granule sizes which do not result in the total
       number of granules exceeding the permissible limits for that system.

       In certain scenarios, the command may not be able to validate if the chosen memory granularities are appropriate for the system.  The  com-
       mand  will  display a warning message. In such cases, the user should validate the granularities against the total memory on the system and
       the supported number of memory granules on the system. Please refer to manpage for more details.

       Note: This command does not modify the ILM/CLM granule values in the vPars database file. It only modifies the appropriate EFI variables.

       This command is not supported on PA-RISC platforms.

   Options and Arguments
       recognizes the following command line options and arguments:

       Specifies the mode for the next system boot.
			 The valid values for mode are case-insensitive If mode is specified as then after the next reboot, the system will be	in
			 the vPars mode.  If mode is specified as then after the next reboot, the system will be in the nPars mode.

			 Note: The mode setting does not take effect until the next system (hard partition) reboot.

       Specifies the desired granularity of Cell Local Memory (CLM) or
			 InterLeaved  Memory  (ILM)  to  be set in the appropriate EFI variable.  memtype specifies the type of memory.  The valid
			 values are case insensitive and size specifies the desired granularity in megabytes.  Note: The granule settings  do  not
			 take effect until the next system (hard partition) reboot.

WARNINGS

       The EFI granule settings must be the same as those in the vPar database loaded into the monitor.  If one or both settings do not match, the
       monitor will not allow any vPar to boot.  Refer to the vparcreate(1M) manpage.  To correct this, you must either change the  EFI  variables
       using this command or change the granularity values in the database file by recreating the database using

EXAMPLES

       Set the boot mode to

       Set the CLM granularity to 128 MB.

       Set the ILM granularity to 128 MB and CLM granularity to 128 MB.

SECURITY RESTRICTIONS

       This command is restricted to processes owned by superuser.

       When virtual partition flexible administrative capability is enabled, the boot environment firmware variables can only be set from within a
       Designated-Admin vPar.

RETURN VALUE

       The command exits with one of the following values:

       Successful completion.
       An error condition occurred.

AUTHOR

       was developed by the Hewlett-Packard Company.

SEE ALSO

       vparadmin(1M), vparboot(1M), vparconfig(1M), vparcreate(1M), vpardump(1M), vparefiutil(1M), vparextract(1M), vparmodify(1M), vparreloc(1M),
       vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), vparresources(5), vpartition(5), vpmon(5).

							   Itanium(R)-based Systems Only					       vparenv(1M)