| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
Table of Contents
| Table of Contents | ||
|---|---|---|
|
Creation of CHARON VM configuration
When a CHARON Virtual Machine (VM) is created from a template using the CHARON Virtual Machines Manager, it has to be updated to meet the desired configuration.
...
| Include Page | ||||
|---|---|---|---|---|
|
VAX/PDP11 model specification
The first configuration statement is the specification of the exact VAX/PDP11 hardware model to emulate, for example:
...
If you create the CHARON VM configuration file from scratch, it must be the very first uncommented line in the configuration file.
...
| Div | ||
|---|---|---|
| ||
Configuration name
The next configuration statement is the "Configuration name" option. If the virtual machine has been created using an existing template, the configuration name is defined in the configuration_name.icfg file otherwise it is defined directly in the configuration file using the "set session configuration_name = <...>" syntax:
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Log file parameters
The execution of a CHARON VM 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 problems with either the running CHARON VM or the emulated system configuration (such as the absence or malfunction of certain devices), the log file is the primary source to be analyzed for troubleshooting.
If it becomes necessary to contact Stromasys for support, the configuration and log files will be requested to begin the problem resolution.Here is an example of a CHARON VM log file:
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
...
| Div | |
|---|---|
| pagebreak |
The next group of parameters defines the name of the CHARON VM log file and how the CHARON VM will use it:
|
Rotating log (default)
By default the CHARON utilizes default CHARON utilizes a so-called "rotating log" methodmechanism. This means that a new default log file is always created each time the CHARON VM starts and can switch to another log file if the size of the log file exceeds 64Kb (previous log files are keptthis 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 a directory rather than to a file. If a directory is specified, the log files will be created in that directory.
...
If the path is not specified, the log file is created in the "Home directory" mentioned in the VM Configuration tab of the CHARON Virtual Machine Manager.
Single log
Alternatively it is possible to use a single log file. Uncomment the "set session log" line and specify the desired log file name. Optionally, a path can be added to the log file name.
...
| Include Page | ||||
|---|---|---|---|---|
|
TOY, ROM and EEPROM containers
The TOY, ROM and EEPROM containers have to be configured. Their presence depends on the VAX/PDP11 model. It is always recommended to enable them. If a container file of the given name does not exist, starting the CHARON VM will create it.
...
| Include Page | ||||
|---|---|---|---|---|
|
KW11 timer
PDP11/93 and PDP11/94 emulators require the KW11 system timer to be configured:
...
| Include Page | ||||
|---|---|---|---|---|
|
ACE mode
The next setting indicates whether the CHARON VM will use the Advanced CPU Emulation (ACE) mode:
...
| Include Page | ||||
|---|---|---|---|---|
|
Emulated memory (RAM) size
The next parameter defines the amount of host memory the CHARON VM reserves for the emulation:
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Console
Mapping to system resources
The next step is the specification of the VAX/PDP11 console (OPA0) serial line:
...
Note that additional parameters for the CHARON VM serial lines configuration can be added. Follow this link for details.
Exit on pressing F6 button
It is recommended to set a hot key to stop the VM from the console (when the console is accessed remotely for example):
...
| Include Page | ||||
|---|---|---|---|---|
|
Disk subsystem
The disk subsystem and the mapping to the system resources can be done using the samples given in the template configuration files.
...
The examples below are for MSCP and SCSI controllers only. DSSI controllers are discussed in details in the following section, CI controllers - in this section.
| Div | ||
|---|---|---|
| ||
MSCP disk controllers (RQDX3, KDB50, KDM70)
Below is a typical configuration sample for the MSCP disk controller RQDX3:
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
SCSI controller NCR53C94
The VAX 4000 and MicroVAX 3100 models have an NCR53C94 SCSI controller on board for the support of different types of SCSI devices including disks and tapes. Optionally a second controller can be added.
...
| Include Page | ||||
|---|---|---|---|---|
|
Tape subsystem
Some MSCP and SCSI controllers support tape devices. CHARON also emulates specific MSCP tape devices such as TQK50 and TUK50.
...
| Warning |
|---|
Using compressed folders to store virtual disks and tapes is not supported |
TQK50 controller
Example statements to configure a TQK50 controller 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:
...
| Include Page | ||||
|---|---|---|---|---|
|
Serial Lines
CHARON supports the following serial lines controllers: CXA16, CXB16, CXY08, DHQ11, DHV11, DZV11, DZQ11, DL11, DLV11, DZ11, DHW42-AA, DHW42-BA and DHW42-CA.
...
The first 5 lines above are example given for loading serial line controllers of different types. The name of the controller (in this example) will be "TXA".
| Div | ||
|---|---|---|
| ||
Once the controller is loaded it can be mapped to system resources (lines 6-11). The following options are available:
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Networking
CHARON supports DEQNA, DESQA, DELQA, DEUNA, DELUA, DEMNA, DEBNI and PMADAA virtual network adapters.
...
| Include Page | ||||
|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Auto boot
CHARON can be configured to automatically boot an operating system at start up.
...
| Include Page | ||||
|---|---|---|---|---|
|
Host load balance for SMP systems
The VAX 6620 through VAX6660 models emulate 2-6 CPUs respectively. In this situation, loading of the host system can be tuned with the following configuration file settings:
...