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.

Back to Table of Contents

...

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

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:

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

...

The configuration name is <...>" syntax:

include configuration_name.icfg

Notes:

The configuration name is reported in the log file and is used to set the log file name for rotating

...

log (see explanations further

...

).

Back to Table of Contents

...

class	pagebreak

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:

...

Changing the configuration name in the "configuration_name.icfg" file does not change the name of the virtual machine at Virtual Machines Manager level.
The "configuration_name.icfg" file can be found in the home directiory of the VM. Select the target VM, open "VM Configuration" tab and press "Explore" button.

The configuration name can be any label that is meaningful.

Example:

set session configuration_name = My_VAX

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

set session configuration_name = "My VAX"

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

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:

20180607:133937:INFO :0:00000249:ethane.cxx(9010): Logging started.
20180607:133937:INFO :0:000003A5:ethane.cxx(

9414

131):

session:

loading

built-in

configuration

"MicroVAX_

3100_Model_96

3600"...

20161120

20180607:

142250

133937:INFO

:0:000003A6:ethane.cxx(

9446

163):

session:

...

done

loading

built-in

configuration

"MicroVAX_

3100_Model_96"
20161120:142250

3600"
20180607:133937:INFO

:0:000003A7:ethane.cxx(

9604

321):

session:

loading

service

configuration

"My_

MV3100_96

MV3600"...

20161120

20180607:

142250

133937:INFO

:0:000003A8:ethane.cxx(

9639

356):

session:

...

done

loading

service

configuration

"My_

MV3100_96

MV3600"

20161120

20180607:

142250

133937:INFO

:0:000003AA:ethane.cxx(

9687

404):

session:

loading

configuration

file

"C:\Program

Files\CHARON\Virtual

Machines\My_MV3600\

My_MV3600\My_MV3100_96\mv3k196

mv3k6.cfg"...
The

previous

message

has

been

repeated

2

times.

20161120

20180607:

142250

133937:INFO

:0:000003AB:ethane.cxx(

540

579):

session:

...

done

loading

configuration

file

"configuration_name.icfg"
The

previous

message

has

been

repeated

2

times.

20161120

20180607:

142250

133937:INFO

:0:000003F2:sesmgr.cxx(

1394

1410):

session:

default

log

file

size

limit

is

4194304

bytes

20161120

20180607:

142250

133937:INFO

:0:0000032B:ethane.cxx(

2581

2694):

Start

request

received.

20161120

20180607:

142250

133937:INFO

:0:000003AC:ethane.cxx(

739

805):

session:

process

affinity

is

00000000000000FF,

system

affinity

is

00000000000000FF

20161120

20180607:

142250

133937:INFO

:0:000003D1:ethane.cxx(

1397

1463):

session:

I/O

domain

affinity

is

0000000000000003,

CPU

domain

affinity

is

00000000000000FC

20161120

20180607:

142250

133937:INFO

:0:

000003BA

0000024D:

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

licenseman(1823): Checking the available license key "1422726238".
The previous message has been repeated 26 times.
20180607:133938:INFO :0:00000408:ethane.cxx(2867): CHARON-VAX (MicroVAX 3600), V 4.9 B 19402, May 10 2018 / 000.msc.test.center.nikolaev / 1918154109
20180607:133938:INFO :0:00000336:ethane.cxx(

2712

2908):

STROMASYS SA, (C) 2009-2016
20161120:142250:INFO :0:00000408

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
20180607:133938:INFO :0:00000097:ethane.cxx(

2754

2987)

: 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

: OS Environment: 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:00000099:ethane.cxx(2997): Host Memory: 24320Mb
20180607:133938:INFO :0:0000041F: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

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"
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 = "C:\My logs\my_vax.log"

...

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

TOY, ROM and EEPROM containers

...

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:

...

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:

...

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

...

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

...

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.

...

#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[64]="\\.\A:CdRom<N>"
#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:

...

5]="<file-name>.

...

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

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

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=50
set pka_5 0 container="\\.\Tape<N><file-name>.vdisk"

# Mapping to tape imagephysical disk load virtual_scsi_tape disk pka_6 1 scsi_bus=pka scsi_id=61
set pka_6 1 container[0]="<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 \\.\PhysicalDrive<N>"
set pka_1 container[1]="\\.\PhysicalDrive(DevID =<XXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX>)"

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

...

class	pagebreak

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

A logical unit number inside physical SCSI target device attached to host’s physical SCSI HBA

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

Mapping Object Description

virtual_scsi_disk

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

# Mapping to *.ISO image load virtual_scsi_cdrom pka_4 scsi_bus=pka scsi_id=4
set pka_4 container="<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"

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_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

Div

class	pagebreak

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

Mapping to a host SCSI device:

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

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.

...

Follow this link for details of NCR53C94 SCSI controller controllers configuration.

...

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.

...

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

...

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.

...

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

...

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Div

class	pagebreak

Networking

...

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

...

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Div

class	pagebreak

Auto boot

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

...

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:

...

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.

...

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Host load balance for SMP systems

...

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.

Section

Column

width	260px

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.

Section

Column

width	260px

set session n_of_io_cpus = 2

...

Include Page

	KBCOMMON:DOC-GoToToc
	KBCOMMON:DOC-GoToToc

Versions Compared

Old Version 15

New Version Current

Key

VAX/PDP11 model specification

Configuration name

Log file parameters

Log file parameters

TOY, ROM and EEPROM containers

KW11 timer

ACE mode

Emulated memory (RAM) size

Console

Mapping to system resources

Disk subsystem

SCSI controller NCR53C94

SCSI controller NCR53C94

Tape subsystem

Serial Lines

Networking

Auto boot

Host load balance for SMP systems