Page Comparison

set session <parameter>=<value>

Virtual HP Alpha system hardware model to be emulated.

Use a default configuration template for each particular model as a starting point for a custom configuration. This would ensure that the parameter is set correctly.

Example:

Name of the CHARON-AXP instance (ir must be unique):

The value of this parameter is used as a prefix to the event log file name. (see below).

From the example above, the CHARON-AXP log file will have the following name:

xxxxxxxxx is an increasing decimal number starting from 000000000 to separate log files with the same time of creation (in case the log is being written faster than one log file per second).

It is strictly recommended to use the "configuration_name" parameter if more than one CHARON instance runs on the same server.

The log file or directory name is where the log file for each CHARON-AXP execution session is stored. If an existing directory is specified, CHARON-AXP automatically creates individual log files for each CHARON-AXP execution session. If the log parameter is omitted CHARON-AXP creates a log file for each CHARON-AXP execution session in the directory where the emulator was started.

It is possible to overwrite the existing log file or extend it using the "log_method" parameter. See below for details. The "log_method" parameter is effective only in the case where a single log file is specified, not a directory.

Examples:

If only a directory name is specified in the "log" parameter and the "configuration_name" parameter of the session is specified, the log file name will have the following format:

If only a directory name is specified in the "log" parameter and the "configuration_name" parameter is omitted, the log file name will have the following format:

xxxxxxxxx is an increasing decimal integer, starting from 000000000 to separate log files with the same time of creation (in case the log is being created faster than one log file per second).

• "overwrite" (default)
• "append"

Determines if the previous log information is maintained or overwritten.

This parameter is applicable only if the CHARON-AXP log is stored to a file that is specified explicitly with the "log" parameter.

Example:

• "all" (default)
• "info"
• "warning"
• "error"

Defines the message types to be shown. The parameter is a string of comma delimited words.

Example:

Specifies if repeated messages should be filtered or not. Possible values are "on" (default) and "off".

If the value is "on", immediately following messages with the same identifier and system error code are not listed in the log, but they are counted. When a different log message is generated, the repeat count of the earlier log message is reported with "The previous message has been repeated N times.", and the counter is cleared.

Example:

An integer (decimal Sentinel Key ID) that specifies the regular (N=0) and backup (N=1) license keys to be used by CHARON-AXP.

It is also possible to specify both regular and backup keys in one line:

Based on the presence of the regular and/or backup license key IDs in the configuration file, CHARON-AXP behaves as follows:
 

Overrides any initial process affinity mask provided by the host operating system. Once specified it binds the running instance of the emulator to particular host CPUs.

Used for soft partitioning of the host CPU resources and/or for isolating host CPUs for other applications.

By default the CHARON-AXP emulator instance allocates as many host CPUs as possible. The “affinity” parameter overrides that and allows explicit specification on which host CPU the instance must run on.

Host CPUs are enumerated as a comma separated list of host system assigned CPU numbers:

Limits the number of emulated CPUs.

Example:

The maximum number of CPUs enabled by CHARON-AXP is specified by the license key, but cannot exceed the original hardware restrictions:

This parameter specifies how many host CPUs CHARON-AXP must use for I/O handling. Use of the “affinity” parameter may limit the number of CPUs available.

By default the CHARON-AXP instance reserves one third of all available host CPUs for I/O processing (round down, at least one). The “n_of_io_cpus” parameter overrides that by specifying the number of CHARON I/O CPUs explicitly.

Example:

In case the CHARON-AXP license connection is not present when the guest starts up, this parameter specifies how many times CHARON-AXP will try to establish the connection and, optionally, a period of time between retries.

Syntax:

Options:

• N - Number of retries to look for license keys.
• T - Time between retries in seconds. If not specified 60 seconds are used
  

Examples:

1. Example 1

   set session license_key_lookup_retry = 1

   If license key is not found during initial scan, do only one more attempt after 60 seconds.

2. Example 2

   set session license_key_lookup_retry = "1,30"

   Same as above but retry in 30 seconds.

3. Example 3

   set session license_key_lookup_retry = "3,10"

   If license key is not found during initial scan, do 3 more attempts waiting 10 seconds between them.

4. Example 4

   set session license_key_lookup_retry = "5"

   If license key is not found during the initial scan, do 5 more attempts waiting 60 seconds between them.