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.8 server with Charon-AXP V4.11 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:

Example2 - Guest stop with stop script defined

Context: Red Hat Enterprise Linux 7.8 server with Charon-AXP V4.11 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.x server, systemd allows us to check the status of the service (menu option 4)
• Option 4 of the menu can help seeing the result of the shutdown commands
• Option 4 can also be used to edit the .service file to allow you to specify the service description, the auto-restart settings, etc... For more, see "# man systemd.service"

 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".