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.

This configuration is represented as a text file ("configuration file") containing some specific keywords to define the main settings such as amount of memory, number of CPUs, peripheral devices as well as specifics of CHARON VM executions such as name of VM log file, number of host CPUs used for emulation, etc.

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:

Notepad will be used to edit the configuration file:

Back to Table of Contents

VAX/PDP11 model specification

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

set session hw_model = MicroVAX_3600

You must leave this line untouched.

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

Back to Table of Contents

Configuration name

The next configuration statement is the "Configuration name" option:

#set session configuration_name = MicroVAX_3600

You can optionally uncomment this line to differentiate this CHARON VM instance from all others in a multi-instance environment. The configuration name can be any label that is meaningful.

It is possible to specify a configuration name containing spaces, in this case use quotation marks:

set session configuration_name = "My VAX"

The configuration name is reported in the log file and is used to set the log file name for rotating log (see further: Rotating log (default) ).

Back to Table of Contents

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:

20161120:142250:INFO :0:00000249:ethane.cxx(8343): Logging started.
20161120:142250:INFO :0:000003A5:ethane.cxx(9414): session: loading built-in configuration "MicroVAX_3100_Model_96"...
20161120:142250:INFO :0:000003A6:ethane.cxx(9446): session: ... done loading built-in configuration "MicroVAX_3100_Model_96"
20161120:142250:INFO :0:000003A7:ethane.cxx(9604): session: loading service configuration "My_MV3100_96"...
20161120:142250:INFO :0:000003A8:ethane.cxx(9639): session: ... done loading service configuration "My_MV3100_96"
20161120:142250:INFO :0:000003AA:ethane.cxx(9687): session: loading configuration file "C:\Program Files\CHARON\Virtual Machines\My_MV3600\My_MV3600\My_MV3100_96\mv3k196.cfg"...
The previous message has been repeated 2 times.
20161120:142250:INFO :0:000003AB:ethane.cxx( 540): session: ... done loading configuration file "configuration_name.icfg"
The previous message has been repeated 2 times.
20161120:142250:INFO :0:000003F2:sesmgr.cxx(1394): session: default log file size limit is 4194304 bytes
20161120:142250:INFO :0:0000032B:ethane.cxx(2581): Start request received.
20161120:142250:INFO :0:000003AC:ethane.cxx( 739): session: process affinity is 00000000000000FF, system affinity is 00000000000000FF
20161120:142250:INFO :0:000003D1:ethane.cxx(1397): session: I/O domain affinity is 0000000000000003, CPU domain affinity is 00000000000000FC
20161120:142250:INFO :0:000003BA:ll_sentine( 730): Looking for a license key ...
20161120:142250:INFO :0:000003DC:ll_sentine( 825): ... found license key 1422726238.
20161120:142250:INFO :0:0000024D:ethane.cxx(2712): STROMASYS SA, (C) 2009-2016
20161120:142250:INFO :0:00000408:ethane.cxx(2754): CHARON-VAX (MicroVAX 3100 Model 96), V 4.8 B 18302, Nov 11 2016 / 000.MSC.TEST.CENTER.KIRILL / 1422726238
20161120:142250:INFO :0:00000336:ethane.cxx(2795): 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
20161120:142250:INFO :0:0000009D:ethane.cxx(2859): License info:
CHARON product code: "CHVAX-480xx-WI-LI".
Licensed to: "MSC".
License KEY driver is installed as hasplms and is running.
Executable "C:\Windows\system32\hasplms.exe", version 18.0.1.55505.
20161120:142250:INFO :0:00000097:ethane.cxx(2868): OS Environment: Microsoft Windows 7 Professional, 64-bit, Service Pack 1 (Build 7601).
20161120:142250:INFO :0:00000098:ethane.cxx(2873): Host CPU: Intel(R) Xeon(R) CPU E31275 @ 3.40GHz x8.
20161120:142250:INFO :0:00000099:ethane.cxx(2878): Host Memory: 24320Mb
20161120:142251:INFO :0:00000001: tpool.cxx(1370): cpu: The ACE option is omitted; enable ACE as license default.
20161120:142251:INFO :0:00000401:ethdev.cxx( 384): eza: RX FIFO is disabled.
20161120:142251:INFO :0:00000133: tpool.cxx(1602): Advanced CPU Emulation (ACE) enabled.
20161120:142251:INFO :0:0000032C:ethane.cxx(2617): "My_MV3100_96" started.

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 a so-called "rotating log" method. This means that a new default log file is always created each time the CHARON VM starts and if the size of the log file exceeds 64Kb (previous log files are kept).

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.

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.

