Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

If the amount of swap created is more than 32 GB, you must increase the kernel tunable swchunk
from its default of 2048. This is not an automatic process. If there is insufficient kernel resources
configured to enable you to use the swap being created, a message appears indicating this during
the installation process. This message might not be accurate if the swchunk value is manually
changed using a configuration file as default value of swchunk (that is, 2048) is considered and
does not take into account any changes to its value.
You can manually increase swchunk once the installation process is complete using SAM. To
increase swchunk during an Ignite-UX installation, you can place a line like the following in the
Ignite-UX configuration:
mod_kernel += "swchunk 4096"
With swchunk set to 4096, you are able to utilize up to 64 GB of swap, assuming that Ignite-UX
had to set maxswapchunks to its maximum value of 16384.
NOTE: Ignite-UX does not detect any changes you make to swchunk manually. It limits the total
size of all swap space to 32 GB.
To calculate how much swap can be utilized, multiply swchunk by maxswapchunks. For example:
16384 * 4096 = 67108864
Since swchunk is measured in KB, 67108864 / (1024*1024) = 64 GB. Provision to configure
more space in swap space than what the kernel can use is provided. Hence, setting swchunk and
maxswapchunks values appropriately for a large configuration is important.
Currently, the maximum supported value of swchunk is 16384. This gives a total of 256 GB of
addressable swap with both swchunk and maxswapchunks set to 16384.
Do not assign large amount of swap space while setting values for maxswapchunks and swchunk.
These values are used to allocate kernel memory that is used to track the swap resources, setting
them too large wastes memory. To efficiently use kernel memory set swchunk as a power of 2
(for example: 2048, 4096, 8192, 16384, and so on).
When choosing values, assign swchunk the lowest value that you can, and then choose the value
needed for maxswapchunks to address the swap required. On a system that actively swaps
memory to a swap space, there might be performance implications when increasing swchunk
past its default of 2048.
The HP-UX Memory Management White Paper (mem_mgt.txt located in /usr/share/doc)
contains detailed information about how swap is controlled inside the kernel.
Additionally, to create logical volumes as unused logical volumes rather than swap logical volumes
you can configure them to be used for swap after the installation process has completed. This is
important only if you need the swap spaces allocated in a particular order.
Why do the text fields in the Ignite-UX TUI not accept my input, and the dialogs
re-open or loop?
The text fields within the Ignite-UX TUI do not recognize keyboard input when the Insert key is
active. Make sure that the Insert key is inactive when entering data in the TUI by pressing it.
What HP applications are tested for use with Ignite-UX?
HP applications that have been tested with Ignite-UX have an OD1 option on the HP CPL (Corporate
Product List), which indicates the factory integrate option. This option directs HP factories to install
the software on the client before it leaves the factory. HP manufacturing installs the software from
a depot using the Ignite-UX process.
All HP applications identified with an OD1 ordering option may be installed from a depot.
Frequently asked questions 29