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.3 server with CHARON-AXP V4.8 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 start

Context: Red Hat Enterprise Linux 7.3 server with CHARON-AXP V4.8 installed, as4100/pluto guest stopped/failed (see above)

Depending on preferences that have been set, the log will be displayed:

...

The error message above (white/red) is expected the first time the virtual machine is started. It tells the .bin file does not exist as it is initialized when console parameters are set

Press CTRL-C at any time to leave the log file view.

Example3 - Guest stop with stop script defined

Context: Red Hat Enterprise Linux 7.3 server with CHARON-AXP V4.8 installed, as4100/pluto guest running (not booted). Stop script created and customized, using the "expect" utility (see "VM management - Create/Edit guest stop script") and the expect script example provided in the kit.

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

As we are running Red Hat Enterprise Linux 7.3 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:

We can see above, the expect utility has been used, did connect to the console, found the SRM prompt (the as4100 was not booted) and then issued a "power off" command.

This depends of what you decide to display in the guest stop script.

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