| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
Table of Contents
| Table of Contents | ||
|---|---|---|
|
...
Context: Red Hat Enterprise Linux 7.5 9 server with Charon-AXP V4.9 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:
| Tip |
|---|
The FAILED status is the result of the lack of stop script, as there's no way to know a clean shutdown of the legacy operating system was done. To solve this issue and have an INACTIVE state when a virtual machine is stopped, please define a stop script as explained below. |
| Div | ||
|---|---|---|
| ||
| Include Page | ||||
|---|---|---|---|---|
|
...
Context: Red Hat Enterprise Linux 7.5 9 server with Charon-AXP V4.9 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 and not in FAILED state:
Note:
...
Notes:
- Option 4 of the menu can help seeing the result of the shutdown commands
- Editing Option 4 can also be used to edit the .service file allows to allow you to specify the service description, the auto-restart settings, etc... For more, see "
# man systemd.service"
...
| Include Page | ||||
|---|---|---|---|---|
|