Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Using the selected editor, here 'vim' with syntax highlighting, the configuration file can be customized:

Status
colourRed
titleTO DO
 screenshot to update with new syntax/OPA0

Div
classpagebreak


Notes on the above example:

...

Enter 'q' twice to reach the "Service management" menu:

Status
colourRed
titleTO DO
screenshot to update with new guests view

We can see below the service is active, meaning the emulator is running ((warning) this does not mean "booted") and will be automatically started at Linux server boot ("B" column on the right side)

The "Stop script" column shows the script has not been initialized meaning the guest will receive a SIGKILL signal upon stop request. This will be explained further (see Service management - Create/Edit guest stop script)

Status
colourRed
titleTO DO
screenshot to update with new guests view

Div
classpagebreak


Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

...

We are now going to remove (1 & 2) the as4100/pluto guest, currently in active state:

Status
colourRed
titleTO DO
screenshot to update withnew guests view

Div
classpagebreak


No stop script has been defined so this guest will be stopped (see below) without proper shutdown (emulator process will receive a SIGKILL). The service status will then be considered as failed (last line in the screenshot below) and deleted:

...

Example: Red Hat Enterprise Linux 7.4 server with CHARON-AXP V4.9 installed, virtual machine as4100/pluto installed

Status
colourRed
titleTO DO
screenshot to update withnew guests view

We are now going to prevent from the as4100/pluto guest to be started automatically (1). Once completed enter 'n' to return to the previous menu (2):

Status
colourRed
titleTO DO
screenshot to update withnew guests view

Edit guests lists (for stop order)

...