Anchor
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.
Example:
...
$ cp /opt/charon/cfg/es40.cfg.template /my_charon_cfg/my_es40.cfg
$ chmod 644 /my_charon_cfg/my_es40.cfg
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:
...
set session hw_model = AlphaServer_ES40
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:
...
#set session configuration_name = My_ES40
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.
...
| class | pagebreak |
|---|
Here is an example of a field test CHARON-AXP log file:
...
| 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.
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.
| Include Page | ||||
|---|---|---|---|---|
|
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.
| Include Page | ||||
|---|---|---|---|---|
|
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: Rotatinglog(default) ).
| Include Page | ||||
|---|---|---|---|---|
|
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.
| Div | ||
|---|---|---|
| ||
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:
|
...
|
...
| 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.
...
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").
...
| Include Page | ||||
|---|---|---|---|---|
|
Number of host CPUs dedicated to CHARON I/O
...
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.
...
.
| Include Page | ||||
|---|---|---|---|---|
|
Setting a specific HP Alpha model
...
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.
...
| Include Page | ||||
|---|---|---|---|---|
|
Reducing number of emulated CPUs
If the CHARON host contains does not contain enough CPUs to emulate full range of the CPUs provided by a certain HP Alpha model, it is possibe 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.
| Include Page | ||||
|---|---|---|---|---|
|
Setting system serial number
...
|
...
| 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 | ||||
|---|---|---|---|---|
|
Emulated memory (RAM) size
...
Note that in some particular orders your license may restrict the maximum RAM amount of each HP Alpha model.
...
| Include Page | ||||
|---|---|---|---|---|
|
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 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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_lineport | Mapping to an IP port of the CHARON -VAX host. | ||||||||||||
| operator_console | Mapping to the current TTY console |
...
console and disconnect from it at any time. | |
| 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.
| Status | ||||
|---|---|---|---|---|
|
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 in addition to the system tray icon:
set OPA0 stop_on = F6 |
This line provides CHARON-AXP the ability to exit by pressing the "F6" button.
...
key.
| Include Page | ||||
|---|---|---|---|---|
|
Improve granularity of emulated timer
...
Do not uncomment this parameter unless there are some problems with system time or system clock intervals in guest OS.
...
| 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 " CD-ROM to the host CD/DVD-ROM with the following setting:
|
How to find proper "/dev/sg" device is explained in this section.
| 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:
|
How to find proper "/dev/sg" device is explained in this section.
...
|
| Note |
|---|
The "Pulse Audio" packages of the last versions must be installed on CHARON host to support audio playback. Please refer to Linux documentation. |
| Include Page | ||||
|---|---|---|---|---|
|
Networking
CHARON-AXP supports DE435, DE450, DE500AA, DE500BA, DE602 and DE602AA virtual network adapters.
...
It is possible to load several DE435, DE450, DE500AA, DE500BA or DE602 controllers, for example (for DE500BA):
...
(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:
|
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:
|
...
| Info |
|---|
| CHARON supports VLAN adapters. If used, proceed with their installation and configuration according to the network adapter vendor User's Guide and then use the resulting VLAN interface the same way as the regular network interface. |
| Note | |
|---|---|
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:
|
Follow this link for more details of CHARON-AXP network controllers configuration.
...
| 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.
...
|
...
| 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.
| ||
"/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 explined 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" |
...
|
| Div | ||
|---|---|---|
| ||
Numbers in the square brackets represent SCSI addresses and LUNs associated with each container of the KZBPA controller. They have the following structure:
...
| 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. |
...
load KZPBA PKA bus=pci_1 device=1 function=0 irq_bus=isa irq=24 |
Follow this link for details of KZPBA controllers configuration.
...
| Include Page | ||||
|---|---|---|---|---|
|
KGPSA-CA PCI FC disk controller
...
It can be configured in 2 modes:
Below is an example of KGPSA-CA controller loading:
...
Follow this link for details of KGPSA-CA controllers configuration.
...
KGPSA-CA controllers configuration.
Include Page KBCOMMON:DOC-GoToToc KBCOMMON:DOC-GoToToc
KGPSA-CA mapping to the host resources
...
|
| Div | ||
|---|---|---|
| ||
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:
...
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.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
KGPSA-CA pass through mode
...
Follow this link for detailed description of building and installation of of an EMULEX LightPulse PCI/PCI-X/PCIe FC adapter driver.
...
| 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.
...
|
...
| Include Page | ||||
|---|---|---|---|---|
|