Anchor | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
...
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
borderColor | #EDEDEE | |||||||||
bgColor | #FFFFFF | |||||||||
titleColor | #000000 | |||||||||
titleBGColor | #EDEDEE | title | CHARON-AXP log file example (part2)
| |||||||
Panel | ||||||||||
|
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
...
Include Page | ||||
---|---|---|---|---|
|
Div | ||
---|---|---|
| ||
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 | ||||
---|---|---|---|---|
|
...
Number of host CPUs dedicated to CHARON I/O
...
Include Page | ||||
---|---|---|---|---|
|
Div | ||
---|---|---|
| ||
Setting a specific HP Alpha model
...
The following table lists all the parameters per model:
Hardware Model | RAM size (in MB) | |||
Min | Max | Default | Increment | |
AlphaServer 400 | 64 | 1024 | 512 | 64 |
AlphaServer 800 | 256 | 8192 | 512 | 256 |
AlphaServer 1000 | 256 | 1024 | 512 | 256 |
AlphaServer 1000A | 256 | 1024 | 512 | 256 |
AlphaServer 1200 | 256 | 32768 | 512 | 256 |
AlphaServer 2000 | 64 | 2048 | 512 | 64 |
AlphaServer 2100 | 64 | 2048 | 512 | 64 |
AlphaServer 4000 | 64 | 32768 | 512 | 64 |
AlphaServer 4100 | 64 | 32768 | 512 | 64 |
AlphaServer DS10 | 64 | 32768 | 512 | 64 |
AlphaServer DS10L | 64 | 32768 | 512 | 64 |
AlphaServer DS15 | 64 | 32768 | 512 | 64 |
AlphaServer DS20 | 64 | 32768 | 512 | 64 |
AlphaServer DS25 | 64 | 32768 | 512 | 64 |
AlphaServer ES40 | 64 | 32768 | 512 | 64 |
AlphaServer ES45 | 64 | 32768 | 512 | 64 |
AlphaServer GS80 | 256 | 65536 | 512 | 256 |
AlphaServer GS160 | 512 | 131072 | 512 | 512 |
AlphaServer GS320 | 1024 | 262144 | 1024 | 1024 |
...
The goal of this configuration step is to tell CHARON-AXP what host device to use as the virtual system console. The following options are available:
Option | Description | ||
---|---|---|---|
line | Mapping to host serial line, both physical and virtual. Use the following mapping for different types of host serial lines:
| ||
port | Mapping to an IP port of the CHARON host. | ||
application | Starting some application (typically another xterm terminal) with its specific options and switches to communicate to CHARON using the IP port defined by the "port" parameter (see above) | ||
alias | Define some meaningful name for "COM1" and "COM2". Usually it is "OPA0" for "COM1" and "TTA0" for "COM2" (see below) |
...
This line provides CHARON-AXP the ability to exit by pressing the "F6" key.
...
Div | ||
---|---|---|
| ||
Improve granularity of emulated timer
...
The first line ("load KZPBA PKA") loads disk controller KZPBA with name "PKA", followed by 8 group of lines showing different ways of mapping to the host resources:
Type of mapping | Description | ||
---|---|---|---|
"<file-name>.vdisk" | Mapping to files representing physical disks of the HP Alpha system (disk images). | ||
"/dev/sd<L>" | Mapping to physical disk. "L" is letter here. Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake. These disks must not be formatted by the host OS. It is also possible to use not a whole disk, but previously created partitions on it. In this case the syntax is the following: "/dev/sd<L><N>" where N is the number of partition to be used.
| ||
"/dev/dm-<N>" | Mapping to multipath disk. Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake. These disks must not be formatted by the host OS. | ||
"/dev/disk/by-*" | Mapping to physical disk.
Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake. These disks must not be formatted by the host OS. | ||
"/dev/sg<N>" | Direct mapping to some SCSI device, for example, a SCSI disk or tape reader. How to find proper "/dev/sg" device is explained in this section. | ||
"/dev/sr<N>" | Mapping to host CD-ROM device. | ||
"<file-name>.iso" | Mapping to an ISO file for reading distribution CD-ROM image. Mapping may also include the full path (recommended), for example: "/my_disks/vms_distributive.iso" | ||
"<file-name>.vtape" | Mapping to the file representing the tape (tape image). These files are created automatically. Mapping may also include a full path (recommended), for example: "/my_tapes/backup.vtape" |
...
Numbers in the square brackets represent SCSI addresses and LUNs associated with each container of the KZBPA controller. They have the following structure:
[XXYY], where
Parameter | Range | Description |
---|---|---|
XX | 0...15 | Stands for SCSI ID of each connected unit. Note that KZPBA itself has some ID associated with it. By default it is 7, but it can be changed in the following way:
In this example an instance "PKA" of KZPBA controller is assigned with SCSI ID 0. |
YY | 00...07 | Stands for LUN. |
...
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
...
The first line ("load KGPSA FGA") loads disk controller KGPSA with name "FGA", followed by 2 groups of lines showing different ways of mapping to the host resources:
Type of mapping | Description | ||
---|---|---|---|
"<file-name>.vdisk" | Mapping to the file representing a physical disk of the HP Alpha system (disk image). These files can be created from scratch with "mkdskcmd" utility. Data and OS disk backups are transferred from the original system via tapes or network and restored into these container files. Mapping may also include the full path (recommended), for example: "/my_disks/my_boot_disk.vdisk" | ||
"/dev/sd<L>" | Mapping to physical disk. "L" is letter here Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake. These disks must not be formatted by the host OS. It is also possible to use not a whole disk, but previously created partitions on it. In this case the syntax is the following: "/dev/sd<L><N>" where N is the number of partition to be used.
| ||
"/dev/dm-<N>" "/dev/mapper/mpath<N>" "/dev/mapper/disk<N>" | Mapping to multipath disk. Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake. These disks must not be formatted by the host OS. | ||
"/dev/disk/by-*" | Mapping to physical disk.
Be careful not to destroy all the information from the disk dedicated to CHARON-AXP by mistake. These disks must not be formatted by the host OS. |
Numbers in the square brackets represent KGPSA-CA units. They can be in the range 0..32766, but no more than 255 units can be configured on a single controller.
...
Include Page | ||||
---|---|---|---|---|
|
Auto boot
CHARONCharon-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.
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:
P00>>>boot [-flags ...] [-file ...] ewa0 |
Both EW and EI adapters are supported for MOP network boot.
Include Page | ||||
---|---|---|---|---|
|