...
The Disk and Tape directories will be used to store emulated logical devices, for example, disk containers.
Please note: each
- Each instance of Charon-PAR must be started in a separate directory because certain files (SSTORAGE.DAT, NVOLATILE.DAT, UA_SSTORAGE.DAT, and console.dat) will always be created in the current working directory of the emulator instance. Starting multiple emulator instances in the same directory will lead to errors due to file locking problems.
- It is not recommended to place emulator storage devices (in particular vdisks) on NFS as this will have a significant impact on performance. However, if any of the storage (e.g., ISO files or vdisks) is on an NFS share, NFS locking must be enabled and all intermediate firewalls between client and server must allow the port used by the lockd and statd. Failure to do so will cause the emulator to hang at startup.
| Div | ||
|---|---|---|
| ||
Ethernet Interface Preparation
...
With respect to the supported Charon-PAR emulated Ethernet configurations (RAW or TAP), please bear in mind the following when deploying Charon in a cloud environment:
- If dedicating a host NIC to the emulator, the emulated system and the guest system must use the same MAC address and IP address on the interface that were assigned to the interface by the cloud provider. On the Linux level, the IP address must be removed from the interface. A dedicated NIC can be a RAW or MACVTAP configuration (MACVTAP support was added in Charon-PAR 3.0.9). For cloud settings, MACVTAP is recommended. Please refer to Ethernet Configuration Notes for more information.
- If using a TAP interface, the bridge must be an internal bridge (not connected to the cloud LAN via a host NIC). The bridge must use a private address range different from the cloud LAN. The emulator can then communicate with the outside world via NAT, or with other other private networks via a routing configuration.
...