| Anchor | ||||
|---|---|---|---|---|
|
...
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 , name them meaningfully and set proper privileges.
...
Once the file has been created you can open it in your favorite editing tool and proceed with modification modifications to reflect the exact features of the system you are going to emulate.
We will review all the parameters step by step issuing some recommendations and guidelines.
Note: the lines preceeded preceded by the comment sign "#" inside the configuration files will not be interpreted. You can use this sign to debug your configuration.
...
The first configuration statement is the specification of the exact HP Alpha hardware model to emulate, for example.
Example:
|
...
If you create the CHARON-AXP configuration file from scratch, it must be the very first uncommented line in the configuration file.
...
The next configuration statement is the "Configuration name" option.
Example:
|
You can optionally uncomment this line to differentiate this CHARON-AXP instance from all others in a multi-instance instances environment. The configuration name can be any label that is meaningful. The configuration name It is reported in the log file and is used to set the log file name for rotating log (see further: Rotating log (default) ).
...
By default CHARON-AXP utilizes a so-called "rotating log" mechanism. This means that a new default log file is always created each time CHARON starts and can switch to another log file if the size of the log file exceeds 64Kb (This this behavior can be changed with the "set session log_file_size" and "set session log_rotation_period" commandsparameters; see more details in the "General Settings" chapter of this guide).
This mode is turned on if all the log parameters above are disabled (commented out) or the "session_log" parameter is pointing to an existing directory rather than to a file. If a directory is specified, the log files will be created in that directory.
Names The names of the rotating log files are composed as follows:
...
Note that "xxxxxxxxx" is an increasing decimal number starting from "000000000" to separate log files with the same time of creation.
| Note |
|---|
Only an existing directory can be used as a value of the "log" parameter. |
...
Alternatively it is possible to use just a single log file. Uncomment : 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.
...
Below is a specification of a CHARON-AXP log file located in the "/my_logs" directory which will be overwritten appended each time CHARON-AXP starts:
...
“Affinity” overrides the default and allows explicit specification of which host CPUs will be used by the instance. Affinity does not reserve the CPU for exclusive use.
Example:
|
...
Just uncomment the provided lines to apply a certain model (It is "AlphaServer ES40 6/667" in the example above).
Full The full description of the parameters and , with other models that can be also configured, is available in the "Configuration details" chapter of this User's Guide.
...
Reducing number of emulated CPUs
If the CHARON host contains not enough CPUs to emulate full range of the CPUs provided by a certain HP Alpha model, it is possibe to direct CHARON-AXP to reduce the number of the emulated Alpha CPUs in the configuration:
...
Setting system serial number
The next configuration option that can be applied is setting This parameter is used to set a specific system serial number instead of the default one:
...
TOY means "Time of Year"; its container records time, date and some console parameters while CHARON-AXP is not running. To enable the TOY, uncomment the following line:
...
The next parameter defines the amount of host memory the chosen CHARON-AXP model reserves for the emulation.
Example:
#set ram size=4096 |
The amount of RAM is specified in MB. It cannot exceed or be lower than certain values specific for each HP Alpha model. It is very important to keep the listed predefined increment between possible memory values.
The following table shows lists all the parameters per model:
| Hardware Model | RAM size (in MB) | |||
| Min | Max | Default | Increment | |
| AlphaServer 400 | 64 | 1024 | 512 | 64 |
| AlphaServer 800 | 256 | 8192 | 512 | 256 |
| AlphaServer 1000 | 256 | 1024 | 512 | 256 |
| AlphaServer 1000A | 256 | 1024 | 512 | 256 |
| AlphaServer 1200 | 256 | 32768 | 512 | 256 |
| AlphaServer 2000 | 64 | 2048 | 512 | 64 |
| AlphaServer 2100 | 64 | 2048 | 512 | 64 |
AlphaServer 4000 | 64 | 32768 | 512 | 64 |
| AlphaServer 4100 | 64 | 32768 | 512 | 64 |
| AlphaServer DS10 | 64 | 32768 | 512 | 64 |
| AlphaServer DS10L | 64 | 32768 | 512 | 64 |
| AlphaServer DS15 | 64 | 32768 | 512 | 64 |
| AlphaServer DS20 | 64 | 32768 | 512 | 64 |
| AlphaServer DS25 | 64 | 32768 | 512 | 64 |
| AlphaServer ES40 | 64 | 32768 | 512 | 64 |
| AlphaServer ES45 | 64 | 32768 | 512 | 64 |
| AlphaServer GS80 | 256 | 65536 | 512 | 256 |
| AlphaServer GS160 | 512 | 131072 | 512 | 512 |
| AlphaServer GS320 | 1024 | 262144 | 1024 | 1024 |
...
The next step is the specification of the HP Alpha console (OPA0) serial line.
Example:
|
...
| Option | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| physical_serial_line | Mapping to host serial line, both physical and virtual. Use the following mapping for different types of host serial lines:
| ||||||||||
| virtual_serial_line | Mapping to an IP port of the CHARON-VAX host. | ||||||||||
| operator_console | Mapping to the current TTY console |
...
Note there are a number of additional parameters for CHARON-AXP serial lines configuration. Follow this link for details.
| Status | ||||
|---|---|---|---|---|
|
Exit on pressing F6 button
...
Follow this link for details of KZPBA controllers configuration.
Back to Table of Contents
KGPSA-CA PCI FC disk controller
...
Follow this link for details of KGPSA-CA controllers configuration.
Back to Table of Contents
KGPSA-CA mapping to the host resources
...
Numbers in the square brackets represent KGPSA-CA units. They can be in the range 0..32766, but no more than 255 units can be configured on a single controller.
Back to Table of Contents
KGPSA-CA pass through mode
...
Follow this link for detailed description of building and installation of EMULEX LightPulse PCI/PCI-X/PCIe FC adapter driver.
Back to Table of Contents
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.
...