Versions Compared

Old Version 60

changes.mady.by.user W.Erber

Saved on

compared with

New Version Current

changes.mady.by.user W.Erber

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add MACVTAP information

Anchor
TOC
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

The Charon-PAR/PA3 functionality of Charon-PAR emulates historic PA-RISC systems for MPE/iX. This section shows a sample installation of an MPE/iX guest system

Emulator Licensing Considerations

...

Excerpt
nameLicSectionPointer

The emulator needs a valid license to run. The license can be a Sentinel HASP license or a Virtual Environment (VE) license. Please refer to Initial Emulator License Configuration for the basic license configuration steps of both options. The license(s) to be used are defined in the configuration file. If running in a cloud environment, a VE license is strongly recommended (supported from Charon-PAR version 3.0.6).

Downloading and Unpacking the Provided MPE/IX Disk Container

...


StepDescription (configuration file settings are examples!)
1Create a copy of the configuration file template.

Example: 

# cd /data/Stromasys/host1/

# cp  /opt/charon/cfg/pa3.cfg host1.cfg

2Open the configuration file in a text editor.

# vi host1.cfg

or

# gedit host1.cfg

3Configure the system model.model "A400-100-110"
Configured model must be covered by your license.
4Configure the RAM for the emulated system.memory 2G
5Configure LDEV 1 (preconfigured system disk).

Change definition of DKA0 to:

DKA0.image="/data/Stromasys/host1/Data/Disk/ldev1.dsk"

6Configure a tape devices.

Change definition of MKAx to:

MKA600.image="/data/Stromasys/host1/Data/Tape/ldev7.img"

MKA500.image="/data/Stromasys/host1/Data/Tape/ldev8.img"

7Configure a network card based on a physical host NIC. This NIC is dedicated to the guest operating system and cannot be used for network communication by the host system. To share an interface, a virtual bridge would have to be used (see Ethernet configuration sections in this document).

In the configuration file template, comment out the dummy interface and the tap interface configuration. Then uncomment the interface configuration of the physical interface example. Change the definition of EWA0 to the interface that is assigned to the emulated system (example: eth1) and disable the offload parameters for the interface:

EWA0.mapping_mode="RAW"

EWA0.iface="eth1"

EWA0.initialize_command="ethtool -K $IFACE rx off ; ethtool -K $IFACE tx off ; ethtool -K $IFACE sg off ; ethtool -K $IFACE gso off ; ethtool -K $IFACE gro off ; ethtool -K $IFACE txvlan off ; ethtool -K $IFACE rxvlan off"

Depending on the capabilities of the Ethernet device, not all offload parameters maybe be available. This will create a warning message. The variable IFACE is set by the system before executing the initialize command.

For cloud environments, please note:

  • The MAC address on an interface must be the same as the one configured by the cloud provider on the dedicated interface. This should be the case by default for Charon-PAR. The IP address used by the guest OS must be the one configured by the cloud provider.
  • Virtual bridge configurations that are linked to a host NIC are not possible in cloud environments. Only "internal virtual bridge" configurations are possible. Such bridges can be used for host-guest communication. External communication for the guest can be achieved either by NAT or by routing configurations (depending on requirements and cloud-specific restrictions). A less complex, TAP based solution is to use a MACVTAP interface (using MAC and IP address assigned by the cloud provider).
8Save the configuration file.

...