The "log" parameter, if specified, must correspond to an existing folder.

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.

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.

The log file can be extended specifying "log_method = append" (*recommended for reporting issues*) or overwritten, specifying "log_method = overwrite".

Below is a specification of a CHARON VM log file located in the "C:\My logs" directory which will be appended each time the CHARON VM starts:

set session log_method = append
set session log = "C:\My logs\my_vax.log"

Back to Table of Contents

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.

TOY means "Time of Year". Its container records time, date and some console parameters while the CHARON VM is not running. It is highly recommended to define and activate this container:

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 and activate this container:

set rom container = "vx4k106.rom"

EEPROM stores the NVRAM content. It is highly recommended to define and activate this container:

set eeprom container = "charon.rom"

Back to Table of Contents

KW11 timer

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

#set KW11 frequency = 50
#set KW11 frequency = 60

Uncomment the line corresponding to the frequency used in the RSX11/RT11 systems to be migrated if needed.

Back to Table of Contents

ACE mode

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

#set cpu ace_mode = false
#set cpu ace_mode = true

Note that ACE significantly speeds up CHARON execution.

Uncomment the desired mode. ACE uses a significant amount of host memory for its normal operation. Check the host resources before enabling.

The "ace_mode" mode is license dependent, the "Charon-xx/Plus" products have ACE mode enabled by default.

Back to Table of Contents

Emulated memory (RAM) size

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

#set ram size = 32
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/PDP11 model. It is very important to keep the listed predefined increment between possible memory values.

The following table shows all the parameters:

Hardware Model	RAM size (in MB)
	Min	Max	Default	Increment
PDP1193	2	4	2	2
PDP1194	2	4	2	2
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.

Note that in some particular orders your license may restrict the maximum RAM amount of each VAX/PDP11 model.

Back to Table of Contents

Console

Mapping to system resources

The next step is the specification of the VAX/PDP11 console (OPA0) serial line:

#load physical_serial_line/chserial OPA0 line="\\.\COM1"
#load virtual_serial_line/chserial OPA0 port=10003
load virtual_serial_line/chserial OPA0 port=10003 application="putty.exe -load OPA0"

The goal of this configuration step is to tell the CHARON VM what host device to use as the virtual system console. The following options are available:

Option Description

physical_serial_line Mapping to host "\\.\COM<n>" physical serial line.

virtual_serial_line

Mapping to an IP port of CHARON VM host.
Using this mapping it is possible to connect to the CHARON VM console and disconnect from it at any time without usage of CHARON Virtual Machines Manager "Show Console" option.It is also possible to start up some chosen application to connect to the CHARON VM console IP port.

Parameter	Description
port	Specifies an IP port on the host to which the CHARON VM console will be mapped
application	A string specifying a name of an application to be started together with CHARON VM to provide emulation of VAX/PDP11 console (terminal emulator)It is assumed that this application has already been configured to use the IP port specified by the corresponding "port" parameter

Example:

load virtual_serial_line/chserial OPA0 port=10003 application="putty.exe -load OPA0"

In the example above, the CHARON VM uses the IP port "10003" for the VAX/PDP11 console and starts the "Putty" terminal emulator (included in the CHARON installation kit) with the "OPA0" saved session directing it to connect to the IP port "10003". If the terminal emulator is closed, it is always possible to reopen it with the "Show Console" feature from the CHARON Virtual Machines Manager.

The default setting is:

load virtual_serial_line/chserial OPA0 port=10003 application="putty.exe -load OPA0"

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:

#load physical_serial_line/chserial TTA0 line="\\.\COM1"
#load virtual_serial_line/chserial TTA0 port=10000

#load virtual_serial_line/chserial TTA0 port=10000 application="putty.exe -load TTA0"

#set quart line[0]=TTA0

#load physical_serial_line/chserial TTA1 line="\\.\COM2"
#load virtual_serial_line/chserial TTA1 port=10001
#load virtual_serial_line/chserial TTA1 port=10001 application="putty.exe -load TTA1"


#set quart line[1]=TTA1

...

