Page Comparison

Anchor

	TopConfigurationPage
	TopConfigurationPage

...

To change the configuration file, run the CHARON Virtual Machine Manager from its shortcut on Desktop / Start menu or from the tray menu item, select the target CHARON VM and either press the "Change VM" button or select the "VM Configuration" tab:

Image RemovedImage Added

In the appearing dialog press the "Edit Configuration file" button:

Image RemovedImage Added

Edit the CHARON VM configuration using the default text editor:

Image RemovedImage Added

Back to Table of Contents

...

You must leave this line untouched.

If you create the CHARON -VAX / CHARON-PDP VM configuration file from scratch it must be the very first uncommented line in the configuration file.

...

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

...

Log file parameters

Execution of CHARON -VAX / CHARON-PDP 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 possible problems either with the running CHARON -VAX / CHARON-PDP VM or the emulated system configuration (such as the absence or malfunction of certain devices), the log file(s) is the primary source to be analyzed for troubleshooting. If it becomes necessary to contact Stromasys for support, the configuration and log files will be requested to begin problem resolution.

Here is an example of a CHARON -VAX / CHARON-PDP VM log file:

20151027

20160920:

112735

142250:INFO :0:00000249:ethane.cxx(

9611

8343): Logging started.

20151027

20160920:

112735

142250:INFO :0:000003A5:ethane.cxx(

781

9414): session

is

: loading built-in configuration "MicroVAX_3100_Model_

3600

96"...

20151027

20160920:

112735

142250:INFO :0:000003A6:ethane.cxx(

814

9446):

session has finished loading

 session: ... done loading built-in configuration "MicroVAX_3100_Model_

3600

96"

.

20151027

20160920:

112735

142250:INFO :0:

000003AA

000003A7:ethane.cxx(

1305

9604): session

is

: loading service configuration

file "mv3k6.cfg

 "My_MV3100_96"...

20151027

20160920:

112735

142250:INFO :0:

000003AB

000003A8:ethane.cxx(

1347

9639):

session has finished loading configuration file "mv3k6.cfg".
20151027:112735:INFO :0:000003F2:sesmgr.cxx(1394): session: default log file size limit is 4194304 bytes
20151027:112735:INFO

 session: ... done loading service configuration "My_MV3100_96"
20160920: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.
20160920:142250:INFO :0:000003AB:ethane.cxx( 540): session: ... done loading configuration file "configuration_name.icfg"
The previous message has been repeated 2 times.
20160920:142250:INFO :0:000003F2:sesmgr.cxx(1394): session: default log file size limit is 4194304 bytes
20160920:142250:INFO :0:0000032B:ethane.cxx(

2520

2581): Start request received.

20151027

20160920:

112735

142250:INFO :0:000003AC:ethane.cxx(

695

 739): session

's

: process affinity is 00000000000000FF, system affinity is 00000000000000FF

.

20151027

20160920:

112735

142250:INFO :0:000003D1:ethane.cxx(

1343

1397): session

's

: I/O domain affinity is 0000000000000003, CPU domain affinity is 00000000000000FC

20151027

20160920:

112735

142250:INFO :0:000003BA:ll_sentine(

725

 730): Looking for a license key ...

20151027

20160920:

112735

142250:INFO :0:000003DC:ll_sentine(

820

 825): ... found license key 1422726238.

20151027

20160920:

112735

142250:INFO :0:0000024D:ethane.cxx(

2651

2712): STROMASYS SA, (C) 2009-

2015

20151027

20160920:

112735

142250:INFO :0:

00000350

00000408:ethane.cxx(

2697

2754): CHARON-VAX (MicroVAX

3600

 3100 Model 96), V 4.

7

8 B

17101, Sep 18 2015 / 000.msc.sanity.tests / 1422726238
20151027:112735:INFO

 18100, Jul 21 2016 / 000.MSC.TEST.CENTER.KIRILL / 1422726238
