...
- The first part of the menu displays server information: server boot time, number of CPUs and Memory Free / Total.
- This description is valid for all menu options displaying the virtual machines list and for the "
vmlist" command line. The second part displays the list of virtual machines (guests) managed. Column details:
Column Description Emulator
Emulator used Configuration File 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)Memory 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 VM 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.
- [Using XXX] where XXX can be EXPECT, RSH or SSH: the script exists and a case line has been added for the specified configuration file and it uses the shutdown scripts provided with the kit
- Customized : a customized script or command lines is/are used
OnBoot 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: How to restart Charon-VAX/AXP on Linux automatically on failure ) - Service start and/or stop timeouts
- Description (not available on Red Hat Enterprise Linux 6.x as it is defined in the
systemdservice) - Start/stop date
- 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 VM 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.
- [Using XXX] where XXX can be EXPECT, RSH or SSH: the script exists and a case line has been added for the specified configuration file and it uses the shutdown scripts provided with the kit
- Customized : a customized script or command lines is/are used
- Not found: the script has not been created.
- Protected against Out Of Memory Killer (OOM Killer)
- Pre-start script if defined (the 3 first lines are displayed)
- Guest OS response (optional, see Service management - Create/Edit guest stop script / Optional guest display status script)
- If the virtual machine is running and is using Charon-AXP or Charon-VAX version 4.9 minimum, the license status is displayed (license found, communication lost/restored, connection lost/application will stop, license expiration information)
- Network Interfaces settings with some checks performed. A NIC displayed followed by a number between parenthesis means an issue has been discovered: (1)=NIC does not exist, (2)=NIC is not managed by ncu, (3)=NIC is already used, (4)=NIC has an IP address.
.
- Auto-restart settings (feature managed by
...