#load physical_serial_line/chserial OPA0 line="\\.\COM4"
#load virtual_serial_line/chserial OPA0 port=10003
load virtual_serial_line/chserial OPA0 port=10003 application="putty.exe -load OPA0"


set quart line[3]=OPA0

When using the VAX 4000 and MicroVAX 3100 models, it is possible to configure up to 4 independent console lines: OPA0, TTA0, TTA1 and TTA2. The main one is OPA0.

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):

set OPA0 stop_on = F6

This line allows the CHARON VM to be stopped by pressing the "F6" key.

Back to Table of Contents

Disk subsystem

The disk subsystem and the mapping to the system resources can be done using the samples given in the template configuration files.

CHARON 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, CI controllers - in this section.

MSCP disk controllers (RQDX3, KDB50, KDM70)

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

#load RQDX3 DUA

#set DUA container[0]="<file-name>.vdisk"
#set DUA container[1]="\\.\PhysicalDrive<N>"
#set DUA container[2]="\\.\PhysicalDrive(DevID = <XXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX>)"
#set DUA container[3]="\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)"
#set DUA container[4]="\\.\CdRom<N>"
#set DUA container[5]="<file-name>.iso"
#set DUA container[6]="\\.\A:"
#set DUA container[7]="\\.\H:"

#load RQDX3 DUB address=...
#load RQDX3 DUC address=...

The first line ("load RQDX3 DUA") loads disk controller RQDX3 with name DUA, followed by 6 lines showing different ways of mapping to the host resources:

Mapping to the file representing a physical disk of the VAX/PDP11 system (disk image).
- "<file-name>.vdisk"
  These files can be created from scratch with "MkDisk" utility. Data and OS disks backups are transferred from the original system via tapes or network and restored into these container files.
  Mapping may also include the full path (recommended), for example: "C:\My disks\my_boot_disk.vdisk"
  Example:
  set DUA container[0]="my_bootable_disk.vdisk"
  .
  
  Using compressed folders to store virtual disks and tapes is not supported
  .
Mapping to physical disk.
- "\\.\PhysicalDrive<N>"
  Be careful not to destroy all the information from the disk dedicated to CHARON VM by mistake. These disks must not be formatted by the host OS.
  
  Example:
  set DUA container[1]="\\.\PhysicalDrive1"
  .
Mapping to physical disk by its WWID.
- "\\.\PhysicalDrive(DevID = <XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX>)"
  Be careful not to destroy all the information from the disk dedicated to CHARON VM by mistake. These disks must not be formatted by the host OS.
  DevID addresses the target physical disk by its WWID (hexadecimal 128-bit identifier assigned to the disk drive by its manufacturer/originator).
  Example:
  set DUA container[2]="\\.\PhysicalDrive(DevID= 6008-05F3-0005-2950-BF8E-0B86-A0C7-0001)"
  
  .
Mapping to iSCSI disks.
- "\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)"
  iScsiTarget addresses the disk by its iSCSI target name. LUN specifies LUN on connected iSCSI disk.
  Example:
  set DUA container[3]="\\.\PhysicalDrive(iScsiTarget= iqn.2008-04:iscsi.charon-target-test1, LUN= 1)"
Mapping to CD-ROM device.
- "\\.\CdRom<N>"
  Example:
  set DUA container[4]="\\.\CdRom0"
  .
Mapping to an ISO file for reading distribution CD-ROM image.
- "<file-name>.iso"
  Mapping may also include the full path (recommended), for example: "C:\My disks\vms_distributive.iso"
  Example:
  set DUA container[5]="vms_distributive.iso"
  .
Mapping to Floppy drive.
- "\\.\A:"
  Example:
  set DUA container[6]="\\.\A:"
  .
Mapping to some other type of drive, for example magneto-optical drive.
- "\\.\<N>:"
  Example:
  set DUA container[6]="\\.\H:"
  .

The numbers in the square brackets represent the unit numbers associated with each container of the MSCP controller. For example, the 3rd "set DUA" line of the configuration sample above creates disk "DUA2". 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:

set PUA container[600] = "<file-name>.vtape"
set PUA container[601] = "\\.\Tape0"

Follow this link for details of (T)MSCP controllers configuration.

Back to Table of Contents

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.

Below is a typical configuration template for a preloaded "PKA" NCR53C94 SCSI controller:

