Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

Table of Contents
excludeTable of Contents

Back to Table of ContentsTopConfigurationPage

Creation of your own configuration file using a template

...

Note: the lines preceded by the comment sign "#" inside the configuration files will not be interpreted. You can use this sign to debug your configuration.

Back to Table of ContentsTopConfigurationPage

VAX model specification

The first configuration statement is the specification of the exact VAX hardware model to emulate.

...

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

Back to Table of ContentsTopConfigurationPage

Configuration name

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

...

You can optionally uncomment this line to differentiate this CHARON-VAX instance from all others in a multi-instances environment. The configuration name can be any label that is meaningful. It 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 ContentsTopConfigurationPage

Log file parameters

Execution of CHARON-VAX 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 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, plus the license number, will be requested to begin problem resolution.

Here is an example of a field test CHARON-VAX log file:

2016112020180528:083215033359:INFO :0:000003A50000024D:hexane.cxxlicenseman(5312): session is loading built-in configuration "VAX_6610"...
20161120:0832151823): Checking product section 0.
20180528:033359:INFO :0:000003A60000024D:hexane.cxxlicenseman(53361823): session has finished loading built-in configuration The value "VAX_6610" .

20161120:083215of the required parameter "P_HW" is not found in the list "AlphaServer_DS10,AlphaServer_DS10L,AlphaServer_DS15,AlphaServer_DS20,AlphaServer_DS25,AlphaServer_ES40,AlphaServer_ES45,AlphaServer_GS80,AlphaServer_GS160,AlphaServer_GS320" for the product 0.
20180528:033359:INFO :0:000003AA0000024D:hexane.cxxlicenseman(54251823): session is loading configuration file "vx6k610.cfg"...

20161120:083215Checking product section 1.
20180528:033359:INFO :0:000003AB0000024D:hexane.cxxlicenseman(5455): session has finished loading configuration file "vx6k610.cfg".

20161120:0832151823): The value "VAX_6610" of the required parameter "P_HW" is not found in the list "PDP1193,PDP1194" for the product 1.
20180528:033359:INFO :0:000003F20000024D:sesmgr.cxxlicenseman(1394): session: default log file size limit is 4194304 bytes

20161120:0832151823): Checking product section 2.
20180528:033359:INFO :0:0000032B0000024D:hexane.cxxlicenseman(2547): Start request received.

20161120:0832161823): License number: "000.msc.test.center.nikolaev".
20180528:033359:INFO :0:000003AC0000024D:hexane.cxxlicenseman(12871823): session's process affinity is 000000000000000F, system affinity is 000000000000000F.

20161120:083216: Product License number: "CHAXP/VAX".
20180528:033359:INFO :0:000003D10000024D:hexane.cxxlicenseman(1541): session's I/O domain affinity is 0000000000000001, CPU domain affinity is 000000000000000E

20161120:0832161823): CHARON product code: "CHVAX-490xx-WI-LI".
20180528:033359:INFO :0:000003BA0000024D:ll_sentinelicenseman( 7251823): Looking for a Unlimited license key ...
2016112020180528:083217033359:INFO :0:000003DC0000024D:ll_sentinelicenseman( 820): ... found license key 1422726238.

20161120:0832171823): Feature 2 check interval 1 hour(s).
20180528:033359:INFO :0:0000024D:hexane.cxxlicenseman(26881823): STROMASYS SA, (C) 2009-2015

