General Settings
Table of Contents
Session
General settings that control the execution of CHARON Virtual Machine (VM) belong to an object called the "session". It is a preloaded object; therefore, only "set" commands are necessary.
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 this section to find how to set a particular HP Alpha model supported by CHARON-AXP. |
configuration_name
Parameter | configuration_name | ||
---|---|---|---|
Type | Text string | ||
Value | Name of the CHARON VM (it must be unique):
In provided templates this parameter is specified in the included configuration file "configuration_name.icfg". The value of this parameter is used as a prefix to the event log file name (see below). From the example above, the CHARON VM 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 VM runs on the same server. |
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. Log specified as a file name It is possible to overwrite the existing log file or to extend it using the "log_method" parameter. The "log_method" parameter is effective only when a single log file is specified, not a directory. Example:
Log specified as a directory 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. In these two cases, the log rotation mode is enabled, meaning a new log file is created each time the virtual machine is started and when the log file size exceeds the one specified (see log_file_size) and/or when the log file is older than a specified number of days (see log_rotation_period). A shortcut located in the same directory will be created, pointing to the active log file. Its name is based on the hw_model parameter or the configuration_name parameter if specified. If the "configuration_name" parameter of the sessionis specified, the log file name is composed as follows:
If the "configuration_name" parameter is omitted, the log file name will have the following format:
where " Only existing directory can be specified. If the directory specified does not exist, this will be considered as a flat file. No trailing backslash character is allowed. Example:
The execution of the virtual machine will create a log file, named |
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 the “log” parameter on the same line. This parameter is applicable only if the CHARON VM 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_file_size
Parameter | log_file_size | ||
---|---|---|---|
Type | Text string | ||
Value | If log rotation is enabled, the log_file_size parameter determines the log file size threshold at which the log is automatically rotated. Rotating log file size is multiple of 64K
Examples:
Minimum LOG File size is 64K, maximum is 1G. Setting a size less than 64K effectively makes the log file size unlimited. |
log_rotation_period
Parameter | log_rotation_period | ||
---|---|---|---|
Type | Text string | ||
Value |
If the rotation log mode is enabled, this parameter controls switching to the next log file based on a period of time. If enabled, the switching to the next log file occurs at midnight Examples:
|
log_repeat_filter
Parameter | log_repeat_filter | |
---|---|---|
Type | Text string | |
Value | Specifies if repeated messages should be filtered or not. Possible values are "on" and "off" (default). 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 entry "The previous message has been repeated N times." and the counter is cleared. Stromasys highly recommends to let this value to "off" otherwise important information will not be reported in the log file. Example:
|
license_key_id
Parameter | license_key_id | |
---|---|---|
Type | Text string | |
Value | A set of Sentinel Key IDs that specifies the license keys to be used by CHARON. It is also possibly to use a keyword "any" to force CHARON to look for a suitable license in all available keys if the license is not found in the specified keys. Example:
Based on the presence of this parameter in the configuration file, CHARON behaves as follows:
If the keyword "any" is specified then if no valid license has been found in the keys with specified ID’s all other available keys are examined for valid license as well. The order in which keys are specified is very important. If a valid license was found in the key which ID was not the first one specified in configuration file, then available keys are periodically re-scanned and if the key with the ID earlier in the list than the current one is found CHARON tries to find a valid license there and in case of success switches to that key. |
license_id
Parameter | license_id | |
---|---|---|
Type | Text string | |
Value | A set of license identifiers that specifies the licenses to be used by CHARON. This parameter is applicable only to licenses on which Stromasys placed restrictions on what products can be combined on a single license key. Please contact your Stromasys representative or VAR for more information. Example:
If this parameter is set, Charon considers for validation only the available licenses with license ID parameter set and equal to one of the license ID's specified in the configuration. This prioritized list corresponds to the "Product License Number" line in the Product section of the license. |
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. |
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 VM 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 the CHARON VM itself (including the CPUs to be used for I/O - they are controlled by the "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 VM is specified by the license key. It 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 VM must use for I/O handling. Use of the “affinity” parameter may limit the number of CPUs available. By default the CHARON VM 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:
|
File inclusion
It is possible to include a configuration file into an existing one using the "include
" command. The file extension is usually .icfg
.
Format:
include "file.icfg" |
Example:
include "c:\charon\commonpart.icfg" |
The configuration template files are defined to use the "configuration_name.icfg" configuration file which is used by the CHARON Virtual Machines Manager. If you use an existing configuration file, including this file is not necessary.
© 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.