# Mapping to disk image load virtual_scsi_disk pka_0 scsi_bus=pka scsi_id=0
set pka_0 container="<file-name>.vdisk"

# Mapping to physical disk load virtual_scsi_disk pka_1 scsi_bus=pka scsi_id=1
set pka_1 container[0]="\\.\PhysicalDrive<N>"
set pka_1 container[1]="\\.\PhysicalDrive(DevID =<XXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX>)"

# Mapping to SCSI device not recognized by Windows load physical_scsi_device pka_2 scsi_bus=pka scsi_id=2
set pka_2 container="\\.\Scsi<N>:<X>:<Y>:<Z>"

# Mapping to host CD-ROM or DVD-ROM load virtual_scsi_cdrom pka_3 scsi_bus=pka scsi_id=3
set pka_3 container="\\.\CdRom<N>"

# Mapping to *.ISO image load virtual_scsi_cdrom pka_4 scsi_bus=pka scsi_id=4
set pka_4 container="<file-name>.iso"

# Mapping to tape drive recognized by Windows load physical_scsi_device pka_5 scsi_bus=pka scsi_id=5
set pka_5 container="\\.\Tape<N>"

# Mapping to tape image load virtual_scsi_tape pka_6 scsi_bus=pka scsi_id=6
set pka_6 container="<file-name>.vtape"

# Include this line to get access to "PKB" adapter include kzdda.cfg

# Mapping to host floppy drive load floppy_scsi_device pkb_6 scsi_bus=pkb scsi_id=6 set pkb_6 container="\\.\A:"

Note that NCR53C94 SCSI controller mapping to system resources is done via specific auxiliary objects:

Mapping Object Description

virtual_scsi_disk

Mapping to a file representing VAX/PDP11 disk (disk image) on the host physical disk:

"<file-name>.vdisk"
These files can be created from scratch with "MkDisk" utility. Data and OS disk backups are transferred from the original system via tapes or network and restored into these container files. Mapping may also include the full path (recommended), for example: "C:\My disks\my_boot_disk.vdisk"

Using compressed folders to store virtual disks and tapes is not supported
"\\.\PhysicalDrive<N>" - mapping to physical disk.
Be careful not to destroy all the information from the disk dedicated to CHARON VM by mistake!
These disks must not be formatted by the host OS.
"\\.\PhysicalDrive(DevID =XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)" - mapping to physical disk by its WWID.
Be careful not to destroy all the information from the disk dedicated to CHARON VM by mistake!
These disks must not be formatted by the host OS.
DevID addresses the target physical disk by its WWID (hexadecimal 128-bit identifier assigned to the disk drive by its manufacturer/originator).
"\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)" - mapping to iSCSI disks.
iScsiTarget addresses the disk by its iSCSI target name.
LUN specifies LUN on connected iSCSI disk.

physical_scsi_device

Mapping to a host SCSI device:

"\\.\Tape<N>" - mapping to a SCSI tape drive known to Windows

"\\.\ScsiN:X:Y:Z" - name of some SCSI device unknown to Windows for direct mapping, for example, a SCSI disk or tape reader. The values of N, X, Y and Z can be collected using special utility "Host Device Check" included in the CHARON distributive - or manually by investigation of the devices connected to CHARON host in the "Device Manager" applet.

Parameter	Description
N	A logical number assigned by host operating system (Microsoft Windows) to logical or host’s physical storage resource such as physical SCSI HBA
X	An internal SCSI bus number (usually 0) on host’s physical SCSI HBA
Y	A SCSI ID of physical SCSI target device attached to host’s physical SCSI HBA
Z	A logical unit number inside physical SCSI target device attached to host’s physical SCSI HBA

virtual_scsi_cdrom

Mapping to a host CD-ROM (not only SCSI) or to ISO image:

"\\.\CdRom<N>" - name of host CD-ROM drive
"<file-name>.iso" - name of ISO image. It may contain the full path, for example: "C:\My disks\vms_distributive.iso"

virtual_scsi_tape Mapping to a file representing tape (tape image). It may contain a path, for example: "C:\My tapes\backup.vtape"

floppy_scsi_device

Mapping to a host floppy drive:

"\\.\A:" or "\\.\B:" - name of host CD-ROM drive. This parameter can be omitted.

Let's look at the syntax of the mapping objects. All of them have several important parameters:

