Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: "Rotating log" chapter updated to match Linux explanations.

Anchor
TOC
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

Table of Contents

Table of Contents
excludeTable 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.

...

To change the configuration file, open the CHARON Virtual Machines Manager from its shortcut on Desktop / Start menu or from the tray menu item, select the target CHARON VM and press the "Edit Configuration" button:

Image RemovedImage Added


Div
classpagebreak


Notepad will be used to edit the configuration file:

Image RemovedImage Added

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

VAX/PDP11 model specification

The first configuration statement is the specification of the exact VAX/PDP11 hardware model to emulate, for example:

...

(warning) If you create the CHARON VM configuration file from scratch, it must be the very first uncommented line in the configuration file.

...

Div
classpagebreak


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
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


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.

(info) 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
borderColor#EDEDEE
bgColor#FFFFFF
titleColor#000000
titleBGColor#EDEDEE
titleCHARON-VAX log file example (part1)

20190110:133937:INFO :0:00000249:ethane.cxx(9010): Logging started.

...

20190110:133937:INFO :0:000003A5:ethane.cxx( 131): session: loading built-in configuration "MicroVAX_3600"...

...

20190110:133937:INFO :0:000003A6:ethane.cxx( 163): session: ... done loading built-in configuration "MicroVAX_3600"

...

20190110:133937:INFO :0:000003A7:ethane.cxx( 321): session: loading service configuration "My_MV3600"...

...

20190110:133937:INFO :0:000003A8:ethane.cxx( 356): session: ... done loading service configuration "My_MV3600"

...

20190110:133937:INFO :0:000003AA:ethane.cxx( 404): session: loading configuration file "C:\Program Files\CHARON\Virtual Machines\My_MV3600\mv3k6.cfg"...
The previous message has been repeated 2 times.

...

20190110:133937:INFO :0:000003AB:ethane.cxx( 579): session: ... done loading configuration file "configuration_name.icfg"
The previous message has been repeated 2 times.

...

20190110:133937:INFO :0:000003F2:sesmgr.cxx(1410): session: default log file size limit is 4194304 bytes

...

20190110:133937:INFO :0:0000032B:ethane.cxx(2694): Start request received.

...

20190110:133937:INFO :0:000003AC:ethane.cxx( 805): session: process affinity is 00000000000000FF, system affinity is 00000000000000FF

...

20190110:133937:INFO :0:000003D1:ethane.cxx(1463): session: I/O domain affinity is 0000000000000003, CPU domain affinity is 00000000000000FC

...

20190110:133937:INFO :0:0000024D:licenseman(1823): Checking the available license key "1422726238".
The previous message has been repeated 26 times.

...

20190110:133938:INFO :0:00000408:ethane.cxx(2867): CHARON-VAX (MicroVAX 3600), V 4.

...

10 B

...

20200,

...

Dec 10

...

2019 / 000.msc.test.center.nikolaev / 1918154109

...

20190110:133938:INFO :0:00000336:ethane.cxx(2908): The end user of this software has agreed to STROMASYS' Terms and Conditions for Software License and Limited Warranty, as described at: http://www.stromasys.com/pub/doc/30-17-033.pdf

...

20190110:133938:INFO :0:00000097:ethane.cxx(2987): OS Environment: Microsoft Windows 10 Pro, 64-bit (Build 17134).

...

20190110:133938:INFO :0:00000098:ethane.cxx(2992): Host CPU: Intel(R) Xeon(R) CPU E31275 @ 3.40GHz x8

...

.


Panel
borderColor#EDEDEE
bgColor#FFFFFF
titleColor#000000
titleBGColor#EDEDEE
titleCHARON-VAX log file example (part2)

20190110:133938:INFO :0:00000099:ethane.cxx(2997): Host Memory: 24320Mb

...

20190110:133938:INFO :0:0000041F:ethane.cxx(3223): Configuration dump::
. session:
. . configuration_name = "My_MV3600"
. . log_method = "append"
. . log_locale = "English"
. . log_show_messages = "all"
. . log_repeat_filter = "on"
. cdal:
. . mm_timer_correction_disable = "false"
. IPR:
. . mm_timer_correction_disable = "false"
. RAM:
. . size = "16"
. SSC:
. . clock_period = "20000"
. . mm_timer_correction_disable = "false"
. q_bus:
. . mm_timer_correction_disable = "false"
. . interface = "enabled"
. UART:
. . line = "OPA0"
. . rx_done_delay = "10000"
. . tx_done_delay = "50"
. . tx_buffer_interval = "2000"
. . baud_rate = "9600"
. . stop_len = "1"
. . char_len = "8"
. . parity = "none"
. . dtr = "off"
. . rts = "off"
. . force_character_mask = "255"
. BDR:
. . boot = "manual"
. . mode = "normal"
. OPA0:
. . trace = "disabled"
. . port = "10003"
. . application = "putty.exe -load OPA0"

...

20190110:133938:INFO :0:00000418:busemul.cx( 188): SSC: MultiMedia Timer correction is enabled.

...

20190110:133939:INFO :0:00000001: tpool.cxx(1374): CPU: The ACE option is omitted; enable ACE as license default.

...

20190110:133939:INFO :0:00000133: tpool.cxx(1606): Advanced CPU Emulation (ACE) enabled.

...

20190110:133939:INFO :0:0000032C:ethane.cxx(2730): "My_MV3600" started.

...

20190110:133939:INFO :0:00000419:winsckio.c(2703): OPA0: Connected. Remote 127.0.0.1:61468.

...

20190110:134413:INFO :0:0000032D:ethane.cxx(2776): "MicroVAX 3600" stop request received.

...

20190110:134413:INFO :0:0000024D:licenseman(1823): Licensing component received stop request.

...

20190110:134413:INFO :0:0000032E:ethane.cxx(2794): Stopped.

...

20190110:134413:INFO :0:0000024A:ethane.cxx(9706): Logging stopped.

Div
classpagebreak

The next group of parameters defines the name of the CHARON VM log file and how the CHARON VM will use it:

set session log_method = append
#set session log_method = overwrite
#set session log = "MicroVAX_3600.log"

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.

...

(info) 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
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc
 

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
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

KW11 timer

PDP11/93 and PDP11/94 emulators require the KW11 system timer to be configured:

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

ACE mode

The next setting indicates whether the CHARON VM will use the Advanced CPU Emulation (ACE) mode:

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Emulated memory (RAM) size

The next parameter defines the amount of host memory the CHARON VM reserves for the emulation:

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


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
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

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
classpagebreak


MSCP disk controllers (RQDX3, KDB50, KDM70)

Below is a typical configuration sample for the MSCP disk controller RQDX3:

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


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
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

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
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

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
classpagebreak


Once the controller is loaded it can be mapped to system resources (lines 6-11). The following options are available:

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc


Div
classpagebreak


Networking

CHARON supports DEQNA, DESQA, DELQA, DEUNA, DELUA, DEMNA, DEBNI and PMADAA virtual network adapters.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


Auto boot

CHARON can be configured to automatically boot an operating system at start up.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

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:

...