...
Example: Red Hat Enterprise Linux 7.8 9 server with Charon-AXP V4.11 installed
...
Once the clone is completed, we can leave the clone utility (1 & 2 below) then use (3) the newly created file:
Select the startup type (4) and customize (45) the newly created this file:
If you don't edit the file now, you won't be prompted to start the guest (virtual machine).
...
We can now start the guest. If the preferences have been set to have a continuous view of the log file, the log will be displayed:
...
...
The An error message above (white/redwith id 00000352 (unable to read container file) 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
...
| Include Page | ||||
|---|---|---|---|---|
|
Remove guest
| Status | ||||
|---|---|---|---|---|
|
...
Before removing a guest, please ensure it has been properly stopped (a check will automatically be performed before removal). The way the guest is stopped depends on the "Stop script" existence and settings (see Service management - Create/Edit guest stop script)
...
Example: Red Hat Enterprise Linux 7.5 9 server with Charon-AXP V4.9 11 installed, virtual machine as4100/pluto installed
...
Use this option if you want (default) or do not want a guest to be started at Linux server boot
By default newly added guests are started automatically at Linux server boot ( this Startup type set to Automatic does not mean "booted"the legacy OS will be booted. The legacy OS boot on start needs to be defined at SRM prompt (>>>)
Example: Red Hat Enterprise Linux 7.5 9 server with Charon-AXP V4.9 11 installed, virtual machine as4100/pluto installed
We are now going to prevent from allow the as4100/pluto guest to be started automatically (1). Once completed enter 'n' to return to the previous menu (2):
Edit guests lists (for stop order)
Use this option to change the order of managed guests using the text editor of your choice
Use with caution, do not add nor delete lines (or at your own risk)
This option is not active for Linux systems using systemd (Red Hat Enterprise Linux 7 and Fedora).
For Linux systems using systemd (Red Hat Enterprise Linux 7 and Fedora), the services description files will have to be modified to add dependencies using Before= or After= for example if you want to define a start and stop order.
For more information, see manpages: # man systemd.unit
| Include Page | ||||
|---|---|---|---|---|
|