Mapping objects parameters	Description
scsi_bus	The name of the NCR53C94 SCSI controller. A typical value for the first and only preloaded NCR53C94 SCSI controller is "PKA"
scsi_id	SCSI address of this particular mapped device. Note that the preloaded NCR53C94 SCSI controller claims address "7"; addresses 0-6 are vacant and usable. The resulting names of virtual SCSI devices as they are seen in VAX/VMS are made up of the VMS name of the SCSI controller and the device address. For PKA, the device names in VMS will be DKA0, DKA1 etc
container	A keyword for specification of which host device is mapped to a particular virtual SCSI device. It can be disk or tape image, physical disk etc

It is possible to configure another NCR53C94 SCSI controller "PKB" by uncommenting the "include kzdda.cfg" line:

#include kzdda.cfg

#load virtual_scsi_disk pkb_0 scsi_bus=pkb scsi_id=0
#set pkb_0 container="<file-name>.vdisk"
...

In the example above the "pkb_0" virtual SCSI device uses "PKB" controller by specifying a parameter "scsi_bus=pkb"

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.

Back to Table of Contents

Tape subsystem

Some MSCP and SCSI controllers support tape devices. CHARON also emulates specific MSCP tape devices such as TQK50 and TUK50.

Follow this link for more details of (T)MSCP controllers configuration.

Using compressed folders to store virtual disks and tapes is not supported

TQK50 controller

Example statements to configure a TQK50 controller are shown below:

#load TQK50 MUA

#set MUA container[0]="<file-name>.vtape"
#set MUA container[1]="\\.\TapeN"#load TQK50 MUB address=...
#load TQK50 MUC address=...

The first line ("load TQK50 MUA") loads a tape controller TQK50 and names it MUA. The following 2 lines demonstrate different ways of mapping to host resources:

Type of mapping	Description
"<file-name>.vtape"	Mapping to the file representing the tape (tape image). These files are created automatically. Mapping may also include a full path (recommended), for example: "`C:\My tapes\backup.vtape`"
"\\.\TapeN"	Mapping to a host tape device.

Numbers in the square brackets represent unit numbers associated with each container of the TQK50 controller. For example, the 2nd "set MUA" line of the configuration sample above creates the "MUA1" tape drive. The maximum unit number allowed is 9999, significantly more than the original hardware provided

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:

load DWBUA UBA vax_bi_node_id = 14load TUK50 MUA

#set MUA container[0] = "<file-name>.vtape"
#set MUA container[0] = "\\.\TapeN"

The first line loads a UNIBUS BI adapter "DWBUA". Configure then the "TUK50" tape controller the same way as the TQK50.

Back to Table of Contents

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.

All of them are configured according to the following template:

#load DHV11/DHV11 TXA
load DHQ11/DHV11 TXA
#load CXY08/DHV11 TXA
#load CXA16/DHV11 TXA

#load CXB16/DHV11 TXA

#load physical_serial_line/chserial TXA0 line="\\.\COMn"
#load virtual_serial_line/chserial TXA0 port=10010

#set TXA line[0]=TXA0

#load physical_serial_line/chserial TXA1 line="\\.\COMn"
#load virtual_serial_line/chserial TXA1 port=10011

#set TXA line[1]=TXA1

...

#load DHV11/DHV11 TXB address=...
#load DHQ11/DHV11 TXB address=...
#load CXY08/DHV11 TXB address=...
#load CXA16/DHV11 TXB address=...
#load CXB16/DHV11 TXB address=...

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".

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

Option Description

physical_serial_line

Mapping to host "\\.\COM<N>" serial line

virtual_serial_line

Mapping to an IP port. This mapping makes it possible to connect to and disconnect from the CHARON VM serial line at any time.It is also possible to start up some chosen application to connect to the CHARON serial line IP port.

Parameter	Description
port	Specifies an IP port on the host to which the CHARON VM serial line will be mapped
application	A string specifying a name of an application to be started together with CHARON to provide emulation of VAX/PDP11 serial line (terminal emulator)It is assumed that this application has already been configured to use the IP port specified by the corresponding "port" parameter

Example:

load virtual_serial_line/chserial TXA0 port=10011 application="putty.exe -load TXA0"

In the example above, the CHARON VM uses the IP port "10011" for the VAX/PDP11 serial line and starts the "Putty" terminal emulator (included the CHARON installation kit) with a "TXA0" saved session directing it to connect to the IP port "10011".

