Anchor | ||||
---|---|---|---|---|
|
...
CHARON-AXP symbolic links
Use the following Each model of CHARON-AXP has a symbolic link to run different models of CHARON-AXP: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 |
as400 | AlphaServer 400 |
as800 | AlphaServer 800 |
as1000 | AlphaServer 1000 |
as1000a | AlphaServer 1000A |
as2000 | AlphaServer 2000 |
as2100 | AlphaServer 2100 |
as4000 | AlphaServer 4000 |
as4100 | AlphaServer 4100 |
ds10 | AlphaServer DS10 |
ds10l | AlphaServer DS10L |
ds15 | AlphaServer DS15 |
ds20 | AlphaServer DS20 |
ds25 | AlphaServer DS25 |
es40 | AlphaServer ES40 |
es45 | AlphaServer ES45 |
gs80 | AlphaServer GS80 |
gs160 | AlphaServer GS160 |
gs320 | AlphaServer GS320 |
...
For multiple instances, please use only absolute paths and unique names to all the files referenced in the configuration file of each CHARON-AXP instance (log, toy clock, rom files and all the other data such as disk images ([Exception: clustering) ] - all these objects to will be discussed explained later in this document). Also, and check the hardware devices (e.g., CD-ROM) may be the CDROM drive for example) are used by only one instance at a time (not shared).
For exampleExample:
|
...
Copy the sample script "
/opt/charon/bin/charon.service
" ( "/opt/charon/bin/charon
" for Red Hat Linux 6.x) to "/usr/lib/systemd/system/
" directory (or to your home directory (Red Hat Linux 6.x)), for example:Red Hat Linux 6.x $ cp /opt/charon/bin/charon /my_services/es40_service
$ chmod 755 /my_services/es40_service
Red Hat Linux 7.x and CentOS 7.x $ cp /opt/charon/bin/charon.service /usr/lib/systemd/system/es40.service
$ chmod 755 /usr/lib/systemd/system/es40.service
Edit the renamed file to replace sample values of the following parameters, for example:
Red Hat Linux 6.x exec="/opt/charon/bin/es40"
prog="my_es40"
config="/my_services/es40-service.cfg"
Red Hat Linux 7.x and CentOS 7.x ExecStart=/opt/charon/bin/es40 -d /my_services/es40-service.cfg
WorkingDirectory=/my_services
"my_es40" is a service name in the example above
- Create and edit the configuration file ( "
/my_services/es40-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 virtual port or physical console, not as operator console, for 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 too, for example
...
set session log="/CharonInstances/1st_es40.log"
set rom container="/CharonInstances/1st_es40.bin"
set toy container="/CharonInstances/1st_es40.dat"set PKA container[0]="/CharonInstances/1st_es40_boot_disk.vdisk"
...
- Make sure the same physical devices are not used by other CHARON-AXP daemons, same for the OPA0 console port number.
...
Once the configuration file is ready run the following commands (from the examples above) to install and start CHARON-AXP as daemon:
Red Hat Linux 6.x |
|
---|---|
Red Hat Linux 7.x and CentOS 7.x |
|
...
To stop a CHARON-AXP daemon use the following command, for example:
Red Hat Linux 6.x |
|
---|---|
Red Hat Linux 7.x and CentOS 7.x |
|
Please note that before stopping CHARON-AXP service, one must shutdown the operating system running in CHARON-AXP.
...
To remove a CHARON-AXP daemon use the following commands, for example:
Red Hat Linux 6.x |
|
---|---|
Red Hat Linux 7.x and CentOS 7.x |
|
...