Table of Contents

Creation of CHARON VM configuration

When a CHARON Virtual Machine (VM) is created from a template using the CHARON Virtual Machines Machine Manager, it has to be updated to meet the desired configuration.
This configuration is represented as a text file ("configuration file") containing some specific keywords to define the main settings such as the text-based configuration file is copied from a template file. This configuration file must be customized for your specific configuration. The configuration file consists of directives written in the Charon-AXP "configuration syntax" which define all aspects of the emulated system, including 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 location of various associated files, to name some examples.

To edit the configuration file, open the CHARON Virtual Machines Machine 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 Removed

Image Added

Notepad will be used to edit the configuration file:

...

...

Alpha model specification

The first configuration statement is the specification of the exact HP Alpha hardware model to emulate, for example:

You must leave this line untouchedThis line must not be changed.

 If you create the CHARON VM 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. 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 = <...>" syntax:

...

• The configuration name is reported in the log file and is used to set the log file name for rotating log (see explanations further).
• Changing the configuration name in the "configuration_name.icfg" file does not change the name of the virtual machine at Virtual Machines Machine 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.

...

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 operations: 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, plus the license number, 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 the CHARON VM default CHARON utilizes a so-called "rotating log" methodmechanism. 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 keptthis 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).

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.

...

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 a single log file. Uncomment the "set session log" line and specify the desired log file name. Optionally, a path can be added to the log file name.

...

CPU affinity

This setting binds the running CHARON VM CPUs to particular host CPUs.This should be used for soft partitioning host CPU resources or for isolating multiple CHARON VMs on the same host from each other. By default the emulator instance allocates as many host CPUs as possible.

...

 Note that the number of the specified host CPUs must correspond to the number of the emulated CPUs (one host CPU for one emulated CPU; this value is specific for each HP Alpha model) and number of CPUs needed for CHARON application itself ("n_of_io_cpus").

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 CHARON VM for I/O handling. By default CHARON VM reserves one third of available host CPUs for I/O processing (round down, at least one). 

...

The example above directs CHARON VM to use 2 host CPUs for CHARON I/O operations.

 Note that the number of the specified CPUs dedicated to CHARON VM I/O operations must correspond to the total number of available for CHARON CPUs (restricted by "affinity" parameter if needed) and the number of the virtual HP Alpha CPUs to be emulated.

Setting a specific

...

Alpha model

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

For example for HP AlphaServer ES40 family the template configuration file contains the following options:

Just uncomment the provided lines to apply a certain model (It is "AlphaServer ES40 6/667" in the example above).

The full description of the parameters and other models that can be also configured is available in the "Configuration details" chapter of this User's Guide.

...

...

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 the CHARON VM to reduce the number of emulated Alpha CPUs:

...

This parameter can also be used to avoid warning messages in the log if the number of CPUs allowed by the license is less than the default number of CPUs of the emulated HP Alpha model.

Setting system serial number

If necessary, a specific system serial number instead of the default one:

...

TOY and ROM containers

The TOY and ROM containers have to be configured. 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, starting the CHARON VM will create it.

...

Emulated memory (RAM) size

The next parameter defines the amount of host memory the CHARON VM reserves for the emulation:

...

The amount of RAM is specified in MB. It cannot exceed or be lower than certain values specific for each HP Alpha model. It is very important to keep the listed predefined increment between possible memory values.

The following table shows all the parameters:

...

Note that in some particular orders your license may restrict the maximum RAM amount of each HP Alpha model.

Console

Mapping to system resources

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

...

Exit on pressing F6 button

Despite the fact that the CHARON VM can stop with the "power off" command entered at SRM console level, it is recommended to set a hot key to stop the VM from the console (when the console is accessed remotely for example)The following directive configures the emulator to exit immediately when the F6 key sequence is sent to the emulator console:

This line allows the CHARON VM to be stopped by pressing the "F6" key.

...

means that if the F6 key is pressed in the terminal emulator being used to connect to the console (PuTTY, for example), the emulator will exit immediately.

Please note that the emulator can be stopped when at the SRM prompt ("P00>>>") by type power off, as well as from the Virtual Machine Manager. To shut down the guest safely, Stromasys recommends the following procedure:

• Shut down the guest OS (OpenVMS/Tru64 UNIX)
• Wait for the SRM prompt ("P00>>>")
• Type power off at the SRM prompt
• The connection to the console will be lost when the emulator exits, which means the terminal emulator window will probaly disappear.
• At this point you can stop or restart the emulator host safely

