...
Context: Red Hat Enterprise Linux 7.3 server with CHARON-AXP V4.8 installed, as4100/pluto guest running
| Div | ||
|---|---|---|
| ||
Due to the absence of stop script, the service receives a SIGKILL signal and then, once stopped, is considered as failed:
| Div | ||
|---|---|---|
| ||
...
Context: Red Hat Enterprise Linux 7.3 server with CHARON-AXP V4.8 installed, as4100/pluto guest stopped/failed (see above)
| Div | ||
|---|---|---|
| ||
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
...
Context: Red Hat Enterprise Linux 7.3 server with CHARON-AXP V4.8 installed, as4100/pluto guest running Tru64 and booted. Stop script created and customized, using the "rsh" 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:
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 rsh utility has been used, did initiate a shutdown that was successfull. As the shutdown does not power off the virtual machine, when the Tru64 system does not respond to ping, the service is stopped.
...