...

...

Alpha model specification

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

...

 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").

...

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:

...

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.

...

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.

...

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.

...

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

...

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

...

...

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:

...

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

    .
• 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.
    .
• Host tape device
  • "\\.\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:"
    .
• Other type of drive, for example magneto-optical drive
  • "\\.\<N>:"
    .

...

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:

...

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

Anchor
KGPSACA1 KGPSACA1

KGPSA-CA mapping 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.

    Warning
    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)"

    .

...

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.

...

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:

...

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.

...