| Anchor | TopConfigurationPage | TopConfigurationPage|||
|---|---|---|---|---|
| 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-VAX, name them meaningfully and set proper privileges.
...
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 | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
VAX model specification
The first configuration statement is the specification of the exact VAX hardware model to emulate.
...
If you create the CHARON-VAX 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-VAX 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) ).
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Log file parameters
Execution of CHARON-VAX 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-VAX 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
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| |
|
...
|
...
|
...
|
...
|
...
|
...
|
...
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
| Div | ||
|---|---|---|
| ||
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
The next group of parameters defines the name of the CHARON-VAX log file and how CHARON-VAX will use it:
|
| Div | ||
|---|---|---|
| ||
| Anchor | ||||
|---|---|---|---|---|
|
By default CHARON-VAX 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-VAX 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 | ||||
|---|---|---|---|---|
|
TOY, ROM and EEPROM containers
The next objects to be configured are TOY, ROM and EEPROM containers (their presence depends on the VAX model). It is always recommended to enable them. If a container file of the given name does not exist, CHARON-VAX will create it. Specific paths can be added to the file name specification.
...
|
...
| Div | ||
|---|---|---|
| ||
Emulated memory (RAM) size
The next parameter defines the amount of host memory the chosen CHARON-VAX model reserves for the emulation.
...
It is possible to leave the RAM line commented out. In this case the model's default RAM amount is used.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Console
Mapping to system resources
The next step is the specification of the VAX console (OPA0) serial line.
...
Note there are a number of additional parameters for CHARON-VAX serial line configuration. Follow this link for details.
| Div | ||
|---|---|---|
| ||
Exit on pressing F6 key
A hot key can be defined to stop the execution of the CHARON-VAX virtual machine:
...
It is strongly recommended to uncomment this line to provide CHARON-VAX the ability to exit by pressing the "F6" key.
...
| Include Page | ||||
|---|---|---|---|---|
|
Disk subsystem
The next step is the configuration of the disk subsystem and mapping it to the system resources using the samples given in the template configuration files.
CHARON-VAX supports MSCP, DSSI, CI and SCSI disk controllers. The examples below are for MSCP and SCSI controllers only. DSSI controllers are discussed in details in the following section and CI controllers in this section.
MSCP disk controllers (RQDX3, KDB50, KDM70)
Below is a typical configuration sample for MSCP disk controller RQDX3:
|
| Div | ||
|---|---|---|
| ||
The first line ("load RQDX3 DUA") loads disk controller RQDX3 with name DUA, followed by 4 lines showing different ways of mapping to the host resources:
...
Follow this link for details of (T)MSCP controllers configuration.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
SCSI controller NCR53C94
The VAX 4000 and MicroVAX 3100 have an NCR53C94 SCSI controller onboard for support of different types of SCSI devices including disks and tapes. Optionally a second controller can be added.
...
Note that versions of VAX/VMS older than 5.5-2H4 do not support the optional SCSI controller and might fail to boot if it is loaded.
Follow this link for details of NCR53C94 SCSI controller controllers configuration.
...
| Include Page | ||||
|---|---|---|---|---|
|
Tape subsystem
Some MSCP and SCSI controllers support tape devices, however CHARON-VAX also emulates specific MSCP tape devices such as TQK50 and TUK50.
Follow this link for more details of (T)MSCP controllers configuration.
TQK50 controller
Example statements to configure TQK50 are shown below:
...
It is possible to load several TQK50 controllers (see the lines 4-5) by configuring specific addresses for them on the Qbus. Use the "CONFIGURE" utility available on the VAX console to determine the addresses. Please refer to specific HP documentation for further information.
TUK50 controller
TUK50 is a UNIBUS controller used by the VAX 6310:
...
The first line loads a UNIBUS BI adapter "DWBUA". Configure then the "TUK50" tape controller the same way as the TQK50.
...
the TQK50.
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Serial Lines
CHARON-VAX supports the following serial lines controllers: CXA16, CXB16, CXY08, DHQ11, DHV11, DZV11, DZQ11, DL11, DLV11, DZ11, DHW42-AA, DHW42-BA and DHW42-CA.
...
Note that additional parameters exist for CHARON-VAX serial lines configuration, follow this link for details.
...
| Include Page | ||||
|---|---|---|---|---|
|
Networking
CHARON-VAX supports DEQNA, DESQA, DELQA, DEUNA, DELUA, DEMNA, DEBNI and PMADAA virtual network adapters.
...
| 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. |
Follow this link for more details of CHARON-VAX network controllers configuration.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Auto boot
CHARON-VAX can be configured to automatically boot an operating system at start up.
...
The CHARON-VAX 6000 models have a similar configuration setting:
|
...
| Include Page | ||||
|---|---|---|---|---|
|
Host load balance for SMP systems
The VAX 6620 through VAX 6660 models emulate 2-6 CPUs respectively. In this situation, loading of the host system can be tuned with the following configuration file settings:
| Setting | Description | Example | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 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. |
| ||||||||
| n_of_io_cpus | 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. |
|
...
| Include Page | ||||
|---|---|---|---|---|
|