Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update for PDF export

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

Table of Contents

Table of Contents
excludeTable of Contents

Creation of your own configuration file using a template

By default, all the CHARON templates are located in the "/opt/charon/cfg" folder. Copy the appropriate template configuration file(s) to your home directory or to any directory intended for CHARON-AXP, name them meaningfully and set proper privileges.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


HP Alpha model specification

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

...

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

...

Configuration name

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

...

You can optionally uncomment this line to differentiate this CHARON-AXP 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 (default) ).

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


Log file parameters

Execution of CHARON-AXP 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-AXP 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.

...

classpagebreak

Here is an example of a field test

Panel
borderColor#EDEDEE
bgColor#FFFFFF
titleColor#000000
titleBGColor#EDEDEE
titleCHARON-AXP log file

...

example (part1)

20190110:035210:INFO :0:000003A5:hexane.cxx(5938): session: loading built-in configuration "AlphaServer_ES40"...
20190110:035210:INFO :0:000003A6:hexane.cxx(5959): session: ... done loading built-in configuration "AlphaServer_ES40"
20190110:035210:INFO :0:000003AA:hexane.cxx(5988): session: loading configuration file "es40.cfg"...
20190110:035210:INFO :0:000003AB:hexane.cxx(6012): session: ... done loading configuration file "es40.cfg"
20190110:035210:INFO :0:000003F2:sesmgr.cxx(1410): session: default log file size limit is 4194304 bytes
20190110:035210:INFO :0:0000032B:hexane.cxx(2698): Start request received.
20190110:035211:INFO :0:000003AC:hexane.cxx(1424): session: process affinity is 000000000000000F, system affinity is 000000000000000F
20190110:035211:INFO :0:000003D1:hexane.cxx(1686): session: I/O domain affinity is 0000000000000001, CPU domain affinity is 000000000000000E
20190110:035211:INFO :0:0000024D:licenseman(1823): Checking the available license key "1918154109".
20190110:035211:INFO :0:0000024D:licenseman(1823): Found license key: "1918154109".
20190110:035211:INFO :0:0000024D:licenseman(1823): Checking product section 0.
20190110:035211:INFO :0:0000024D:licenseman(1823): License number: "000.msc.test.center.nikolaev".
20190110:035211:INFO :0:0000024D:licenseman(1823): Product License number: "CHAXP/AXP".
20190110:035211:INFO :0:0000024D:licenseman(1823): CHARON product code: "CHAXP-490xx-WI-LI".
20190110:035211:INFO :0:0000024D:licenseman(1823): Unlimited license.
20190110:035211:INFO :0:0000024D:licenseman(1823): Feature 2 check interval 1 hour(s).
20190110:035211:INFO :0:0000024D:licenseman(1823): Concurrency info:
20190110:035211:INFO :0:0000024D:licenseman(1823): There are 10 instances allowed.
20190110:035211:INFO :0:0000024D:hexane.cxx(2848): STROMASYS SA, (C) 2009-2019
20190110:035211:INFO :0:00000408:hexane.cxx(2892): CHARON-AXP (AlphaServer ES40), V 4.10 B 20200, Jan 10 2019 / 000.msc.test.center.nikolaev / 1918154109
20190110:035211:INFO :0:00000336:hexane.cxx(2924): The end user of this software has agreed to STROMASYS' Terms and Conditions for Software License and Limited Warranty, as described at: /pub/doc/30-17-033.pdf
20190110:035211:INFO :0:00000097:hexane.cxx(2999): OS Environment: Red Hat Enterprise Linux Server release 7.4 (Maipo), Linux 3.10.0-693.5.2.el7.x86_64 #1 SMP Fri Oct 13 10:46:25 EDT 2017 x86_64.

20190110:035211:INFO :0:00000098:hexane.cxx(3004): Host CPU: GenuineIntel, Family 6, Model 42, Stepping 1, Intel Xeon E312xx (Sandy Bridge), 1 Sockets, 1 Cores per Socket, 4 Threads per Core, at ~2593 MHz, 4 cpu's available
20190110:035211:INFO :0:00000099:hexane.cxx(3009): Host Memory: 3840Mb

20190110:035211:INFO :0:0000041F:hexane.cxx(3224): Configuration dump::
. session:
. . configuration_name = "AlphaServer_ES40"
. . log_method = "overwrite"
. . hw_model = "AlphaServer_ES40"
. . log_mode = "shared"
. . log_locale = "english"
. RAM:
. . size = "256"


Div
classpagebreak



Panel
borderColor#EDEDEE
bgColor#FFFFFF
titleColor#000000
titleBGColor#EDEDEE
titleCHARON-AXP log file example (part2)

