| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
Table of Contents
| Table of Contents | ||
|---|---|---|
|
Creation of your own configuration file using a template
By default, all the CHARON templates are located in the "/opt/charon/cfg" folder. Copy the appropriate template configuration file(s) to your home directory or to any directory intended for CHARON-AXP, name them meaningfully and set proper privileges.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
HP Alpha model specification
The first configuration statement is the specification of the exact HP Alpha hardware model to emulate.
...
If you create the CHARON-AXP configuration file from scratch, it must be the very first uncommented line in the configuration file.
...
...
Configuration name
The next configuration statement is the "Configuration name" option.
...
You can optionally uncomment this line to differentiate this CHARON-AXP instance from all others in a multi-instances environment. The configuration name can be any label that is meaningful. It is reported in the log file and is used to set the log file name for rotating log (see further: RotatinglogRotating log (default) ).
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Log file parameters
Execution of CHARON-AXP creates one log file or a set of log files reflecting the progress of its start-up and ongoing operation - start and end time of execution, system information, license and configuration details, warnings, reports on problems that may occur, etc. In case of possible problems either with the running CHARON-AXP or the emulated system configuration (such as the absence or malfunction of certain devices), the log file(s) is the primary source to be analyzed for troubleshooting. If it becomes necessary to contact Stromasys for support, the configuration and log files, plus the license number, will be requested to begin problem resolution.
...
| class | pagebreak |
|---|
Here is an example of a field test
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| |
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
| Div | ||
|---|---|---|
| ||
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
The next group of parameters defines the name of the CHARON-AXP log file and how CHARON-AXP will use it:
|
| Div | ||
|---|---|---|
| ||
| Anchor | ||||
|---|---|---|---|---|
|
By default CHARON-AXP utilizes a so-called "rotating log" mechanism. This means that a new default log file is created each time CHARON starts and can switch to another log file if the size of the log file exceeds 64Kb (this behavior can be changed with the "set session log_file_size" and "set session log_rotation_period" parameters; see more details in the "General Settings" chapter of this guide).
...
| Note |
|---|
Only an existing directory can be used as a value of the "log" parameter. |
Single log
Alternatively it is possible to use a single log file: uncomment the "set session log" line and specify the desired CHARON-AXP log file name. Optionally, a path can be added to the log file name. If the path is not specified, the log file is created in the directory from where the guest (emulated machine) is started.
...
| Include Page | ||||
|---|---|---|---|---|
|
CPU affinity
This setting binds the running instance of the emulator CPUs to particular host CPUs. This should be used for soft partitioning host CPU resources or for isolating multiple CHARON instances on the same host from each other. By default the emulator instance allocates as many host CPUs as possible.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Number of host CPUs dedicated to CHARON I/O
This setting reserves host CPUs (of those specified by “affinity” parameter, if any) for use by the emulator for I/O handling. By default the emulator instance reserves one third of available host CPUs for I/O processing (round down, at least one).
...
| Include Page | ||||
|---|---|---|---|---|
|
Setting a specific HP Alpha model
CHARON-AXP allows to specify an exact model of HP Alpha.
...
| Include Page | ||||
|---|---|---|---|---|
|
Reducing number of emulated CPUs
If the CHARON host does not contain enough CPUs to emulate full range of the CPUs provided by a certain HP Alpha model, it is possible to direct CHARON-AXP to reduce the number of emulated Alpha CPUs in the configuration:
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Setting system serial number
This parameter is used to set a specific system serial number instead of the default one:
...
| Include Page | ||||
|---|---|---|---|---|
|
TOY and ROM containers
The next objects to be configured are TOY and ROM containers (their presence depends on the HP Alpha model). It is always recommended to enable them. If a container file of the given name does not exist, CHARON-AXP will create it. It is recommended to specify the path for each file so that time and console parameters will be kept whatever the current directory is when starting the guest.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Emulated memory (RAM) size
The next parameter defines the amount of host memory the chosen CHARON-AXP model reserves for the emulation.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Console
Mapping to system resources
The next step is the specification of the HP Alpha console (OPA0) serial line.
...
Note there are a number of additional parameters for CHARON-AXP serial lines configuration. Follow this link for details.
Exit on pressing F6 key
Despite the fact that CHARON-AXP can exit with "power off" command given in its SRM console it is also recommended to set a hot key to stop the guest from the console:
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Improve granularity of emulated timer
The next configuration option can be applied for improving granularity of emulated CHARON-AXP timer:
...
| Include Page | ||||
|---|---|---|---|---|
|
ATAPI CD/DVD-ROM configuration
If the sample configuration file provides this parameter, it is possible to map this particular CHARON-AXP emulator's "DQA0" CD-ROM to the host CD/DVD-ROM with the following setting:
...
| Include Page | ||||
|---|---|---|---|---|
|
AlphaStation Sound Card (AD1848) configuration
If the sample configuration file provides this parameter, it is possible to load "PCXBJ" emulator of AlphaStation Sound Card (AD1848) with the following setting:
...
| Include Page | ||||
|---|---|---|---|---|
|
Networking
CHARON-AXP supports DE435, DE450, DE500AA, DE500BA, DE602 and DE602AA virtual network adapters.
...
| Include Page | ||||
|---|---|---|---|---|
|
Disk/tape subsystem
The next step is configuration of the disk/tape subsystem and mapping it to system resources using the samples given in the template configuration files.
CHARON-AXP supports KZPBA and KGPSA-CA adapters.
KZPBA PCI SCSI disk/tape controller
Below is the typical configuration options for KZPBA PCI SCSI disk/tape controller:
...
| Include Page | ||||
|---|---|---|---|---|
|
KGPSA-CA PCI FC disk controller
Optionally it is possible to configure KGPSA-CA FC disk controller.
...
Follow this link for details of KGPSA-CA controllers configuration.
Include Page KBCOMMON:DOC-GoToToc KBCOMMON:DOC-GoToToc
KGPSA-CA mapping to the host resources
Below is the typical configuration options for KGPSA-CA PCI FC disk controller, mapped to the host resources ("L" is letter here):
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
KGPSA-CA pass through mode
It is also possible to use the emulated KGPSA-CA in "pass through" mode to address a physical EMULEX LightPulse PCI/PCI-X/PCIe FC adapter plugged into the host’s PCI/PCI-X/PCIe slot.
...
| Include Page | ||||
|---|---|---|---|---|
|
Auto boot
CHARON-AXP can be configured to automatically boot an operating system at start up by specifying the default boot device and setting the 'auto_action' parameter to 'restart' from the console.
...