...
- The first part of the menu displays server information: server boot time, number of CPUs and Memory Free / Total.
The second part displays the list of virtual machines (guests) managed. Column details:
Column Description Emulator/Config File Emulator used with its configuration file name (shortened) CPU Displays the number of CPUs by looking into configuration file settings (set n_of_cpus ...) first then using default value for the selected hardware. If no information is available, "-" is displayed instead.
The number of CPUs displayed does represent the number defined in the configuration file or the default number of cpus for this hardware model. The real number of CPUs the virtual machine owns depends on the CHARON server hardware limitations, CHARON licenses and also licenses on the virtual machine side (Tru64 or OpenVMS)Mem Displays the amount of memory defined in the configuration file (if defined). If no information is available, "-" is displayed instead. State - For Red Hat 6
- can be either RUNNING, STARTING, STARTING/ALL (if all guests have been started at the same time), STOPPED.
- If the guest is in STOPPED state, an additional information will be displayed:
- REQUESTED: the service has been stopped by user request or has not been started on Linux server boot due to boot parameter set to off
- FAILURE: the guest process failed
- For Red Hat 7 and Fedora (using both
systemd)- can be either ACTIVE, ACTIVATING, INACTIVE, DEACTIVATING, FAILED or UNKNOWN
- If the guest is in STOPPED state, an additional information will be displayed:
- REQUESTED: the service has been stopped by user request or has not been started on Linux server boot due to boot parameter set to off
- FAILURE: the guest process failed
Stop script Displays the status of the stop script used to perform a clean shutdown of the guest. Can be:
- Not found: the script has not been created. If not found, a service stop request will induce a kill of the emulator process
- To customize: the script exists and a case line has been added for the specified configuration file. It must however be customized with some commands to perform a clean shutdown of the guest (OpenVMS or Tru64 virtual machine).
For more information and examples, see Service management - Create/Edit guest stop script
- Case not set : the script exists but does not relate to the specified configuration file. This means it has either been created manually or initialized automatically by the menu and a new guest has been added after initialization.
B Displays the automatic boot on server startup value, Yes or No. This means the CHARON virtual machine will be started. To automatically boot the virtual machine on startup, please refer to the CHARON-AXP or CHARON-VAX users guides and console settings..
- For Red Hat 6
Depending on settings and virtual machine state, more information can be displayed
- Auto-restart settings (feature managed by
systemd, described here: XXXXXXXXXXXXXXXXX How to restart CHARON-VAX/AXP on Linux automatically on failure ) - Description (not available on Red Hat Enterprise Linux 6.x)
- Start date
- Guest OS response (optional, see Service management - Create/Edit guest stop script / Optional guest display status script)
- Network Interfaces settings
.
- Auto-restart settings (feature managed by
...
Enabling auto restart on failure is managed by systemd and is described here: How to restart CHARONCharon-VAX/AXP on Linux automatically on failure
...