General Settings
- Copy Page Tree
- Bruno Miretti (Deactivated)
- Kirill Nikolaev (Unlicensed)
Session
General settings that control the execution of CHARON-AXP belong to an object called the "session". It is a preloaded object; therefore, only "set" commands apply.
Example:
|
The following table describes all available "session" parameters, their meaning and examples of their usage:
hw_model
| Parameter | hw_model | |
|---|---|---|
| Type | Text string | |
| 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:
Available models are:
|
Refer to configuration_name
| Parameter | configuration_name | ||
|---|---|---|---|
| Type | Text string | ||
| Value | 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 "log
| Parameter | log | ||||
|---|---|---|---|---|---|
| Type | Text string | ||||
| Value | 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. 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). Only existing directory can be used as a value of the "log" parameter. |
log_method
| Parameter | log_method | |
|---|---|---|
| Type | Text string | |
| Value |
Determines if the previous log information is maintained or overwritten. This parameter must be specified only in addition to “log” parameter on the same line. This parameter is applicable only if the CHARON-AXP log is stored to a file that is specified explicitly with the "log" parameter. Example:
|
log_show_messages
| Parameter | log_show_messages | |
|---|---|---|
| Type | Text string | |
| Value |
Defines the message types to be shown. The parameter is a string of comma delimited words. Example:
|
log_repeat_filter
| Parameter | log_repeat_filter | |
|---|---|---|
| Type | Text string | |
| Value | 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:
|
license_key_id
| Parameter | license_key_id[N] N=0 or 1 | ||
|---|---|---|---|
| Type | Numeric | ||
| Value | 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:
|
affinity
| Parameter | affinity | |
|---|---|---|
| Type | Text string | |
| Value | 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. The "affinity" parameter defines the total number of host CPUs to be used both for emulated Alpha CPUs and for CHARON-AXP application itself (including the CPUs to be used for I/O - they are controlled by "n_of_io_cpus" parameter described below). Host CPUs are enumerated as a comma separated list of host system assigned CPU numbers:
|
n_of_cpus
| Parameter | n_of_cpus | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Type | Numeric | |||||||||||||||||||||||||||||||||||||||
| Value | 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:
|
n_of_io_cpus
| Parameter | n_of_io_cpus | |
|---|---|---|
| Type | Numeric | |
| Value | 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:
|
license_key_lookup_retry
| Parameter | license_key_lookup_retry | |||||
|---|---|---|---|---|---|---|
| Type | Text String | |||||
| Value | 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:
Example 1:
If license key is not found during initial scan, do only one more attempt after 60 seconds. Example 2:
Same as above but retry in 30 seconds. Example 3:
If license key is not found during initial scan, do 3 more attempts waiting 10 seconds between them. Example 4:
If license key is not found during the initial scan, do 5 more attempts waiting 60 seconds between them. |
© Stromasys, 1999-2024 - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.