| Include Page |
|---|
| KBCOMMON:KB-CSSstyle |
|---|
| KBCOMMON:KB-CSSstyle |
|---|
|
Table of Contents
Creation of CHARON VM configuration
When a CHARON Virtual Machine (VM) is created from a template using the CHARON Virtual Machines Manager, it has to be updated to meet the desired configuration.
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
HP Alpha model specification
The first configuration statement is the specification of the exact HP Alpha hardware model to emulate, for example:
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
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:
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
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.
...
set session log_method = append
#set session log_method = overwrite
#set session log = "AlphaServer_ES40.log"
|
Rotating log (default)
By default the CHARON VM 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 if the size of the log file exceeds 64Kb (previous log files are kept).
...
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.
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
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.
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
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).
...
| 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.
...
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:
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
Setting system serial number
If necessary, a specific system serial number instead of the default one:
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
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.
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
Emulated memory (RAM) size
The next parameter defines the amount of host memory the CHARON VM reserves for the emulation:
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
Console
Mapping to system resources
The next step is the specification of the HP Alpha console (OPA0) serial line.
...
#set COM2 alias = TTA0 line = "COM2:"
#set COM2 alias = TTA0 port = 10000
#set COM2 alias = TTA0 port = 10000 application = "tta0.ht"
set COM2 alias = TTA0 port = 10000 application = "putty -load TTA0 -P 10000"
#set COM2 alias = TTA0 port = 10000 application = "c:\kea\user\tta0.ktc"
|
Note that additional parameters for the CHARON VM serial lines configuration can be added. Follow this link for details.
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):
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
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 VM emulator's "DQA0" CD-ROM to the host CD/DVD-ROM 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 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:
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
KGPSA-CA PCI FC disk controller
Optionally it is possible to configure KGPSA-CA FC disk controllers.
...
Follow this link for details on the KGPSA-CA controllers configuration.
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
KGPSA-CA mapping to the host resourcesBelow is the typical configuration options for a KGPSA-CA PCI FC disk controller, mapped to the host resources:
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
KGPSA-CA mapping to a storage controller using its "presentation" modeSome storage controllers allows CHARON VM to use their resources using so called "presentation" mode.
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
KGPSA-CA pass through modeIt 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 |
|---|
|
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:
...
| Include Page |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
| KBCOMMON:DOC-GoToToc |
|---|
|
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:
#load PBXDA/DIGI <name>
#load PBXDA_BA/DIGI <name>
#load PBXDA_BB/DIGI <name>
#load PBXDA_AC/DIGI <name>
|
Example:
The adapter instance name ("TXA" in the example above) is used then for parametrization, for example:
set TXA line[2]="COM1:"
set TXA port[3]=1706
|
The numbers in the square brackets represent line number on the virtual PBXDA adapter starting from 0.
| PBXDA | 2 |
| PBXDA_BA | 4 |
| PBXDA_BB | 8 |
| PBXDA_AC | 16 |
It is possible to specify either physical port ("COM<n>") or an IP port for connecting the virtual PBXDA-xx to system resources. No other parameters are applicable in this type of emulation.
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:
...
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 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.
...