Versions Compared

Old Version 3

changes.mady.by.user Bruno Miretti (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Kirill Nikolaev

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
TopConfigurationPage
TopConfigurationPage
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

20150922:083215:INFO :0:000003A5:hexane.cxx(5312): session is loading built-in configuration "VAX_6610"...
20150922:083215:INFO :0:000003A6:hexane.cxx(5336): session has finished loading built-in configuration "VAX_6610".
20150922:083215:INFO :0:000003AA:hexane.cxx(5425): session is loading configuration file "vx6k610.cfg"...
20150922:083215:INFO :0:000003AB:hexane.cxx(5455): session has finished loading configuration file "vx6k610.cfg".
20150922:083215:INFO :0:000003F2:sesmgr.cxx(1394): session: default log file size limit is 4194304 bytes
20150922:083215:INFO :0:0000032B:hexane.cxx(2547): Start request received.
20150922:083216:INFO :0:000003AC:hexane.cxx(1287): session's process affinity is 000000000000000F, system affinity is 000000000000000F.
20150922:083216:INFO :0:000003D1:hexane.cxx(1541): session's I/O domain affinity is 0000000000000001, CPU domain affinity is 000000000000000E
20150922:083216:INFO :0:000003BA:ll_sentine( 725): Looking for a license key ...
20150922:083217:INFO :0:000003DC:ll_sentine( 820): ... found license key 1422726238.
20150922:083217:INFO :0:0000024D:hexane.cxx(2688): STROMASYS SA, (C) 2009-2015
20150922:083217:INFO :0:00000350:hexane.cxx(2734): CHARON-VAX (VAX 6000 Model 610), V 4.7 B 17101, Sep 22 2015 / 000.msc.sanity.tests / 1422726238
20150922:083217:INFO :0:00000336:hexane.cxx(2761): The end user of this software has agreed to STROMASYS' Terms and Conditions for Software License and Limited Warranty, as described at: http://www.stromasys.com/pub/doc/30-17-033.pdf
20150922:083217:INFO :0:0000009D:hexane.cxx(2838): License info:
CHARON product code: "CHVAX-460xx-WI".
Licensed to: "MSC".

20150922:083217:INFO :0:00000097:hexane.cxx(2847): OS Environment: Linux 3.19.8-100.fc20.x86_64 #1 SMP Tue May 12 17:08:50 UTC 2015 x86_64.
20150922:083217:INFO :0:00000098:hexane.cxx(2852): Host CPU: GenuineIntel, Family 6, Model 42, Stepping 1, Intel Xeon E312xx (Sandy Bridge), 1 Cores per Chip, 1 Threads per Core, at ~2593 MHz, 4 cpu's available
20150922:083217:INFO :0:00000099:hexane.cxx(2857): Host Memory: 4096Mb
20150922:083217:INFO :0:00000348:mscpdisk.c( 333): PUA0 is being set OFFLINE
20150922:083217:INFO :0:00000001: tpool.cxx(1370): cpu: The ACE option is omitted; enable ACE as license default.
20150922:083218:INFO :0:00000133: tpool.cxx(1602): Advanced CPU Emulation (ACE) enabled.
20150922:083218:INFO :0:0000032C:hexane.cxx(2589): "VAX_6610" started.
20150922:083300:INFO :0:00000347:mscpdisk.c(3656): PUA0 is being set ONLINE
container = "/home/charon/Charon/test/performancecomparison-66x0.vdisk"
media_type = ""
geometry = ""
use_io_file_buffering = false

...

Back to Table of Contents

Div
classpagebreak

 

Emulated memory (RAM) size

...

Back to Table of Contents

Div
classpagebreak

 

Console

Mapping to system resources

...

Type of mappingDescription
"<file-name>.vdisk"

Mapping to files representing physical disks of the VAX system (disk images). 
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, for example: "/my_disks/my_boot_disk.vdisk" 

"/dev/sd<L>"

Mapping to physical disks. "L" is letter here. Be careful not to destroy all the information from the disk dedicated to CHARON-VAX by mistake! These disks can not be formatted by the host OS.

(info) 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. 

Note

Since "/dev/

sr<N>"Mapping to CD-ROMs. There are some variants of this mapping:

sd<L>" addressing is not persistent, so it is strongly recommended to use "/dev/

cdrom<N>" or "/dev/cdrom"
"<file-name>.iso"Mapping to an ISO file for reading distribution CD-ROM images.

Numbers in the square brackets represent unit numbers associated with each container of the MSCP controller. For example, line 3 of the configuration sample above creates disk "DUA2". The maximum unit number allowed is 9999, significantly more than the original hardware provided.

...

disk/by-id/wwn-*" syntax instead to refer the disk by its WWID - especially in the enviroments utilizing FC and SAN storages (see below).

"/dev/dm-<N>"
"/dev/mapper/mpath<N>"
"/dev/mapper/disk<N>"		Mapping to multipath disk. (warning) Be careful not to destroy all the information from the disk dedicated to CHARON-VAX by mistake.  

These disks must not be formatted by the host OS.

"/dev/disk/by-*"

Mapping to physical disk.

  • by-id (addressing by the disk ID, for example "/dev/disk/by-id/ata-ST1000DM003-9YN162_S1D01QJ4")
  • by-label (addressing by the disk label, for example "/dev/disk/by-label/MyStorage")
  • by-uuid (addressing by the disk UUID, for example "/dev/disk/by-uuid/0e808a2f-cdd3-4944-a245-f729ffd73882")

(warning) Be careful not to destroy all the information from the disk dedicated to CHARON-VAX by mistake.

 These disks must not be formatted by the host OS.

"/dev/sr<N>"Mapping to CD-ROMs. There are some variants of this mapping: "/dev/cdrom<N>" or "/dev/cdrom"
"<file-name>.iso"Mapping to an ISO file for reading distribution CD-ROM images.

Numbers in the square brackets represent unit numbers associated with each container of the MSCP controller. For example, line 3 of the configuration sample above creates disk "DUA2". The maximum unit number allowed is 9999, significantly more than the original hardware provided.

It is possible to load several RQDX3 controllers DUB, DUC, etc. (see lines 6-7, above) by configuring specific addresses for them on the Qbus. Use the "CONFIGURE" utility available on the VAX console to determine the addresses. Please refer to specific HP documentation for further information.

...

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.

...

# Mapping to disk image
load virtual_scsi_disk pka_0 scsi_bus=pka scsi_id=0
set pka_0 container="<file-name>.vdisk"

# Mapping to physical disk
load virtual_scsi_disk pka_1 scsi_bus=pka scsi_id=1
set pka_1 container="/dev/sd<L>"

# Mapping to some SCSI device connected to the host
load physical_scsi_device pka_2 scsi_bus=pka scsi_id=2
set pka_2 container="/dev/sg<N>"

# Mapping to host CD-ROM or DVD-ROM
load virtual_scsi_cdrom pka_3 scsi_bus = pka scsi_id = 3
set pka_3 container = "/dev/cdrom<N>"
#set pka_3 cdrom<N>"
#set pka_3 container = "/dev/sr<N>"

# Mapping to *.ISO image
load virtual_scsi_cdrom pka_4 scsi_bus=pka scsi_id=4
set pka_4 container="<file-name>.iso"

# Mapping to tape drive
load physical_scsi_device pka_5 scsi_bus=pka scsi_id=5
set pka_5 container="/dev/sr<N>sg<N>"

# Mapping to *.ISO tape image
load virtual_scsi_cdrom tape pka_4 6 scsi_bus=pka scsi_id=46
set pka_4 6 container="<file-name>.iso"vtape"

# Include this line to get access to "PKB" adapter
include kzdda.cfg

# Mapping to tape host floppy drive
load physicalvirtual_scsi_device pkadisk pkb_5 6 scsi_bus=pka pkb scsi_id=56
set pkapkb_5 6 container="/dev/sg<N>"

# Mapping to tape image
load virtual_scsi_tape pka_6 scsi_bus=pka scsi_id=6
set pka_6 container="<file-name>.vtape"

# Include this line to get access to "PKB" adapter
include kzdda.cfg

# Mapping to host floppy drive
load virtual_scsi_disk pkb_6 scsi_bus=pkb scsi_id=6
set pkb_6 container="/dev/fd<N>" 

Note that NCR53C94 SCSI controller mapping to system resources is done via specific auxiliary objects:

Mapping ObjectDescription
virtual_scsi_disk

Mapping to a file representing VAX disk (disk image) on the host physical disk:

  • "<file-name>.vdisk"
    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, for example: "/my_disks/my_boot_disk.vdisk"
  • "/dev/sd<L>" - name of a physical disk. "L" is letter here.
    • "/dev/dm-<N>", "/dev/mapper/mpath<N>", "/dev/mapper/disk<N>" - for multipath disks. N is 0,1,2...

    fd<N>" 


    Note that NCR53C94 SCSI controller mapping to system resources is done via specific auxiliary objects:

    Mapping ObjectDescription
    virtual_scsi_disk

    Mapping to a file representing VAX disk (disk image) on the host physical disk:

    • "<file-name>.vdisk"
      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, for example: "/my_disks/my_boot_disk.vdisk"
    • "/dev/sd<L>" - name of a physical disk. "L" is letter here.
    • "/dev/dm-<N>", "/dev/mapper/mpath<N>", "/dev/mapper/disk<N>" - for multipath disks. N is 0,1,2...
    • "/dev/disk/by-id/..." - addressing by the disk ID, for example "/dev/disk/by-id/ata-ST1000DM003-9YN162_S1D01QJ4"
    • "/dev/disk/by-label/..." - addressing by the disk label, for example "/dev/disk/by-label/MyStorage"
    • "/dev/disk/by-uuid/..." - addressing by the disk UUID, for example "/dev/disk/by-uuid/0e808a2f-cdd3-4944-a245-f729ffd73882"
    • "/dev/df<N>" - name of host CD-ROM drive. N is 0,1,2... This parameter can be omitted.

    Be careful not to destroy all the information from the disk dedicated to CHARON-VAX by mistake! These disks can not be formatted by the host OS.

    Note

    Since "/dev/sd<L>" addressing is not persistent, so it is strongly recommended to use "/dev/disk/by-id/wwn-*" syntax instead to refer the disk by its WWID - especially in the enviroments utilizing FC and SAN storages.

    (info) 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.  

    physical_scsi_device

    Mapping to a host SCSI device:

    • "/dev/sg<N>" - name of the SCSI device for direct mapping, for example, a SCSI disk or tape reader.
    virtual_scsi_cdrom

    Mapping to a host CD-ROM (not only SCSI) or to ISO image:

    • "/dev/sr<N>", "/dev/cdrom", "/dev/cdrom<N>" - name of host CD-ROM drive
    • "<file-name>.iso" - name of ISO image. It may contain the full path, for example: "/my_disks/vms_distributive.iso"
    virtual_scsi_tapeMapping to a file representing tape (tape image). It may contain a path, for example: "/my_tapes/backup.vtape"

     

    Let's look at the syntax of the mapping objects. All of them have several important parameters:

    ...

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

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

    Section
    Column
    width320px

    set session affinity = ”0"0, 2, 4, 6”6"

    n_of_io_cpus

    Reserves host CPUs (of those specified by “affinity” parameter, if any) for use by the emulator for I/O handling.

    By default the emulator instance reserves one third of available host CPUs for I/O processing (round down, at least one).

    The “n_of_io_cpus” overrides the default by specifying the number of I/O host CPUs explicitly.

    Section
    Column
    width320px

    set session n_of_io_cpus = 2

    ...