Stromasys does not recommend enabling this feature. It means that any person (or software) which connects to the console port on the emulator host can stop the emulator and thus "pull the virtual power cable" from the OpenVMS or Tru64 UNIX guest. In particular, many organizations have deployed automated port scanners in their datacenters to discover open ports on the systems in the network. Many such port-scanning solutions, if they are able to connect to an open port, will next try to send data to the port. In many cases this data can be interpreted as the stop sequence and cause the emulator to exit.

If you must allow incoming connections to the console port, you should configure the Windows firewall with a "whitelist" of IP addresses from which such connections are allowed, and disallow all other addresses.

Improve granularity of emulated timer

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

...

ATAPI CD/DVD-ROM configuration

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

...

Networking

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

...

Some network adapters available in CHARON-AXP are preloaded (for example, HP AlphaServer DS15 contains 2 preloaded adapters EWA and EWB), so their configuration in CHARON VM is even more simple:

...

Please note:

• CHARON supports VLAN adapters. If used, proceed with their installation and configuration according to the network adapter vendor User's Guide and then use the resulting VLAN interface the same way as the regular network interface. 

...

• The AlphaServer DS15 and DS25 contain two built-in PCI Ethernet adapters. Models and names (EI* or EW*) of them depend on configuration addon. Choose one of the two or none, but not both. The first instantiates onboard network interfaces as EIA and EWA. While the second - EWA and EWB (enabled by default for backward compatibility)

  Example:

  #include ds25-onboard-nics.icfg
include ds25-onboard-nics-ew.icfg

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

Disk/tape subsystem

The disk and tapes subsystems and the mapping to the system resources can be done 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 the KZPBA PCI SCSI disk/tape controller:

...

• File representing a physical disk of the HP Alpha 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, for example: "C:\My disks\my_boot_disk.vdisk". If the path is not specified, the disk images are expected to be in the CHARON VM home directory.

    WarningUsing

    Important note: using compressed folders to store virtual disks and tapes is not supported

    .

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

    .
• 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:

    set PKA container[100]="\\.\PhysicalDrive(DevID= 6008-05F3-0005-2950-BF8E-0B86-A0C7-0001)"

    .

• iSCSI disks

  • "\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)"
    
    

    Parameter	Description
    iScsiTarget	Addresses the disk by its iSCSI target name.
    LUN	Specifies the LUN on the connected iSCSI disk.

    Example:

    Div class small set PKA container[200]="\\.\PhysicalDrive(iScsiTarget= iqn.2008-04:iscsi.charon-target-test1, LUN= 1)"

    .

• SCSI device unknown to Windows for direct mapping, for example, a SCSI disk or tape reader

  • "\\.\Scsi<N>:<X>:<Y>:<Z>"
    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

    .

• CD-ROM device
  • "\\.\CdRom<N>"
    .
• ISO file for reading distribution CD-ROM image

  • "<file-name>.iso"
    Mapping may also include the full path, for example: "C:\My disks\vms_distributive.iso". If the path is not specified, the CD-ROM images are expected to be in the CHARON VM home directory.

    Div
    class pagebreak

    
    .

• Host tape device
  • "\\.\Tape<N>"
    .
• File representing the tape (tape image)
  • Using

    "<file-name>.vtape"
    These files are created automatically.
    Mapping may also include a full path, for example: "C:\My tapes\backup.vtape". If the path is not specified, the tape images are expected to be in the CHARON VM home directory.
    

    Warning

    
    

    Important note: using compressed folders to store virtual disks and tapes is not supported.
    

    .

• Floppy drive
  • "\\.\A:"
    .
• Other type of drive, for example magneto-optical drive
  • "\\.\<N>:"
    .

...

The numbers in the square brackets represent the SCSI addresses and LUNs associated with each container of the KZBPA controller. They have the following structure:

[XXYY], where:

It is possible to load several KZPBA controllers: DKB, DKC, etc. by configuring specific placement for them on the PCI bus. It is discussed in details in the "Configuration details" chapter of this Guide.

Some HP Alpha systems emulated by CHARON-AXP have already one or two KZPBA controllers pre-loaded. If the system has only one preloaded controller, the template configuration file usually provides some sample line on how to add another one. For example:

...

KGPSA-CA PCI FC disk controller

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