20161120:083217Concurrency info:
20180528:033359:INFO :0:000003500000024D:licenseman(1823): There are 10 instances allowed.
20180528:033359:INFO :0:0000024D:hexane.cxx(2848): STROMASYS SA, (C) 2009-2018
20180528:033359:INFO :0:00000408:hexane.cxx(27342892): CHARON-VAX (VAX 6000 Model 610), V 4.8 9 B 18302, Nov 11 2016 19401, May 10 2018 / 000.msc.sanitytest.center.tests nikolaev / 14227262381918154109
2016112020180528:083217033359:INFO :0:00000336:hexane.cxx(27612924): 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:083217:INFO :0:0000009D:hexane.cxx(2838): License info:
CHARON product code: "CHVAX-460xx-WI".
Licensed to: "MSC".20161120:08321720180528:033359:INFO :0:00000097:hexane.cxx(28472999): OS Environment: Linux 3.1910.8-100.fc200-693.5.2.el7.x86_64 #1 SMP Tue May 12 17:08:50 UTC 2015 Fri Oct 13 10:46:25 EDT 2017 x86_64.
2016112020180528:083217033359:INFO :0:00000098:hexane.cxx(28523004): Host CPU: GenuineIntel, Family 6, Model 42, Stepping 1, Intel Xeon E312xx (Sandy Bridge), 1 Sockets, 1 Cores per ChipSocket, 1 4 Threads per Core, at ~2593 MHz, 4 cpu's available
2016112020180528:083217033359:INFO :0:00000099:hexane.cxx(28573009): Host Memory: 4096Mb3840Mb
2016112020180528:083217033359:INFO :0:000003480000041F:mscpdiskhexane.ccxx( 3333224): PUA0 is being set OFFLINE

20161120:083217:INFO :0:00000001: tpool.cxx(1370): cpu: The ACE option is omitted; enable ACE as license default.
20161120:083218:INFO :0:00000133: tpool.cxx(1602): Advanced CPU Emulation (ACE) enabled.
20161120:083218:INFO :0:0000032C:hexane.cxx(2589): "VAX_6610" started.
20161120:083300:INFO :0:00000347:mscpdisk.c(3656): PUA0 is being set ONLINE
container = "/home/charon/Charon/test/performancecomparison-66x0.vdisk"
media_type = ""
geometry = ""
use_io_file_buffering = falseConfiguration dump::
. session:
. . configuration_name = "VAX_6610"
. . log_method = "overwrite"
. . hw_model = "VAX_6610"
. . log_mode = "shared"
. . log_locale = "english"
. XMI:
. . clock_period = "20000"
. . boot = "manual"
. RAM:
. . size = "512"
. eeprom:
. . container = "charon.rom"
. TOY:
. . container = "charon.dat"
. OPA0:
. . trace = "disabled"
. . stop_on = "F6"
. . tx_flush_delay = "0"
. PUA:
. . container[0] = "/home/charon/Charon/test/performancecomparison-66x0.vdisk"
. . xmi_node_id = "11"
. EXA:
. . adapter_mode = "auto"
. . interface = "EXA0"
. . rx_fifo_delay_on_overload = "false"
. . extended_command_ring = "false"
. . xmi_node_id = "13"
. EXA0:
. . interface = "eth1"
. . disabled_mode = "10BaseT-HD"
. . port_show_driver_statistics = "false"
. . port_enable_mac_addr_change = "true"
. . port_snd_sock_buf_size_kb = "0"

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

...

set session log_method = append
set session log = "/my_logs/my_vax.log"

Back to Table of ContentsTopConfigurationPage 

TOY, ROM and EEPROM containers

...

set eeprom container="charon.rom"

Back to Table of ContentsTopConfigurationPage

Emulated memory (RAM) size

...

It is possible to leave the RAM line commented out. In this case the model's default RAM amount is used.

Back to Table of ContentsTopConfigurationPage

Div
classpagebreak


Console

Mapping to system resources

...

It is strongly recommended to uncomment this line to provide CHARON-VAX the ability to exit by pressing the "F6" key.

Back to Table of ContentsTopConfigurationPage

Disk subsystem

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

...

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

Back to Table of Contents

SCSI controller NCR53C94

The VAX 4000 and MicroVAX 3100 have an NCR53C94 SCSI controller onboard for support of different types of SCSI devices including disks and tapes. Optionally a second controller can be added.

...

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

Back to Table of ContentsTopConfigurationPage

Tape subsystem

Some MSCP and SCSI controllers support tape devices, however CHARON-VAX 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.

Back to Table of ContentsTopConfigurationPage

Div
classpagebreak


Serial Lines

...

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

Back to Table of ContentsTopConfigurationPage

Networking

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

...

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

Back to Table of ContentsTopConfigurationPage

Div
classpagebreak


Auto boot

...

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

set xmi boot=auto

Back to Table of ContentsTopConfigurationPage


Host load balance for SMP systems

...

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

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


Section


Column
width320px


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


Section


Column
width320px


set session n_of_io_cpus = 2





Back to Table of ContentsTopConfigurationPage