Note that the "Putty" saved session used in this example is not installed during the CHARON installation procedure. It has to be created manually to connect to the chosen port ("10011" in this example).You can use the OPA0 console configuration specifics as an example to create your own "Putty" configurations.It is also possible to use other terminal emulators. Consult with their User's Guides to learn how to specify loading specific configuration on their startup.

Look at the line "set TXA line[0]=TXA0" in the example. This one and the following lines of similar syntax map the loaded virtual controller ("TXA") to instances of the host serial lines ("TXA<N>").

The number of possible serial lines for each controller depends on its type and corresponds to the HP specification for a given controller.

It is possible to load several CXA16, CXB16, CXY08, DHQ11, DHV11, DZV11, DZQ11, DL11, DLV11 and DZ11 controllers (see the lines 12-16) by configuring specific addresses for them on the Qbus. Use the "CONFIGURE" utility available on the VAX/PDP11 console to determine the addresses. Please refer to specific HP documentation for further information.

The VAX 4000 and MicroVAX3100 models support DHW42-AA, DHW42-BA and DHW42-CA serial lines adapters:

#load DHW42AA/DHV11 TXA
#load DHW42BA/DHV11 TXA

#load DHW42CA/DHV11 TXA

#load physical_serial_line/chserial TXA0 line="\\.\COMn"
#load virtual_serial_line/chserial TXA0 port=10010
#set TXA line[0]=TXA0

Configuring these adapters is the same as above, except it is possible to load one and only one instance of DHW42-AA, DHW42-BA or DHW42-CA.

Note that additional parameters for CHARON VM serial lines configuration can be added. Follow this link for details.

Back to Table of Contents

Networking

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

All of them are configured in a similar way:

load DELQA/DEQNA XQA

load packet_port/chnetwrk XQA0 interface="connection:Charon"
set XQA interface=XQA0

#load DELQA XQB address=...
#load DELQA XQC address=...

In the example above the first line loads DELQA virtual adapter with a name "XQA"; the following 2 lines map it to host network interface having a name "Charon" ("connection" is a key word).

The mapping is performed in 2 steps:

A mapping object "packet_port" with a name "XQA0" is loaded and connected to host interface having a name "Charon" so the CHARON VM will use this interface for its networking
The loaded DELQA virtual adapter "XQA" is connected to the "packet_port" object "XQA0"

It is possible to load several DEQNA, DESQA, DELQA, DEUNA and DELUA controllers (see the lines 4-5) by configuring specific addresses for them on the Qbus. Use the "CONFIGURE" utility available on the VAX/PDP11 console to determine the addresses. Please refer to specific HP documentation for further information.

Some network adapters available in the CHARON VM are preloaded (for example, the SGEC controller for the MicroVAX 3100 with the predefined name "EZA"), so their configuration is even more simple:

load packet_port/chnetwrk EZA0 interface="connection:Charon"

set EZA interface=EZA0

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.

After few seconds the chosen interface will be assigned to CHARON:

Follow this link for more details of CHARON VM network controllers configuration.

Back to Table of Contents

Auto boot

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

The MicroVAX 3100, VAX/PDP11 6310 and VAX/PDP11 4000 models boot automatically if the correct boot flags are set at the VAX/PDP11 console level:

>>>set halt reboot

Please check that the TOY, EEPROM and ROM containers (see above) are enabled so the updated parameters are saved upon reboot.

The ROM of certain VAX models (MicroVAX II, MicroVAX 3600, MicroVAX 3900, VAXserver 3600 and VAXserver 3900) does not allow the SRM console to accept the commands to enable auto booting. In this case, a specific parameter can be defined in the configuration file as a workaround:

set bdr boot=auto

The CHARON-VAX 6000 models have a similar configuration setting:

set xmi boot=auto

The CHARON-PDP models have the following setting:

set cpu_0 auto_boot = "DU0"

These configuration lines are specified in the template configuration files in commented out form. In case of absence please add the corresponding line according to the examples above.

Back to Table of Contents

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:

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.

The “affinity” parameter overrides the default and allows explicit specification of which host CPUs will be used by the instance. The affinity does not reserve the CPU for exclusive use.

set session affinity = "0, 2, 4, 6"

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” parameter overrides the default by specifying the number of I/O host CPUs explicitly.

set session n_of_io_cpus = 2

Back to Table of Contents

Browser not supported