...
| Table of Contents | ||
|---|---|---|
|
Description
This option allows you to Manual start and stop of managed guests.
Examples
Example1 - Guest stop with no stop script defined
Context: Red Hat Enterprise Linux 7.1 server with CHARON-AXP V4.7 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:
| Div | ||
|---|---|---|
| ||
|
Example2 - Guest start
Context: Red Hat Enterprise Linux 7.1 server with CHARON-AXP V4.7 installed, as4100/pluto guest stopped/failed (see above)
...
...
The error message above (black/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
...
Example3 - Guest stop with stop script defined
Context: Red Hat Enterprise Linux 7.1 server with CHARON-AXP V4.7 installed, as4100/pluto guest running (not booted). Stop script created and customized based on the example provided with , using the "expect" utility (see "Service 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.1 server, systemd allows us to check the status of the service.
Use option 5 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)
...