...
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.
Link name | Emulator to run |
mv3k196 | MicroVAX 3100 Model 96 |
mv3k198 | MicroVAX 3100 Model 98 |
mv3k6 | MicroVAX 3600 |
mv3k9 | MicroVAX 3900 |
mvii | MicroVAX II |
vs4k90 | VAXStation 4000 Model 90 |
vx3k6 | VAXserver 3600 |
vx3k6_128 | VAXserver 3600 (128Mb of RAM is available) |
vx3k6_512 | VAXserver 3600 (512Mb of RAM is available) |
vx3k9 | VAXserver 3900 |
vx3k9_128 | VAXserver 3900 (128Mb of RAM is available) |
vx3k9_512 | VAXserver 3900 (512Mb of RAM is available) |
vx4k106 | VAX 4000 Model 106 |
vx4k108 | VAX 4000 Model 108 |
vx4k700 | VAX 4000 Model 700 |
vx4k705 | VAX 4000 Model 705 |
vx6k310 | VAX 6310 |
vx6k610 | VAX 6610 |
vx6k620 | VAX 6620 |
vx6k630 | VAX 6630 |
vx6k640 | VAX 6640 |
Div | ||
---|---|---|
| ||
Link name | Emulator to run |
---|---|
vx6k650 | VAX 6650 |
vx6k660 | VAX 6660 |
...
class | pagebreak |
---|
Running CHARON-VAX emulators
...
The next stage can be either installation of a new VAX/VMS system using a distributive distribution media provided by HP or data transfer from some existing VAX system. These possibilities will be discussed in details in the next chapters.
...
To exit from the CHARON-VAX emulator use the following methods:
Configuration | How to exit |
---|---|
No change to the template configuration file (not recommended) | Kill the console from where CHARON runs (CTRL-C for example) or kill the CHARON process |
Enable "F6" button in configuration file to trigger exit from CHARON:
| Press the "F6" key |
Please note that before stopping CHARON-VAX, a clean shutdown of the operating system running on the virtual machine has to be performed.
...
Include Page | ||||
---|---|---|---|---|
|
Div | ||
---|---|---|
| ||
Running as system service (daemon)
...
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:
Red Hat Linux 6.x $ cp /opt/charon/bin/charon /my_services/mv3k6_service
Red Hat Linux 8x, 7.x and CentOS 8x, 7.x $
chmod 755 /my_services/mv3k6_service$
cp /opt/charon/bin/charon.service /usr/lib/systemd/system/mv3k6.service
$ chmod 755 /usr/lib/systemd/system/mv3k6.service
Edit the renamed file to replace sample values of the following parameters.
Example:
Red Hat Linux 8.x, 7.x and CentOS 8.x, 7.xRed Hat Linux 6.x exec="/opt/charon/bin/mv3k6"
prog="my_mv3k6"
config="/my_services/mv3k6-service.cfg"
"my_mv3k6" is a service name in the example aboveExecStart=/opt/charon/bin/mv3k6 -d /my_services/mv3k6-service.cfg
WorkingDirectory=/my_services
- 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 OPA0Use 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.
Div | ||
---|---|---|
| ||
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
...
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 licenses by Sentinel Run-time on CHARON-VAX host system startup. If the CHARON-VAX service is starting automatically 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:
where:
Example:
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. |
...
To stop a CHARON-VAX daemon, use the following commands.
Example:
...
#
...
systemctl stop mv3k6
Please note that before stopping a CHARONCharon-VAX service, a clean shutdown of the operating system running on the virtual machine 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.
Include Page | ||||
---|---|---|---|---|
|
Removing
...
Charon-VAX service
To remove a CHARONCharon-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 CHARONCharon-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 CHARONCharon-VAX configuration details
...