Page Comparison

...

Context: Red Hat Enterprise Linux 7.3 8 server with CHARONCharon-AXP V4.8 11 installed, as4100/pluto guest running

Image RemovedImage Added

Due to the absence of stop script, the service receives a SIGKILL signal and then, once stopped, is considered as failed:

Image RemovedImage Added

Image RemovedImage Added

Example2 - Guest

...

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

Image Removed

...

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

Image Removed

...

Image Removed

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.

...

...

stop with stop script defined

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

Image RemovedImage Added

Image RemovedImage Added

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

Image RemovedImage Added

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

...

Image Removed

Image Removed

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.

...

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

...