Hardware Family (Model) Configuration

To view the configured virtual machine hardware family, select Model in the Device column on the left. This displays the current value in the field Hardware Model (see figure above).

The hardware families currently supported by Charon-SSP/4M are:

Sun-4c and Sun-4m (an example would be the Sun SPARCstation 20)

The hardware family currently supported by Charon-SSP/4U(+) is:

Sun-4u (an example would be the Sun Enterprise 450)

The hardware family currently supported by Charon-SSP/4V(+) is:

Sun-4v (an example would be the SPARC T2)

Configurable options:

The Comments field allows you to add additional optional information about the virtual machine.
The option Start VM with system integrates the startup of the Charon-SSP instance in the host system startup. With this option enabled, the virtual machine starts automatically when the system boots. Optionally, a delay can be configured (for example to wait for a license to come online). Possible values for the delay parameter: 0 to 300 seconds.
Please note that the mechanism changed in version 4.0.x:
- In Charon-SSP 4.0.x, Charon-SSP no longer creates a start/stop script in /etc/init.d if this option is selected. Existing scripts are not deleted, but will no longer be activated. Instead, the Charon Agent is now responsible for starting emulator instances configured via the Charon Manager for starting with the host system boot. A problem exists in versions 4.0.x before version 4.0.4 that will cause the Agent to stop all active emulator instances that were started by the Charon Manager or configured via the Charon Manager for automatic startup at host system boot when the Agent itself is stopped. Please review the release notes for more details and the description of a workaround.
- Starting with version 4.0.4, the previous problem has been fixed. Also, as a new feature, a startup delay of up to 300 seconds can be configured to avoid timing problems that may, for example, cause the emulator to become active before the license is fully available (thus causing the startup to fail).

If a VM is started automatically with the host system startup and stopped with host system shutdown, it is the responsibility of the user to shut down the guest OS cleanly before host system shutdown. Failing to do so may cause data corruption in the guest system.

Unless otherwise mentioned, the terms Charon-SSP/4U and Charon-SSP/4V also include Charon-SSP/4U+ and Charon-SSP/4V+.