| 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.
...
| 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.
| Code Block | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| language | text | theme | Confluence||||||||
| Panel | ||||||||||
| ||||||||||
|
| Div | ||
|---|---|---|
| ||
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
TEST WITH PANEL
| Panel |
|---|
20190523:074333:INFO :0:000003A5:hexane.cxx(5952): session: loading built-in configuration "VAX_6610"... |
The next group of parameters defines the name of the CHARON-VAX log file and how CHARON-VAX will use it:
...
set session log_method = append#set session log_method = overwrite#set session log = "MicroVAX_3600.log"
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:
...
configuration_name-YYYY-MM-DD-hh-mm-ss-xxxxxxxxx.log
If the "Configuration name" parameter described before is omitted (commented out), the log name has the following format instead:
...
hw_model-YYYY-MM-DD-hh-mm-ss-xxxxxxxxx.log
Note that "xxxxxxxxx" is an increasing decimal number starting from "000000000" to separate log files with the same time of creation.
| 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.
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:
...
set session log_method = appendset session log = "/my_logs/my_vax.log"
...
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:
...
set toy container="charon.dat"
The ROM container stores an intermediate state of the Flash ROM and some console parameters. It is highly recommended to define its location:
...
set rom container="vx4k106.rom"
EEPROM stores the NVRAM content. It is highly recommended to define its location:
...
set eeprom container="charon.rom"
...
Emulated memory (RAM) size
The next parameter defines the amount of host memory the chosen CHARON-VAX model reserves for the emulation.
Example:
...
set ram size=64
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.
...
| Div | ||
|---|---|---|
| ||
20190523:074333:INFO :0:000003A5:hexane.cxx(5952): session: loading built-in configuration "VAX_6610"... 20190523:074333:INFO :0:000003A6:hexane.cxx(5973): session: ... done loading built-in configuration "VAX_6610" 20190523:074333:INFO :0:000003AA:hexane.cxx(6002): session: loading configuration file "vx6k610.cfg"... 20190523:074333:INFO :0:000003AB:hexane.cxx(6026): session: ... done loading configuration file "vx6k610.cfg" 20190523:074333:INFO :0:000003F2:sesmgr.cxx(1419): session: default log file size limit is 4194304 bytes 20190523:074333:INFO :0:0000032B:hexane.cxx(2698): Start request received. 20190523:074334:INFO :0:000003AC:hexane.cxx(1424): session: process affinity is 000000000000000F, system affinity is 000000000000000F 20190523:074334:INFO :0:000003D1:hexane.cxx(1686): session: I/O domain affinity is 0000000000000001, CPU domain affinity is 000000000000000E 20190523:074334:INFO :0:0000024D:licenseman(1823): Checking the available license key "1422726238". 20190523:074334:INFO :0:0000024D:licenseman(1823): Found license key: "1422726238". 20190523:074334:INFO :0:0000024D:licenseman(1823): Checking product section 0. 20190523:074334:INFO :0:0000024D:licenseman(1823): The value "VAX_6610" of the required parameter "P_HW" is not found in the list "AlphaServer_400,AlphaServer_800,AlphaServer_1000,AlphaServer_1000A,AlphaServer_1200,AlphaServer_2000,AlphaServer_2100,AlphaServer_4000,AlphaServer_4100" for the product 0. 20190523:074334:INFO :0:0000024D:licenseman(1823): Checking product section 1. 20190523:074334:INFO :0:0000024D:licenseman(1823): The value "VAX_6610" of the required parameter "P_HW" is not found in the list "AlphaServer_DS10,AlphaServer_DS10L,AlphaServer_DS15,AlphaServer_DS20,AlphaServer_DS25,AlphaServer_ES40,AlphaServer_ES45,AlphaServer_GS80,AlphaServer_GS160,AlphaServer_GS320" for the product 1. 20190523:074334:INFO :0:0000024D:licenseman(1823): Checking product section 2. 20190523:074334:INFO :0:0000024D:licenseman(1823): The value "VAX_6610" of the required parameter "P_HW" is not found in the list "PDP1193,PDP1194" for the product 2. 20190523:074334:INFO :0:0000024D:licenseman(1823): Checking product section 3. 20190523:074334:INFO :0:0000024D:licenseman(1823): HASP clock: 23-May-2019 08:47:05. 20190523:074334:INFO :0:0000024D:licenseman(1823): Host clock: 23-May-2019 07:43:34. 20190523:074334:INFO :0:0000024D:licenseman(1823): License number: "003.msc.test.center.kirill". 20190523:074334:INFO :0:0000024D:licenseman(1823): Product License number: "p.vax". 20190523:074334:INFO :0:0000024D:licenseman(1823): CHARON product code: "CHVAX-4110xx-WI-LI". 20190523:074334:INFO :0:0000024D:licenseman(1823): Unlimited license. 20190523:074334:INFO :0:0000024D:licenseman(1823): Feature 1 check interval 1 hour(s). 20190523:074334:INFO :0:0000024D:licenseman(1823): Concurrency info: 20190523:074334:INFO :0:0000024D:licenseman(1823): There are 7 instances allowed. 20190523:074334:INFO :0:0000024D:hexane.cxx(2848): STROMASYS SA, (C) 2009-2019 20190523:074334:INFO :0:00000408:hexane.cxx(2892): CHARON-VAX (VAX 6000 Model 610), V 4.10 B 20200, May 14 2019 / 003.msc.test.center.kirill / 1422726238 20190523:074334:INFO :0:00000336:hexane.cxx(2924): The end user of this software has agreed to STROMASYS' Terms and Conditions for Software License and Limited Warranty, as described at: /pub/doc/30-17-033.pdf 20190523:074334:INFO :0:00000097:hexane.cxx(2999): OS Environment: Red Hat Enterprise Linux Server release 7.4 (Maipo), Linux 3.10.0-693.5.2.el7.x86_64 #1 SMP Fri Oct 13 10:46:25 EDT 2017 x86_64. 20190523:074334:INFO :0:00000098:hexane.cxx(3004): Host CPU: GenuineIntel, Family 6, Model 42, Stepping 1, Intel Xeon E312xx (Sandy Bridge), 1 Sockets, 1 Cores per Socket, 4 Threads per Core, at ~2593 MHz, 4 cpu's available 20190523:074334:INFO :0:00000099:hexane.cxx(3009): Host Memory: 3840Mb 20190523:074334:INFO :0:0000041F:hexane.cxx(3224): Configuration dump:: . session: . . configuration_name = "VAX_6610" . . log_method = "overwrite" . . hw_model = "VAX_6610" . . log_mode = "shared" . . log_locale = "english" . XMI: . . clock_period = "20000" . . boot = "manual" . RAM: . . size = "512" . eeprom: . . container = "charon.rom" . TOY: . . container = "charon.dat" . OPA0: . . trace = "disabled" . . stop_on = "F6" . . tx_flush_delay = "0" . PUA: . . container[0] = "/home/charon/Charon/test/performancecomparison-66x0.vdisk" . . xmi_node_id = "11" . EXA: . . adapter_mode = "auto" . . interface = "EXA0" . . rx_fifo_delay_on_overload = "false" . . extended_command_ring = "false" . . xmi_node_id = "13" . EXA0: . . interface = "eth1" . . disabled_mode = "10BaseT-HD" . . port_show_driver_statistics = "false" . . port_enable_mac_addr_change = "true" . . port_snd_sock_buf_size_kb = "0" 20190523:074336:WARN :1:00000431:lnxpackpor(1006): (95) Operation not supported: EXA0: ioctl("eth1", SIOCETHTOOL, GSET) 20190523:074336:INFO :0:00000001: tpool.cxx(1374): CPU: The ACE option is omitted; enable ACE as license default. 20190523:074337:INFO :0:00000133: tpool.cxx(1606): Advanced CPU Emulation (ACE) enabled. 20190523:074337:INFO :0:00000400:ethdev.cxx( 388): EXA: RX FIFO size is 512KB. 20190523:074338:INFO :0:0000032C:hexane.cxx(2740): "VAX_6610" started. 20190523:074345:INFO :0:0000014F:lnxpackpor(1652): EXA0: Carrier loss detected. 20190523:074539:INFO :0:000003D7:hexane.cxx(5548): All virtual CPUs of "VAX_6610" have been stopped by now. 20190523:074539:INFO :0:0000032D:hexane.cxx(2784): "VAX 6000 Model 610" stop request received. 20190523:074539:INFO :0:0000014C:lnxpackpor( 433): EXA0: Stopping network interface ... please wait. 20190523:074539:INFO :0:0000024D:licenseman(1823): Licensing component received stop request. 20190523:074539:INFO :0:0000032E:hexane.cxx(2811): Stopped. 20190523:074539:INFO :0:0000014C:lnxpackpor( 433): EXA0: Stopping network interface ... please wait. |
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).
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.
| 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.
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:
|
| 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.
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:
|
| Div | ||
|---|---|---|
| ||
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.
| 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:
...
| 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:
...
| 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:
...
| 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.
...
| 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.
...
| 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:
...