AnchorTopRunningPageTopRunningPage

Table of Contents

...

CHARON-VAX symbolic links

Use the following Each model of CHARON-VAX has a symbolic link to run different models of CHARON-VAX:defined to point to the corresponding CHARON executable (see the table below). If the PATH is correctly defined, you can start a virtual machine by specifying the link followed by the configuration file. This is described further.

...

Running CHARON-VAX emulators

It is possible to run one or several instances of CHARON-VAX at the same time if your license allows it.

In case of For multiple instances, please note to use only absolute paths and unique names to all the files referenced in the configuration file of each CHARON-VAX instance (log, toy clock, nvram files and all the other data such as disk images - all these objects will be discussed explained later; at this stage just pay attention to the files specified in the configuration file) and to specify only unique for each instance hardware devices to avoid clashing. .For examplecheck the hardware devices are used by only one instance at a time (not shared).

Example:

Please refer to the next chapters for more details concerning CHARON-VAX configuration details.

...

Running from the console

Copy required the selected configuration template from the "/opt/charon/cfg/" directory to some local file and set the correct privileges to that for the file to be able to edit itedited.

Example:

Now let's execute CHARON Run the virtual machine using this template configuration file:

You will see Below is an example of a normal VAX test sequence, followed by the prompt sign (">>>"):

The next stage can be either installation of a new VAX/VMS system using a distributive provided by HP or data transfer of data from some existing VAX system. These possibilities will be discussed in details in the next chapters.

If for some reason CHARON-VAX refuses to start, please look for files with .log extension (CHARON-VAX log files) located in the directory from which where CHARON-VAX startswas started, open them in some with an editing tool and analyze their content. In most cases those files contain very helpful information on what may possible went wrong.

To exit from the CHARON-VAX emulator use the following methods:

 Please note that before stopping CHARON-VAX, one must a clean shutdown of the operating system running by CHARON-VAX.

...

on the virtual machine has to be performed.

Running as system service (daemon)

It is possible to run CHARON-VAX as a daemon (service). In this case the CHARON-VAX process will be detached from its parent process and from the terminal window in which it runs.

Follow the description below to establish install and run execute CHARON-VAX as a daemon:

Installation and start of CHARON-VAX service

...

1. Copy the sample script "/opt/charon/bin/charon.service" ( "/opt/charon/bin/charon.service" for Fedora Core Linux ) to your home directory ( Red Hat Linux Linux 6.x) or to the "/usr/lib/systemd/system/" directory (Fedora Core), for exampleor to your home directory for Red Hat Enterprise Linux 6.x).

   Example:

   Red Hat Linux 6.x	$ cp /opt/charon/bin/charon /my_services/mv3k6_service $ chmod 755 /my_services/mv3k6_service

   Fedora Core

   Red Hat Linux 7.x and CentOS 7.x	$ cp /opt/charon/bin/charon.service /usr/lib/systemd/system/mv3k6.service $ chmod 755 /usr/lib/systemd/system/mv3k6.service

   
   

2. Edit the renamed file to replace sample values of the following parameters, for example.

   Example:

   Red Hat Linux 6.x	exec="/opt/charon/bin/mv3k6" prog="my_mv3k6" config="/my_services/mv3k6-service.cfg"

   Fedora Core

   Red Hat Linux 7.x and CentOS 7.x	ExecStart=/opt/charon/bin/mv3k6 -d /my_services/mv3k6-service.cfg WorkingDirectory=/my_services

    "my_mv3k6" is a service name in the example above

              

3. Create and edit the configuration file ("/my_services/mv3k6-service.cfg" in the examples above) the way it was described before and make sure that the following pre-requisites are met:

   • OPA0 must be configured as a virtual port or physical console, not as an operator console, for example.

     Example:

     load virtual_serial_line OPA0 port=10003 #load operator_console OPA0

     div

     class	pagebreak

      

     
     

   • Use only absolute paths to log, toy clock, nvram files and all the other data such as disk images, etc. The names of the references files must be unique too, for example.

     Example:

     ... set session log="/my_services/my_mv3k6.log" set toy container="/my_services/my_mv3k6.dat" load RQDX3/RQDX3 DUA set DUA container[0]="/my_services/mv3k6_daemon_boot_disk.vdisk" ...

     
     

   • Make sure the same physical devices are not used by other CHARON-VAX daemon, same for daemons and the OPA0 console port number is unique across the CHARON server.
     
     

Once configuration file is ready issue , execute the following commands (the specifics belongs to based on the examples above) to install and start CHARON-VAX as a daemon:

Red Hat Linux 6.x	# ln -sf /my_services/mv3k6_service /etc/init.d/mv3k6_service # chkconfig mv3k6_service on # service mv3k6_service start

Fedora Core

Red Hat Linux 7.x and CentOS 7.x	# systemctl enable mv3k6.service # systemctl start mv3k6.service

Info
title Red Hat Linux 7.x and CentOS 7.x
If you update the /usr/lib/systemd/system/<my virtual machine>.service file, the following command must be executed in order to take changes into account: # systemctl daemon-reload

Warning

Note that a certain delay may appear in finding network license licenses by Sentinel Run-time on CHARON-VAX host system startup. So if If the CHARON-VAX service is starting automatically on at host system startup, it may report a "License not found" error and exit. This problem can be avoided by specifying the "license_key_lookup_retry" parameter in the following way: set session license_key_lookup_retry = "N [, T]" where: N - = Number of retries looking for the license key (or keys) T - = Time between retries in seconds. If not specified, 60 seconds is used Example: set session license_key_lookup_retry = 5 In this example, if the license key is not found during initial scan, CHARON-VAX will do 5 more attempts waiting 60 seconds between them. See General Settings section for more details.

 

...

Include Page
KBCOMMON:DOC-GoToToc KBCOMMON:DOC-GoToToc

Div
class pagebreak

Stopping CHARON-VAX service

To stop a CHARON-VAX daemon, use the following command, for examplecommands.

Example:

Please note that before stopping a CHARON-VAX service, one must  a clean shutdown of the operating system running by CHARON-VAX. 

Back to Table of Contents 

on the virtual machine has to be performed.

Removing CHARON-VAX service

To remove a CHARON-VAX daemon use the following commands, for example.

Example:

 Please note that before removing a CHARON-VAX service one must shutdown , a clean shutdown of the operating system running by CHARON-VAX and then stop corresponding CHARON-VAX service. on the virtual machine has to be performed and the service has to be stopped.

Please refer to the next chapters for more details concerning CHARON-VAX configuration details

...