| Anchor | ||||
|---|---|---|---|---|
|
...
|
| Div | ||
|---|---|---|
| ||
|
The goal of this configuration step is to tell CHARON-VAX what host device to use as the virtual system console. The following options are available:
...
CHARON-VAX supports MSCP, DSSI, CI and SCSI disk controllers. The examples below are for MSCP and SCSI controllers only. DSSI controllers are discussed in details in the following section, CI controllers - in this section.
| Div | ||
|---|---|---|
| ||
|
MSCP disk controllers (RQDX3, KDB50, KDM70)
...
Follow this link for details of (T)MSCP controllers configuration.
Back to Table of Contents
SCSI controller NCR53C94
The VAX 4000 and MicroVAX 3100 have an NCR53C94 SCSI controller onboard for support of different types of SCSI devices including disks and tapes. Optionally a second controller can be added.
| Div | ||
|---|---|---|
| ||
|
Below is a typical configuration template for a preloaded "PKA" NCR53C94 SCSI controller:
...
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.
“Affinity” overrides the default and allows explicit specification of which host CPUs will be used by the instance. Affinity does not reserve the CPU for exclusive use.
Example:
set session affinity = "0, 2, 4, 6" |
...