Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Table of Contents

Description

Manual start and stop of managed guests.

Examples


Example1 - Guest stop with no stop script defined

Context: Red Hat Enterprise Linux 7.5 server with Charon-AXP V4.9 installed, as4100/pluto guest running


Due to the absence of stop script, the service receives a SIGKILL signal and then, once stopped, is considered as failed:


<Go to top>

Example2 - Guest stop with stop script defined

Context: Red Hat Enterprise Linux 7.5 server with Charon-AXP V4.9 installed, as4100/pluto guest running Tru64 and booted. Stop script created and customized, using the "ssh" method (see "VM management - Create/Edit guest stop script") with example provided in the kit.

We can see below the guest has been properly stopped and is now in INACTIVE / REQUESTED state:

Note:

  • As we are running Red Hat Enterprise Linux 7.5 server, systemd allows us to check the status of the service.
  • Use option 4 of the menu can help seeing the result of the shutdown commands
  • Editing the .service file allows you to specify the service description, the auto-restart settings, etc... For more, see "# man systemd.service"

(info) With Linux systems not using systemd (Red Hat Enterprise Linux 6.x), we would have to look into a log file defined in the stop script / output redirection. For more information, see "VM management - Create/Edit guest stop script".

<Go to top>

  • No labels


© Stromasys, 1999-2024  - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.