...

• Charon-PAR/PA3: a minimum of 10GB
• Charon-PAR/PA9-64: a minimum of 16GB
• Charon-PAR/PA9-32: 1-2GB for HP-UX 9.0.7 and 10.20, a minimum of 10GB for HP-UX 11.00.

The numbers above are just basic guidelines for the minimum operating system installation. The space actually required depends on the individual configuration of the system to be migrated.

...

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.

Ethernet Interface Preparation

...

Even though it is not mandatory, it is good practice to exclude the Ethernet interfaces that will be used by the guest system running on Charon-PAR from being managed by the NetworkManager. . This can be done for physical NICs dedicated to the guest operating system, or for virtual bridge and TAP configurations (that allow the host and the guest to share a physical interface).

In a network environment controlled by the NetworkManager, the NetworkManager—if configured accordingly—will create and manage the interface configuration files. This may create conflicts with the requirements of the Charon-PAR guest system. If this is the case, a manual configuration should be considered.

There are several options to prevent such problems:

...

Example of a minimal ifcfg-<interface> file in /etc/sysconfig/network-scripts/:

NM_CONTROLLED=no
DEVICE=eth0
HWADDR=00:11:22:33:44:55
BOOTPROTO=none
ONBOOT=yes

Example of a minimal bridge configuration via ifcfg-<interface> files in /etc/sysconfig/network-scripts/:

DEVICE=br_enp0s8
NAME=br_enp0s8
TYPE=Bridge
ONBOOT=yes
DEFROUTE=yes
STP=no
BOOTPROTO=none
IPADDR=10.0.0.1
NETMASK=255.255.255.0
GATEWAY=10.0.0.10
NM_CONTROLLED=no

DEVICE=enp0s8
NAME=enp0s8
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=no
BRIDGE=br_enp0s8

DEVICE=tap0_enp0s8
NAME=tap0_enp0s8
BRIDGE=br_enp0s8
TYPE=Tap
ONBOOT=yes
NM_CONTROLLED=no

Please refer to your host system’s man-pages for additional information about the NetworkManager.

...

The following image shows a sample configuration that disables the IPv4 configuration for an interface that is to be dedicated to the emulator using the GNOME network settings (.

Image Added

Also, make sure to include the option to make the interface Make available to other users) in the Details tab:

Image RemovedImage Added

You can use the following command to disable IPv6 for an interface (enp0s8 in the example):

...

To make this setting permanent, add it to /etc/sysctl.conf.

...