They can be configured in 3 modes:

• Direct mapping to the host resources
• Usage of "presentation mode" of connected or external storage controllers
• Pass Through mode

Below is an example of a KGPSA-CA controller loading:

...

Follow this link for details on the KGPSA-CA controllers configuration.

Anchor
KGPSACA1 KGPSACA1

KGPSA-CA mapping to the host resources

Below is the typical configuration options for a KGPSA-CA PCI FC disk controller, mapped to the host resources:

...

• File representing a physical disk of the HP Alpha 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, for example: "C:\My disks\my_boot_disk.vdisk". If the path is not specified, the disk images are expected to be in the CHARON VM home directory.

    WarningUsing

    Important note: using compressed folders to store virtual disks and tapes is not supported.

    .

• Physical disk
  • "\\.\PhysicalDriveN"
    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.
    .

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

    set PKA container[100]="\\.\PhysicalDrive(DevID= 6008-05F3-0005-2950-BF8E-0B86-A0C7-0001)"

    .

• iSCSI disks

  • "\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)"
    iScsiTarget addresses the disk by its iSCSI target name. LUN specifies LUN on the connected iSCSI disk.

    Example:

    Div class small set PKA container[200]="\\.\PhysicalDrive(iScsiTarget= iqn.2008-04:iscsi.charon-target-test1, LUN= 1)"

    .

...

Anchor
KGPSACA2 KGPSACA2

KGPSA-CA mapping to a storage controller using its "presentation" mode

Some storage controllers allows CHARON VM to use their resources using so called "presentation" mode. 

...

This line loads an instance of KGPSA-CA controller and maps it to some external controller having ID "5008-05F3-0005-2950-5008-05F3-0005-2951".

...

Anchor
KGPSACA3 KGPSACA3

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.

...

The "host_bus_location" parameter addresses the host EMULEX LightPulse PCI/PCI-X/PCIe FC adapter in the following way:

...

The following is the list of EMULEX LightPulse PCI/PCI-X/PCIe FC adapters supported by the CHARON-AXP PCI Pass Through driver and suitable for the emulation of a KGPSA-CA PCI FC adapter in CHARON PCI Pass Through mode:

FDDI support via DEFPA PCI FDDI controller in "pass through" mode

Optionally it is possible to configure a DEFPA PCI FDDI controller in "pass through" mode, mapped to a physical DEFPA FDDI adapter installed on the host:

...

Pay attention to the proper placement of the emulated DEFPA adapter on the virtual HP Alpha PCI bus (it is controlled by "bus", "device", "function", "irq" and "irq_bus" parameters). Refer to this chapter of this Guide for more information.

The "host_bus_location" parameter addresses the host DEFPA FDDI adapter in the following way:

...

Serial lines support via emulated PBXDA-xx family PCI controllers

Optionally it is possible to configure the folIowing models of PBXDA-xx family controllers.

VIrtual PBXDA-xx

Syntax for loading PBXDA-xx family serial lines adapters:

Example:

The adapter instance name ("TXA" in the example above) is used then for parametrization, for example:

PBXDA-xx support in "pass through" mode

In "pass through" mode PBXDA-xx family controllers are mapped to specific models of the physical DIGI serial lines adapters installed on the CHARON VM host:

...

Pay attention to the proper placement of the emulated PBXDA-xx adapter on the virtual HP Alpha PCI bus (it is controlled by "bus", "device", "function", "irq" and "irq_bus" parameters). Refer to this chapter of this Guide for more information.

The "host_bus_location" parameter addresses the host DIGI adapter in the following way:

...

Now it is possible to collect the parameters for CHARON VM mapping to the DIGI host adapter.

...

Open the “Computer Management” application and select “Device Manager”:

...

 Non-US-EN installations of Windows may present “Location:” string in local language, but "host_bus_location" parameter requires English notation, so the words “PCI”, “bus”, “device”, and “function” must be specified in English.

...

Auto boot

The CHARON VM Charon-AXP can be configured to automatically boot an operating system at start up immediately after it has started by specifying the default boot device and setting the 'auto_action' parameter to 'restart' from the console.

Example: dka0 is defined as the default boot device

Network boot

Charon-AXP  can be configured to boot on network if the legacy operating system allows it via MOP. MOPv3 (DECnet) and MOPv4 (LANCP) are supported.

Usage/example:

Both EW and EI adapters are supported for MOP network boot.