Page Comparison

...

Creation of CHARON VM configuration

Once you have created When a CHARON Virtual Machine (VM) in CHARON Virtual Machine Manager using some template you should update this sample template is created from a template using the CHARON Virtual Machines Manager, it has to be updated to meet the desired configuration of your HP Alpha.

This configuration is represented as a text file ("configuration file") containing some specific keywords to define the HP Alpha main settings such as amount of memory, number of CPUs, peripheral devices as well as specifics of CHARON VM executions such as name of VM log file, number of host CPUs used for emulation, etc.

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

Edit the CHARON VM configuration using the default text editorNotepad will be used to edit the configuration file:

Back to Table of Contents

...

You must leave this line untouched.

If you create the CHARON 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 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:

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

See example below with configuration name set to: MicroVAX_3100_Model_98

Back to Table of Contents

Log file parameters

Execution 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 possible problems with either with the running CHARON 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 the problem resolution.

Here is an example of a CHARON VM log file:

...

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

Rotating log (default)

By default CHARON utilizes 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 can switch to another log file 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.

Names The names of the rotating log files are composed as follows:

...

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 just a single log file. Uncomment the "set session log" line and specify the desired CHARON 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.

...

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

Back to Table of Contents

SCSI controller NCR53C94

...