. ACE:
. . num_entries = "2139"
. . num_translators = "0"
. . cache_size = "1024"
. . cache_base_size = "200"
. . host_options = " --locked-size=16"
. . enabled = "true"
. . ext_compiler = "ml64.exe"
. . ext_path = ""
. . cpu_architecture = "EV67"
. . locked_size = "16"
. cpu_0:
. . locked_size = "16"
. . wtint_idle = "true"
. cpu_1:
. . locked_size = "16"
. . wtint_idle = "true"
. cpu_2:
. . locked_size = "16"
. . wtint_idle = "true"
. cpu_3:
. . locked_size = "16"
. . wtint_idle = "true"
. ROM:
. . container = "clipper.bin"
. . dsrdb[0] = "1820"
. . dsrdb[1] = "50"
. . dsrdb[4] = "50"
. . dsrdb[11] = "1050"
. . dsrdb[12] = "1050"
. . system_name = "AlphaServer ES40 6/667"
. ISA:
. . clock_period = "10000"
. TOY:
. . container = "clipper.dat"
. COM1:
. . line = "OPA0"
. . communication = "console"
. COM2:
. . line = "(void)"
. . communication = "ascii"
. OPA0:
. . trace = "disabled"
. . stop_on = "F6"
. . tx_flush_delay = "0"
. EWA:
. . adapter_mode = "auto"
. . interface = "EWA0"
. . rx_fifo_delay_on_overload = "false"
. EWA0:
. . interface = "eth1"
. . disabled_mode = "10BaseT-HD"
. . port_show_driver_statistics = "false"
. . port_enable_mac_addr_change = "true"
. . port_snd_sock_buf_size_kb = "0"
. PKA:
. . scsi_id = "7"
. . min_n_of_threads = "0"
. . container[0] = "/home/charon/Charon/test/performancecomparison-axp.vdisk"

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

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


Div
classpagebreak


Anchor
ROTA
ROTA
Rotating log (default)

By default CHARON-AXP utilizes a so-called "rotating log" mechanism. This means that a new default log file is created each time CHARON starts and can switch to another log file if the size of the log file exceeds 64Kb (this behavior can be changed with the "set session log_file_size" and "set session log_rotation_period" parameters; see more details in the "General Settings" chapter of this guide).

...

Note

Only an existing directory can be used as a value of the "log" parameter.

Single log

Alternatively it is possible to use a single log file: uncomment the "set session log" line and specify the desired CHARON-AXP 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.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

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

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


Number of host CPUs dedicated to CHARON I/O

This setting 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). 

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Setting a specific HP Alpha model

CHARON-AXP allows to specify an exact model of HP Alpha.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Reducing number of emulated CPUs

If the CHARON host does not contain enough CPUs to emulate full range of the CPUs provided by a certain HP Alpha model, it is possible to direct CHARON-AXP to reduce the number of emulated Alpha CPUs in the configuration:

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


Setting system serial number

This parameter is used to set a specific system serial number instead of the default one:

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

TOY and ROM containers

The next objects to be configured are TOY and ROM containers (their presence depends on the HP Alpha model). It is always recommended to enable them. If a container file of the given name does not exist, CHARON-AXP 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.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


Emulated memory (RAM) size

The next parameter defines the amount of host memory the chosen CHARON-AXP model reserves for the emulation.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


Console

Mapping to system resources

The next step is the specification of the HP Alpha console (OPA0) serial line.

...

(warning) Note there are a number of additional parameters for CHARON-AXP serial lines configuration. Follow this link for details.

Exit on pressing F6 key

Despite the fact that CHARON-AXP can exit with "power off" command given in its SRM console it is also recommended to set a hot key to stop the guest from the console:

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Div
classpagebreak


Improve granularity of emulated timer

The next configuration option can be applied for improving granularity of emulated CHARON-AXP timer:

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

ATAPI CD/DVD-ROM configuration

If the sample configuration file provides this parameter, it is possible to map this particular CHARON-AXP emulator's "DQA0" CD-ROM to the host CD/DVD-ROM with the following setting:

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

AlphaStation Sound Card (AD1848) configuration

If the sample configuration file provides this parameter, it is possible to load "PCXBJ" emulator of AlphaStation Sound Card (AD1848) with the following setting:

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Networking

CHARON-AXP supports DE435, DE450, DE500AA, DE500BA, DE602 and DE602AA virtual network adapters.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Disk/tape subsystem

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

CHARON-AXP supports KZPBA and KGPSA-CA adapters.

KZPBA PCI SCSI disk/tape controller

Below is the typical configuration options for KZPBA PCI SCSI disk/tape controller:

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

KGPSA-CA PCI FC disk controller

Optionally it is possible to configure KGPSA-CA FC disk controller.

It can be configured in 2 modes:

Below is an example of KGPSA-CA controller loading:

...

Follow this link for details of KGPSA-CA controllers configuration.

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

KGPSA-CA mapping to the host resources

Below is the typical configuration options for KGPSA-CA PCI FC disk controller, mapped to the host resources ("L" is letter here):

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc


Div
classpagebreak


KGPSA-CA pass through mode

It is also possible to use the emulated KGPSA-CA in "pass through" mode to address a physical EMULEX LightPulse PCI/PCI-X/PCIe FC adapter plugged into the host’s PCI/PCI-X/PCIe slot.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Auto boot

CHARON-AXP can be configured to automatically boot an operating system at start up by specifying the default boot device and setting the 'auto_action' parameter to 'restart' from the console.

...