Versions Compared

Old Version 68

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: Fix broken link

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

...

Table of Contents
excludeContents
stylesquare

Please note: All Linux and HP-UX sample commands in this section are performed as the root user (prompt = #). This may not be necessary for all commands in all environments depending on the local permission settings. The commands can be executed on the Charon host graphical console or via a non-graphical login (e.g., SSH). However, for accessing the running emulator, the use of PuTTY is strongly recommended because it works best with the emulator environment.

The Charon-PAR/PA9-64 functionality of Charon-PAR emulates historic 64-bit PA-RISC hardware. This section shows a sample installation of a 64-bit guest system.

Emulator Licensing Considerations

Insert excerpt
Charon-PAR/PA3 Guest - Basic Configuration and Installation
Charon-PAR/PA3 Guest - Basic Configuration and Installation
nameLicSectionPointer
nopaneltrue

HP-UX ISO Installation Medium 

...


StepCommand
1Change to the directory where you store your virtual disks.# cd /data/Stromasys/host1/Data/Disk/
2Unpack an ISO file contained in a compressed tar archive into this directory (example only: the actual command will vary depending on the location and archive format of your ISO file).# tar -xzf /path-to-file/HPUX_11v1_Sept2005_FOE.tgz

...

The configuration file template must be adapted to the customer environment and the required guest system characteristics. This section describes the minimum number of changes required to configure a Charon-PAR/PA9-64 emulator instance. Please refer to Configuration File Reference for a detailed description of the configuration file options.

...



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

Example: 

# cd /data/Stromasys/host1/

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

2Open the configuration file in a text editor.

# vi host1.cfg

or

# gedit host1.cfg

3Configure the system model.model "rp2400-1-650"
Configured model must be covered by your license.
4Configure the RAM for the emulated system.memory 2G
5Configure the serial console for telnet via PuTTY.

Use the method 2 section in the configuration file and make sure the definition of the serial.uart0.device is:

serial.uart0.device.command="putty -load PAR-Telnet-VT100"

6Configure disk 1 (system disk).

Change definition of DKA0 to:

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

7Add a definition for  disk 2 (ISO file) or (if it already exists) modify the definition to point to your ISO file.

load DKA100

DKA100.image="/data/Stromasys/host1/Data/Disk/HP-UX_11v1_Sept2005_FOE.iso"

8Configure a tape devices.

Change definition of MKAx to:

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

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

9

Configure 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 off-load 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).
10Save the configuration file.


Starting the Emulated System and Installing the Guest System

This section shows how to start the emulator and install a HP-UX system.

Please note:

  • The examples in this section assume that a graphical interface is used, on which a PuTTY session can be run.
  • Should this not be possible, you can access the console of the emulated system by using, for example, a telnet client and pointing it to the TCP port on the Charon host defined for the serial console port in the configuration file. The default port is 30000. Sample command to connect to an emulator on the local system:

           $ telnet localhost 30000.

In this case, do not start the PuTTY program automatically from the emulator configuration.

Starting the Emulator

To start the emulated Charon-PAR/PA9-64 system, perform the following steps:

...

For more information about the Charon-PAR console, please refer to Charon-PAR Console. For more information about the Charon-PAR command-line options, please refer to Charon-PAR Command-Line Options.


Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc