Anchor | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
...
The following table shows all the parameters:
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, "COM<n>:". |
port | Mapping to an IP port of the CHARON host. |
application | Starting some application (typically terminal emulator) 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) |
The second console line "TTA0" can be also optionally configured (for 1 CPU models such as HP AlphaServer 400, HP AlphaServer 800, HP AlphaServer 1000, HP AlphaServer 1000A, HP AlphaServer DS10, HP AlphaServer DS10L and HP AlphaServer DS15):
...
Note |
---|
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:
|
Follow this link for more details of CHARON-AXP network controllers configuration.
...
- 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.Warning 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.
.
- "\\.\PhysicalDrive<N>"
- 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)"
.
- "\\.\PhysicalDrive(DevID =XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX)"
- 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>"
.
- "\\.\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.
.
- "<file-name>.iso"
- Host tape device
- "\\.\Tape<N>"
.
- "\\.\Tape<N>"
- File representing the tape (tape image)
"<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 Using compressed folders to store virtual disks and tapes is not supported
.
- Floppy drive
- "\\.\A:"
.
- "\\.\A:"
- Other type of drive, for example magneto-optical drive
- "\\.\<N>:"
.
- "\\.\<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
Parameter | Range | Description |
---|---|---|
XX | 0...15 | Stands for SCSI ID of each connected unit. Note that the 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 on the KGPSA-CA controllers configuration.
Include Page KBCOMMON:DOC-GoToToc KBCOMMON:DOC-GoToToc
Div | ||
---|---|---|
| ||
Anchor | ||||
---|---|---|---|---|
|
...
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".
Type of mapping | Description |
---|---|
storage_controller_path_id = <Storage controller path ID> | "Storage controller path ID" is a storage (for example SAN) controller path ID. This ID can be obtained from the special utility "Device check tool" (accessible in the "Host Information and Utilities" section of the CHARON Virtual Machine Manager). Once specified, all the disks attached to the storage are automatically mapped as disk units to the CHARON VM. |
...
The "host_bus_location" parameter addresses the host EMULEX LightPulse PCI/PCI-X/PCIe FC adapter in the following way:
Parameters | Description |
---|---|
"PCI bus X" | PCI bus number of the host EMULEX LightPulse PCI/PCI-X/PCIe FC adapter |
"device Y" | PCI bus device number of the host EMULEX LightPulse PCI/PCI-X/PCIe FC adapter |
"function Z" | The "function" parameter of the the host EMULEX LightPulse PCI/PCI-X/PCIe FC adapter |
...
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:
Supported | Not Supported | Not tested |
---|---|---|
LP8000 | LPe1150 (FC2142SR, A8002A) | LPe11000 |
...
The "host_bus_location" parameter addresses the host DEFPA FDDI adapter in the following way:
Parameters | Description |
---|---|
"PCI bus X" | PCI bus number of the host DEFPA FDDI adapter |
"device Y" | PCI bus device number of the host DEFPA FDDI adapter |
"function Z" | The "function" parameter of the the host DEFPA FDDI adapter |
...
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:
load PBXDA_AC/DIGI TXA |
The adapter instance name ("TXA
" in the example above) is used then for parametrization, for example:
set TXA line[2]="COM1:" |
The numbers in the square brackets represent line number on the virtual PBXDA adapter starting from 0.
Controller type | Maximum number of lines |
---|---|
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.
...
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:
DEC PBXDA-xx adapter | Name of the device to map to | Controller | Vendor ID | Device ID |
---|---|---|---|---|
PBXDA-BA | DIGI AccelePort 4r 920 | ASIC PCI | 114Fh | 0026h |
PBXDA-BB | DIGI AccelePort 8r 920 | ASIC PCI | 114Fh | 0027h |
PBXDA-AC | DIGI AccelePort Xem | ASIC PCI | 114Fh | 0004h |
PBXDA-AC | DIGI AccelePort Xem | ASIC PCI | 114Fh | 0008h |
...
The "host_bus_location" parameter addresses the host DIGI adapter in the following way:
Parameters | Description |
---|---|
"bus X" | PCI bus number of the host DIGI adapter |
"device Y" | PCI bus device number of the host DIGI adapter |
"function Z" | The "function" parameter of the the host DIGI adapter |
...