Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: CPU column definition updated

...

  • The first part of the menu displays server information like server boot time, current time (at display), number of CPUs and Memory Free / Total.
  • The second part displays the list of emulated machines (guests) managed. Column details:

    ColumnDescription
    Emulator/Config FileEmulator used with its configuration file name (shortened)
    CPU

    Displays the number of CPUs

    :
  • for VAX: always 1 (except for VAX66x0)
  • for AXP: based on configuration files

    by looking into configuration file settings (set n_of_cpus ...)

    . If the information is not found,

    first then using default value for the selected hardware. If no information is available, "-" is displayed instead.

    (warning) 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 HW limitations, CHARON licenses and also licenses on the virtual machine side

    MemDisplays the amount of memory defined for the guest
    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 stop perform a clean shutdown of the guest. Can be:

    • To customize: the script exists and a case has been added for the specified configuration file. It must however be customized with your commands to perform a clean shutdown of the guest (OpenVMS or Tru64 virtual machine). (info) For more information, see Service management - Create/Edit guest stop script
    • Case not set : the script exists but does not relate to the specified configuration file. This mean it has either been created manually or initialized automatically by the menu and you added a new guest.
    • Not found: the script has not been created. (warning) In this case, a service stop request will induce a kill of the emulator process
    BDisplays the Boot no server startup value, yes or no.

    .

  • The third part displays the available options that are detailed below.

...