Page Comparison

TopConfigurationPage

Anchor

TopConfigurationPage

Anchor

	TOC
	TOC

Include Page

	KBCOMMON:KB-CSSstyle
	KBCOMMON:KB-CSSstyle

...

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

class	pagebreak

Notepad will be used to edit the configuration file:

Image Removed

...

Image Added

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

VAX/PDP11 model specification

...

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

...

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Div

class	pagebreak

Configuration name

...

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 Rotatinglog(default) ).

Back to Table of Contents

...

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Div

class	pagebreak

Log file parameters

...

Here is an example of a CHARON VM log file:

The default setting is:

load

2016112020180607:142250133937:INFO :0:00000249:ethane.cxx(83439010): Logging started.
2016112020180607:142250133937:INFO :0:000003A5:ethane.cxx(9414 131): session: loading built-in configuration "MicroVAX_3100_Model_963600"...
2016112020180607:142250133937:INFO :0:000003A6:ethane.cxx(9446 163): session: ... done loading built-in configuration "MicroVAX_3100_Model_963600"
2016112020180607:142250133937:INFO :0:000003A7:ethane.cxx(9604 321): session: loading service configuration "My_MV3100_96MV3600"...
2016112020180607:142250133937:INFO :0:000003A8:ethane.cxx(9639 356): session: ... done loading service configuration "My_MV3100_96MV3600"
2016112020180607:142250133937:INFO :0:000003AA:ethane.cxx(9687 404): session: loading configuration file "C:\Program Files\CHARON\Virtual Machines\My_MV3600\My_MV3600\My_MV3100_96\mv3k196mv3k6.cfg"...
The previous message has been repeated 2 times.
2016112020180607:142250133937:INFO :0:000003AB:ethane.cxx( 540579): session: ... done loading configuration file "configuration_name.icfg"
The previous message has been repeated 2 times.
2016112020180607:142250133937:INFO :0:000003F2:sesmgr.cxx(13941410): session: default log file size limit is 4194304 bytes
2016112020180607:142250133937:INFO :0:0000032B:ethane.cxx(25812694): Start request received.
2016112020180607:142250133937:INFO :0:000003AC:ethane.cxx( 739805): session: process affinity is 00000000000000FF, system affinity is 00000000000000FF
2016112020180607:142250133937:INFO :0:000003D1:ethane.cxx(13971463): session: I/O domain affinity is 0000000000000003, CPU domain affinity is 00000000000000FC
2016112020180607:142250133937:INFO :0:000003BA0000024D:ll_sentine( 730licenseman(1823): LookingChecking forthe aavailable license key ."1422726238"..
20161120:142250:INFO :0:000003DC:ll_sentine( 825): ... found license key 1422726238.
20161120:142250The previous message has been repeated 26 times.
20180607:133938:INFO :0:0000024D00000408:ethane.cxx(27122867): 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 2016CHARON-VAX (MicroVAX 3600), V 4.9 B 19401, May 10 2018 / 000.MSCmsc.TESTtest.CENTERcenter.KIRILLnikolaev / 14227262381918154109
2016112020180607:142250133938:INFO :0:00000336:ethane.cxx(27952908): 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
2016112020180607:142250133938:INFO :0:0000009D00000097:ethane.cxx(28592987): LicenseOS 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:142250Environment: Microsoft Windows 10 Pro, 64-bit (Build 17134).
20180607:133938:INFO :0:00000098:ethane.cxx(2992): Host CPU: Intel(R) Xeon(R) CPU E31275 @ 3.40GHz x8.
20180607:133938:INFO :0:0000009700000099:ethane.cxx(28682997): OSHost Environment: Microsoft Windows 7 Professional, 64-bit, Service Pack 1 (Build 7601).
20161120:142250Memory: 24320Mb
20180607:133938:INFO :0:000000980000041F:ethane.cxx(28733223): HostConfiguration CPUdump:: 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.

...

class	pagebreak

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.

...

class	pagebreak

The following table shows all the parameters:

...

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

...

class	pagebreak

Console

Mapping to system resources

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

...

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:

...

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.


. 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"
20180607:133938:INFO :0:00000418:busemul.cx( 188): SSC: MultiMedia Timer correction is enabled.
20180607:133939:INFO :0:00000001: tpool.cxx(1374): CPU: The ACE option is omitted; enable ACE as license default.
20180607:133939:INFO :0:00000133: tpool.cxx(1606): Advanced CPU Emulation (ACE) enabled.
20180607:133939:INFO :0:0000032C:ethane.cxx(2730): "My_MV3600" started.
20180607:133939:INFO :0:00000419:winsckio.c(2703): OPA0: Connected. Remote 127.0.0.1:61468.
20180607:134413:INFO :0:0000032D:ethane.cxx(2776): "MicroVAX 3600" stop request received.
20180607:134413:INFO :0:0000024D:licenseman(1823): Licensing component received stop request.
20180607:134413:INFO :0:0000032E:ethane.cxx(2794): Stopped.
20180607:134413:INFO :0:0000024A:ethane.cxx(9706): Logging stopped.

Div

class	pagebreak

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"

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.

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"

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

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.

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:

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

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:

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

Div

class	pagebreak

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.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Div

class	pagebreak

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"

...

class	pagebreak

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:

...

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 "\\.\COM1"
#load virtual_serial_line/chserial TTA0 port=10000
#load COM<n>" physical serial line.

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

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

line

port=10003 application="

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

...

class	pagebreak

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:

...

"<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"
.
Warning
Using compressed folders to store virtual disks and tapes is not supported
.

...

.

...

DevID addresses the target physical disk by its WWID (hexadecimal 128-bit identifier assigned to the disk drive by its manufacturer/originator).

Example:

Div

class	small

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:

Div

class	small

set DUA container[3]="\\.\PhysicalDrive(iScsiTarget= iqn.2008-04:iscsi.charon-target-test1, LUN= 1)"

Mapping to CD-ROM device.

"\\.\CdRom<N>"

Example:

...

.

...

"<file-name>.iso"

Mapping may also include the full path (recommended), for example: "C:\My disks\vms_distributive.iso"

Example:

...

.

...

"\\.\A:"

Example:

...

.

...

"\\.\<N>:"

Example:

...

.

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:

...

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

Back to Table of Contents

...

class	pagebreak

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

...

class	pagebreak

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

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"

Mapping Object	Description
virtual_scsi_disk

Warning
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_deviceMapping 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.

ParameterDescriptionNA logical number assigned by host operating system (Microsoft Windows) to logical or host’s physical storage resource such as physical SCSI HBAXAn internal SCSI bus number (usually 0) on host’s physical SCSI HBAYA SCSI ID of physical SCSI target device attached to host’s physical SCSI HBAZA logical unit number inside physical SCSI target device attached to host’s physical SCSI HBA

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"

Div

class	pagebreak

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.

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.

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.

Div

class	pagebreak

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"
  .
  Warning
  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:
  
  Div
  class small
  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:
  
  Div
  class small
  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.

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Div

class	pagebreak