CHARON-VAX for Linux configuration
Table of Contents
- 1 Creation of your own configuration file using a template
- 2 VAX model specification
- 3 Configuration name
- 4 Log file parameters
- 4.1 Rotating log (default)
- 4.2 Single log
- 5 TOY, ROM and EEPROM containers
- 6 Emulated memory (RAM) size
- 7 Console
- 8 Disk subsystem
- 9 Tape subsystem
- 9.1 TQK50 controller
- 9.2 TUK50 controller
- 10 Serial Lines
- 11 Networking
- 12 Auto boot
- 13 Host load balance for SMP systems
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.
Example:
|
Please do not edit the original template configuration files since they can be updated or even removed on update/deinstallation of CHARON-VAX
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.
VAX model specification
The first configuration statement is the specification of the exact VAX hardware model to emulate.
Example:
|
You must leave this line untouched.
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.
Example:
|
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: Rotatinglog(default) ).
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 CHARON-VAX log file:
|
The next group of parameters defines the name of the CHARON-VAX log file and how CHARON-VAX will use it:
|
Rotating log (default)
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).
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-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.
The log file can be extended ("log_method = append") or overwritten ("log_method = overwrite") by CHARON-VAX.
Below is a specification of a CHARON-VAX log file located in the "/my_logs" directory which will be appended each time CHARON-VAX starts:
|
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.
TOY means "Time of Year"; its container records time, date and some console parameters while CHARON-VAX 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:
|
EEPROM stores the NVRAM content. It is highly recommended to define its location:
|
Emulated memory (RAM) size
The next parameter defines the amount of host memory the chosen CHARON-VAX model reserves for the emulation.
Example:
|
The amount of RAM is specified in MB. It cannot exceed or be lower than certain values specific for each VAX 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 |
MicroVAX_II | 1 | 16 | 16 | 1,8,16 |
MicroVAX_3600 | 16 | 64 | 16 | 16 |
MicroVAX_3900 | 16 | 64 | 16 | 16 |
VAXserver_3600 | 16 | 64 | 16 | 16 |
VAXserver_3900 | 16 | 64 | 16 | 16 |
VAXserver_3600_128 | 32 | 128 | 32 | 32 |
VAXserver_3900_128 | 32 | 128 | 32 | 32 |
MicroVAX_3100_Model_96 | 16 | 128 | 16 | 16 |
VAXstation_4000_Model_90 | 16 | 128 | 16 | 16 |
VAX_4000_Model_106 | 16 | 128 | 16 | 16 |
VAX_6000_Model_310 | 32 | 512 | 32 | 32 |
VAXserver_3600_512 | 32 | 512 | 32 | 32 |
VAXserver_3900_512 | 32 | 512 | 32 | 32 |
MicroVAX_3100_Model_98 | 16 | 512 | 16 | 16 |
VAX_4000_Model_108 | 16 | 512 | 16 | 16 |
VAX_4000_Model_700 | 64 | 512 | 64 | 64 |
VAX_4000_Model_705 | 64 | 512 | 64 | 64 |
VAX_6610 | 128 | 3584 | 128 | 128 |
VAX_6620 | 128 | 3584 | 128 | 128 |
VAX_6630 | 128 | 3584 | 128 | 128 |
VAX_6640 | 128 | 3584 | 128 | 128 |
VAX_6650 | 128 | 3584 | 128 | 128 |
VAX_6660 | 128 | 3584 | 128 | 128 |
It is possible to leave the RAM line commented out. In this case the model's default RAM amount is used.
Console
Mapping to system resources
The next step is the specification of the VAX console (OPA0) serial line.
Example:
|
The goal of this configuration step is to tell CHARON-VAX 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:
The specific account for running CHARON ("charon") does not allow the usage of physical consoles, " | ||||||||
virtual_serial_line | Mapping to an IP port of CHARON-VAX host. | ||||||||
operator_console | Mapping to the current TTY console |
The default setting is "operator_console".
Note that the VAX 4000 and MicroVAX 3100 models have a 4-line QUART adapter onboard so their configuration for the console line looks a bit different:
|
IF VAX 4000 and MicroVAX 3100 models are used, it is possible to configure up to 4 independent console lines: OPA0, TT0, TT1 and TT2. The main one is OPA0.
Note there are a number of additional parameters for CHARON-VAX serial line configuration. Follow this link for details.
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.
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:
|
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:
Type of mapping | Description |
|---|---|
"<file-name>.vdisk" | Mapping to files representing physical disks of the VAX system (disk images). |
"/dev/sd<L>" | Mapping to physical disks. "L" is letter here. Be careful not to destroy all the information from the disk dedicated to CHARON-VAX by mistake! These disks can not be formatted by the host OS. It is also possible to use not a whole disk, but previously created partitions on it. In this case the syntax is the following: "/dev/sd<L><N>" where N is the number of partition to be used. 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>" | Mapping to multipath disk. Be careful not to destroy all the information from the disk dedicated to CHARON-VAX by mistake. These disks must not be formatted by the host OS. |
"/dev/disk/by-*" | Mapping to physical disk.
Be careful not to destroy all the information from the disk dedicated to CHARON-VAX by mistake. These disks must not be formatted by the host OS. |
"/dev/sr<N>" | Mapping to CD-ROMs. There are some variants of this mapping: "/dev/cdrom<N>" or "/dev/cdrom" |
"<file-name>.iso" | Mapping to an ISO file for reading distribution CD-ROM images. |
The numbers in the square brackets represent unit numbers associated with each container of the MSCP controller. For example, the line of the configuration sample above, referring container #2, creates the "DUA2" disk. The maximum unit number allowed is 9999, significantly more than the original hardware provided.
It is possible to load several RQDX3 controllers DUB, DUC, etc. (see lines 6-7, above) 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.
Please also refer to the HP documentation for information on placement of additional KDM70 controllers on an XMI bus (VAX 6000 models) and additional KDB50 controllers on a BI bus (VAX 6310).
Note that the KDM70 controller is capable of mapping to files representing tapes (tape images) and physical tape devices:
|
Follow this link for details of (T)MSCP controllers configuration.
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.
Below is a typical configuration template for a preloaded "PKA" NCR53C94 SCSI controller:
|