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.
Example:
|
Please do not edit the original template configuration files since they can be updated or even removed on update/deinstallation of CHARON-AXP
Once the file has been created you can open it in your favorite editing tool and proceed with 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 preceded by the comment sign "#" inside the configuration files will not be interpreted. You can use this sign to debug your configuration.
HP Alpha model specification
The first configuration statement is the specification of the exact HP Alpha hardware model to emulate.
Example:
|
You must leave this line untouched.
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.
Example:
|
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: Rotating log (default)).
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.
Here is an example of a field test CHARON-AXP log file:
|
The next group of parameters defines the name of the CHARON-AXP log file and how CHARON-AXP will use it:
|
Rotating log (default)
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).
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.
The names of the rotating log files are composed as follows:
|
If the "Configuration name" parameter described before is omitted (commented out), the log name has the following format instead:
|
Note that "xxxxxxxxx" is an increasing decimal number starting from "000000000" to separate log files with the same time of creation.
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.
The log file can be extended ("log_method = append") or overwritten ("log_method = overwrite") by CHARON-AXP.
Below is a specification of a CHARON-AXP log file located in the "/my_logs" directory which will be appended each time CHARON-AXP starts:
|
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.
“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:
|
The example above directs CHARON-AXP to use CPU 0,1,2 and 3.
If this parameter is omitted CHARON host will allocate available CPUs automatically.
Note that the number of the specified host CPUs must correspond to the number of the emulated CPUs (one host CPU for one emulated CPU; this value is specific for each HP Alpha model) and number of CPUs needed for CHARON application itself ("n_of_io_cpus").
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).
The “n_of_io_cpus” overrides the default by specifying the number of I/O host CPUs explicitly
Example:
|
The example above directs CHARON-AXP to use 2 CPUs for CHARON I/O operations.
Note that the number of the specified CPUs dedicated to CHARON I/O operations must correspond to the total number of available for CHARON CPUs (restricted by "affinity" parameter if needed) and the number of the virtual HP Alpha CPUs to be emulated.
Setting a specific HP Alpha model
CHARON-AXP allows to specify an exact model of HP Alpha.
For example for HP AlphaServer ES40 family the "es40.cfg" sample configuration file contains the following options:
|
Just uncomment the provided lines to apply a certain model (It is "AlphaServer ES40 6/667" in the example above).
The full description of the parameters, 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 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:
|
This parameter can also be used to avoid warning messages in the log if the number of CPUs allowed by the license is less than the default number of CPUs of the emulated HP Alpha model.
Setting system serial number
This parameter is used to set a specific system serial number instead of the default one:
|
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.
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 ROM container stores an intermediate state of the Flash ROM and some console parameters. It is highly recommended to define its location:
|
Emulated memory (RAM) size
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 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 |
It is possible to leave the RAM line commented out. In this case the model's default RAM amount is used.
Note that in some particular orders your license may restrict the maximum RAM amount of each HP Alpha model.
Console
Mapping to system resources
The next step is the specification of the HP Alpha console (OPA0) serial line.
Example:
|
The goal of this configuration step is to tell CHARON-AXP what host device to use as the virtual system console. The following options are available:
| Option | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| line | Mapping to host serial line, both physical and virtual. Use the following mapping for different types of host serial lines:
The specific account for running CHARON ("charon") does not allow the usage of physical consoles, " | ||||||||||
| port | Mapping to an IP port of the CHARON host. | ||||||||||
| application | Starting some application (typically another xterm terminal) with its specific options and switches to communicate to CHARON using the IP port defined by the "port" parameter (see above) | ||||||||||
| alias | Define some meaningful name for "COM1" and "COM2". Usually it is "OPA0" for "COM1" and "TTA0" for "COM2" (see below) |
The default setting for OPA0 is "line = (console)".
The second console line "TTA0" can be also optionally configured (for 1 CPU models such as HP AlphaServer 400, HP AlphaServer 800, HP AlphaServer 1000, HP AlphaServer 1000A, HP AlphaServer DS10, HP AlphaServer DS10L and HP AlphaServer DS15):
|
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:
set OPA0 stop_on = F6 |
This line provides CHARON-AXP the ability to exit by pressing the "F6" key.
Improve granularity of emulated timer
The next configuration option can be applied for improving granularity of emulated CHARON-AXP timer:
|
Do not uncomment this parameter unless there are some problems with system time or system clock intervals in guest OS.
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:
|
How to find proper "/dev/sg" device is explained in this section.
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:
|
The "Pulse Audio" packages of the last versions must be installed on CHARON host to support audio playback. Please refer to Linux documentation.
Networking
CHARON-AXP supports DE435, DE450, DE500AA, DE500BA, DE602 and DE602AA virtual network adapters.
All of them are configured in a similar way:
|
load DE602/i8255x EIA interface=EIA0load packet_port/chnetwrk EIA0 interface="eth0" |
In the examples above the first line loads DE500BA/DE602 virtual adapter with a name "EWA"/"EIA" (note that "/i8255x" syntax must be used only in case of DE602 and DE602AA adapters); the following line maps it to host network interface "eth0". Note that the mapping is performed in 2 steps:
- A mapping object "packet_port" with a name "EWA0"/"EIA0" is loaded and connected to host interface "eth0", so CHARON-AXP will use this interface for its networking
- The loaded DE500BA virtual adapter "EWA"/"EIA" is connected to the "packet_port" object "EWA0"/"EIA0"
It is possible to load several DE435, DE450, DE500AA, DE500BA or DE602 controllers, for example (for DE500BA):
|
Some network adapters available in CHARON-AXP are preloaded (for example, HP AlphaServer DS15 contains 2 preloaded adapters EWA and EWB), so their configuration is even more simple:
|
The AlphaServer DS15 and DS25 contain two built-in PCI Ethernet adapters. Models and names (EI* or EW*) of them depend on configuration addon. Choose one of the two or none, but not both. The first instantiates onboard network interfaces as EIA and EWA. While the second - EWA and EWB (enabled by default for backward compatibility)
Example:
#include ds25-onboard-nics.icfginclude ds25-onboard-nics-ew.icfg |
It could be necessary to specify the path to the .icfg file if you use your own configuration file using the "include /opt/charon/cfg/ds25-onboard-nics-ew.icfg" syntax.
Follow this link for more details of CHARON-AXP network controllers configuration.
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:
|
The first line ("load KZPBA PKA") loads disk controller KZPBA with name "PKA", followed by 8 group of lines showing different ways of mapping to the host resources:
| Type of mapping | Description |
|---|---|
| "<file-name>.vdisk" | Mapping to files representing physical disks of the HP Alpha system (disk images). |
| "/dev/sd<L>" | Mapping to physical disk. "L" is letter here. These disks must not be formatted by the host OS.
Since "/dev/sd<L>" addressing is not persistent, it is strongly recommended to use "/dev/disk/by-id/wwn-*" syntax instead to refer the disk by its WWID - especially in the enviroments utilizing FC and SAN storages (see below). |
"/dev/dm-<N>" | Mapping to multipath disk. Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake. These disks must not be formatted by the host OS. |
| "/dev/disk/by-*" | Mapping to physical disk.
These disks must not be formatted by the host OS. |
| "/dev/sg<N>" | Direct mapping to some SCSI device, for example, a SCSI disk or tape reader. How to find proper "/dev/sg" device is explained in this section. |
"/dev/sr<N>" | Mapping to host CD-ROM device. |
| "<file-name>.iso" | Mapping to an ISO file for reading distribution CD-ROM image. Mapping may also include the full path (recommended), for example: "/my_disks/vms_distributive.iso" |
| "<file-name>.vtape" | Mapping to the file representing the tape (tape image). These files are created automatically. Mapping may also include a full path (recommended), for example: "/my_tapes/backup.vtape" |
Additionally it is possible to specify a parameter "media_type" to assign the type of the attached media explicitly.
Example:
|
Numbers in the square brackets represent SCSI addresses and LUNs associated with each container of the KZBPA controller. They have the following structure:
[XXYY], where
| Parameter | Range | Description | |
|---|---|---|---|
| XX | 0...15 | Stands for SCSI ID of each connected unit.
In this example an instance "PKA" of KZPBA controller is assigned with SCSI ID 0. | |
| YY | 00...07 | Stands for LUN. |
It is possible to load several KZPBA controllers: DKB, DKC, etc. by configuring specific placement for them on the PCI bus. It is discussed in details in the "Configuration details" chapter of this Guide.
Some HP Alpha systems emulated by CHARON-AXP have already had one or two KZPBA controllers preloaded. If the system has only one preloaded controller, the template configuration file usually provides some sample line on how to add another one, for example:
load KZPBA PKA bus=pci_1 device=1 function=0 irq_bus=isa irq=24 |
Follow this link for details of KZPBA controllers configuration.
KGPSA-CA PCI FC disk controller
Optionally it is possible to configure KGPSA-CA FC disk controller.
It can be configured in 2 modes:
Below is an example of KGPSA-CA controller loading:
|
Optionally another KGPSA-CA adapter can be loaded similar way:
|
Follow this link for details of KGPSA-CA controllers configuration.
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):
|
The first line ("load KGPSA FGA") loads disk controller KGPSA with name "FGA", followed by 2 groups of lines showing different ways of mapping to the host resources:
| Type of mapping | Description |
|---|---|
| "<file-name>.vdisk" | Mapping to the file representing a physical disk of the HP Alpha system (disk image). These files can be created from scratch with "mkdskcmd" utility. Data and OS disk backups are transferred from the original system via tapes or network and restored into these container files. Mapping may also include the full path (recommended), for example: "/my_disks/my_boot_disk.vdisk" |
| "/dev/sd<L>" | Mapping to physical disk. "L" is letter here These disks must not be formatted by the host OS.
Since "/dev/sd<L>" addressing is not persistent, so it is strongly recommended to use "/dev/disk/by-id/wwn-*" syntax instead to refer the disk by its WWID - especially in the enviroments utilizing FC and SAN storages (see below). |
| "/dev/dm-<N>" "/dev/mapper/mpath<N>" "/dev/mapper/disk<N>" | Mapping to multipath disk. Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake. These disks must not be formatted by the host OS. |
| "/dev/disk/by-*" | Mapping to physical disk.
These disks must not be formatted by the host OS. |
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.
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.
The sample configuration file provides a template for this type of mapping:
|
Follow this link for detailed description of building and installation of an EMULEX LightPulse PCI/PCI-X/PCIe FC adapter driver.
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.
Example: dka0 is defined as the default boot device
|