20160920:142250:INFO :0:00000336:ethane.cxx(

2724

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

20151027

20160920:

112735

142250:INFO :0:0000009D:ethane.cxx(

2801

2859): License info:
CHARON product code: "CHVAX-

460xx

480xx-WI-LI".
Licensed to: "MSC".
License KEY driver is installed as hasplms and is running.
Executable "C:\Windows\system32\hasplms.exe", version

17

 18.0.1.

48248

55505.

20151027

20160920:

112735

142250:INFO :0:00000097:ethane.cxx(

2810

2868): OS Environment: Microsoft Windows 7 Professional, 64-bit, Service Pack 1 (Build 7601).

20151027

20160920:

112735

142250:INFO :0:00000098:ethane.cxx(

2815

2873): Host CPU: Intel(R) Xeon(R) CPU E31275 @ 3.40GHz x8.

20151027

20160920:

112735

142250:INFO :0:00000099:ethane.cxx(

2820

2878): Host Memory: 24320Mb

20151027

20160920:

112735

142251:INFO :0:00000001: tpool.cxx(1370): cpu: The ACE option is omitted; enable ACE as

license default.
20151027:112735:INFO

 license default.
20160920:142251:INFO :0:00000401:ethdev.cxx( 384): eza: RX FIFO is disabled.
20160920:142251:INFO :0:00000133: tpool.cxx(1602): Advanced CPU Emulation (ACE) enabled.

20151027

20160920:

112735

142251:INFO :0:0000032C:ethane.cxx(

2556

2617): "

MicroVAX_3600" started.
20151027:112749:INFO :0:0000032D:ethane.cxx(2602): "MicroVAX 3600" stop request received.
20151027:112749:INFO :0:0000032E:ethane.cxx(2620): Stopped.
20151027:112749:INFO :0:0000024A:ethane.cxx( 365): Logging stopped

My_MV3100_96" started.

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

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

Rotating log (default)

By default CHARON-VAX / CHARON-PDP utilizes default CHARON utilizes a so-called "rotating log". This means that a new default log file is always created each time CHARON VM starts and can switch to another log file if the size of the log file exceeds 64Kb.

...

Alternatively it is possible to use just a single log file. Uncomment the "set session log" line and specify the desired CHARON -VAX / CHARON-PDP VM log file name. Optionally, a path can be added to the log file name. If the path is not specified, the log file is created in the directory from where the guest (emulated machine) is started.

The log file can be extended ("log_method = append") or overwritten ("log_method = overwrite") by CHARON -VAX / CHARON-PDPVM.

Below is a specification of a CHARON -VAX / CHARON-PDP VM log file located in the "?C:\My logs" directory which will be overwritten each time CHARON -VAX / CHARON-PDP VM starts:

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

...

The next objects to be configured are TOY, ROM and EEPROM containers (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, CHARON -VAX / CHARON-PDP VM will create it. It is recommended to specify the path for each file so that time and console parameters will be kept whatever the current directory is when starting the guest.

TOY means "Time of Year"; its container records time, date and some console parameters while CHARON -VAX / CHARON-PDP is VM is not running. To enable, uncomment the following line:

...

The next setting indicates whether CHARON -VAX / CHARON-PDP VM will use Advanced CPU Emulation (ACE) mode:

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

Note Note that ACE significantly speeds up CHARON execution.

...

The next parameter defines the amount of host memory the chosen CHARON -VAX / CHARON-PDP VM model reserves for the emulation:

...

The goal of this configuration step is to tell CHARON -VAX / CHARON-PDP 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 -VAX / CHARON-PDP VM host.
Using this mapping it is possible to connect to CHARON -VAX / CHARON-PDP VM console and disconnect from it at any time.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 -VAX / CHARON-PDP 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, CHARON -VAX / CHARON-PDP VM use the IP port "10003" for the VAX/PDP11 console and starts the "Putty" terminal emulator (included in each CHARON distributive) 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" command from the CHARON system tray icon:Image Removedfeature from the CHARON Virtual Machines Manager.

The default setting is:

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

...

Note there are a number of additional parameters for CHARON -VAX / CHARON-PDP VM serial lines configuration. Follow this link for details.

...

This line provides CHARON -VAX / CHARON-PDP the VM the ability to exit by pressing the "F6" button.

...

The next step is configuration of the disk subsystem and mapping it to system resources using the samples given in the template configuration files.

CHARON-VAX / CHARON -PDP supports MSCP, DSSI, CI and SCSI disk controllers.

...

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"
  .
Mapping to physical disk.
- "\\.\PhysicalDrive<N>"
  Be careful not to destroy all the information from the disk dedicated to CHARON -VAX / CHARON-PDP 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 -VAX / CHARON-PDP 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)"
  
  Div
  class pagebreak
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:"
  .

...

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

Back to Table of Contents

Div

class	pagebreak

SCSI controller NCR53C94

...

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"
"\\.\PhysicalDrive<N>" - mapping to physical disk.
Be careful not to destroy all the information from the disk dedicated to CHARON-VAX / CHARON-PDP 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 -VAX / CHARON-PDP 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.

...

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

...

Back to Table of Contents

Serial Lines

CHARON -VAX / CHARON-PDP supports the following serial lines controllers: CXA16, CXB16, CXY08, DHQ11, DHV11, DZV11, DZQ11, DL11, DLV11, DZ11, DHW42-AA, DHW42-BA and DHW42-CA.

...

Option Description

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

virtual_serial_line

Mapping to an IP port of CHARON -VAX / CHARON-PDPVM.
This mapping makes it possible to connect to and disconnect from the CHARON -VAX / CHARON-PDP 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 -VAX / CHARON-PDP 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, CHARON -VAX / CHARON-PDP VM uses the IP port "10011" for the VAX/PDP11 serial line and starts the "Putty" terminal emulator (included in each CHARON distributive) with a "TXA0" saved session directing it to connect to the IP port "10011".

Info

Note that the "Putty" saved session used in this example is not installed by 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.

...

Note that additional parameters exist for CHARON -VAX / CHARON-PDP VM serial lines configuration, follow this link for details.

...

Div

class	pagebreak

Networking

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

...

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

...

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

...

Follow this link for more details of CHARON -VAX / CHARON-PDP VM network controllers configuration.

Back to Table of Contents

Auto boot

CHARON -VAX / CHARON-PDP can be configured to automatically boot an operating system at start up.

...

Versions Compared

Old Version 2

New Version 3

Key

Log file parameters

Rotating log (default)

SCSI controller NCR53C94

Serial Lines

Networking

Auto boot