Table of Contents

CHARON-VAX symbolic links

Each model of CHARON-VAX has a symbolic link 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.

For multiple instances, please 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 explained later; at this stage just pay attention to the files specified in the configuration file) and check 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 the selected configuration template from the "/opt/charon/cfg/" directory to some local file and set the correct privileges for the file to be edited.

Example:

Run the virtual machine using this configuration file:

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 distribution media provided by HP or data transfer 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 where CHARON-VAX was started, open them 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, a clean shutdown of the operating system running on the virtual machine has to be performed.

Options for running CHARON-VAX from console

If "-h" of "--help" option is specified when running CHARON-VAX from console, it displays a list of additional available options:

Usage:

  <program-name> [options] [<configuration-file-name>]

Command line options:

  -l,--log <file-name>             - write log to the file (overwrite),
                                     until configuration is loaded;
  -la,--log-append <file-name>     - write log to the file (append),
                                     until configuration is loaded;
  -f,--configuration <file-name>   - read configuration from the file;
  -d,--daemon                      - run detached;
  -h,--help                        - display this text

Note that configuration file must be supplied either as a command line
operand <configuration-file-name> or using '-f' command line option followed
by name of the configuration file.

Options to use with CHARON Manager:

  -a,--alias <alias-name>          - virtual machine alias name;
  -s,--shm-name <shm-name>         - name of shared memory section

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 install and 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" for Red Hat  Linux 6.x) to the "/usr/lib/systemd/system/" directory (or to your home directory for Red Hat Enterprise Linux 6.x).

   Example:
   $ 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.

   Example:
   ExecStart=/opt/charon/bin/mv3k6 -d /my_services/mv3k6-service.cfg
WorkingDirectory=/my_services

           
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 the following pre-requisites are met:

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

     Example:

     load virtual_serial_line OPA0 port=10003 #load operator_console OPA0

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

     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 daemons and the OPA0 console port number is unique across the CHARON server.
     
     

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

# systemctl enable mv3k6.service
# systemctl start mv3k6.service

Stopping CHARON-VAX service

To stop a CHARON-VAX daemon, use the following commands.

Example:

# systemctl stop mv3k6

Please note that before stopping a Charon-VAX service, a clean shutdown of the operating system running on the emulator has to be performed. Stopping the emulator when the guest is still running should be the last resort when all attempts to stop the guest have failed.

Removing Charon-VAX service

To remove a Charon-VAX daemon use the following commands.

Example:

# systemctl disable mv3k6.service
# rm -f /usr/lib/systemd/system/mv3k6.service

 Please note that before removing a Charon-VAX service, a clean shutdown of the operating system running 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