Product Documentation and Knowledge Base - HomeDocumentation


Charon-VAXCharon-AXPCharon-PDPCharon-SSPCharon-PAR
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Description

This option will allow you to edit the configuration file(s).

Notes:

  • (warning) Changes will be applied on emulator restart
  • (tick) Some checks will be performed on network interface upon exit:
    • If virtual disk files (.vdisk) are used then their existence will be checked.
    • If the log file defined is a folder, an error message is displayed (currently not supported)
      (warning) If you change the log file name, you must remove the previous log monitoring service associated with this log file and recreate the service. See Manage monitored guests logs
    • If the network interface does not exist, an error message is displayed
    • If the network interface has an assigned IP address, an error message is displayed
    • If the network interface is not managed by 'ncu', an error message will be displayed
    • If the network interface is used in another configuration file, an error message will be displayed
  • (lightbulb) All offload parameters will be switched off automatically at guest start.
  • (warning) Rotating log files are supported only with CHARON-AXP and CHARON-VAX V4.7 minimum and Linux Toolkit 42 minimum

Example

We will add several issues in the "pluto" virtual machine configuration file:

  • the log file will be changed from a rotating log file set to "/charon/logs" to another one which is a folder or a file that does not exist: "/charon/logsINEX"
  • the network interface "ensINEX" will be added whereas this interface does not exist,
  • a virtual disk that does not exist will be added

 

When the editor will be closed, in our case 'vim', some checks will be performed:

 

When no issue is found, the following output is displayed:

  • No labels