Adding disk space to the Charon-HPA emulated HP3000 or HP9000 system is a process consisting of several steps:

• Build disk container files in the Linux host file system.
• Link these disk container files with the corresponding HP3000 or HP9000 paths in the Charon configuration file.
• Enable the disk for use by the guest operating system.
• For HP3000:
  • Define virtual disk devices using SYSGEN on the virtual HP3000.
  • Create the virtual volume using VOLUTIL on the virtual HP3000.

There is no direct correspondence between the number of virtual disks that are added to the emulated system and the number of Linux disks on which they reside. The storage on the host system just must provide enough capacity to store the disk containers used as virtual disks by the emulated system.

The sections below describe the process in more detail.

Creating Disk Container Files

The disk container files are created using the dd command. This command takes an input file name, an output file name, a block size, and a count as parameters. When instructed to read from /dev/zero , the command creates the output file and fills it with (block-size * count) zero bytes. Each file may be built as large as needed.

 The maximum disk size supported by MPE/iX is 512GB. The maximum size for HP-UX is 2TB.

Use the following steps to create a new disk container file:

Adding a Virtual Disk to the Configuration File

The new virtual disk must be added to the configuration file of the Charon-HPA instance. This requires two commands:

The device name DKXnnn encodes the device type and the device path of the emulated SCSI device presented to the guest operating system:

A disk device name has the following components:

• Value DK at the beginning of the device name: specifies that device type is disk.
• X: value consists of an uppercase letter encoding the device path. Please refer to Emulated Model Hardware Configuration Details and the relevant configuration file templates for system specific device path information.
  Example (rp4000):
  A = device path 0/0/1/0
  B = device path 0/0/1/1
  C = device path 0/0/2/0
  D = device path 0/0/2/1
• nnn: value encodes the SCSI device connected to the SCSI controller.
  Formula: (SCSI target ID*100)+LUN

Start Using the Disk in the Guest OS

Before the disk can be used by guest operating system applications, there are some required steps that need to be performed on the guest OS. The following examples are only used for illustrative purposes. They are intended to provide a general impression of the necessary actions.

Enable a Disk for Use by HP-UX

After booting the emulated system with the new disk added to the configuration file, check if HP-UX did recognize it:

HP-UX Device Nodes

During HP-UX boot-up, /sbin/insf is executed to create the character and block device special /dev files that allow communication with the disk. HP-UX uses the following device file naming system. For each disk device, the following special files are created:

• Block device file:
  /dev/dsk/c<number of card>t<SCSI target ID>d<device-LUN>
• Character device file:
  /dev/rdsk/c<number of card>t<SCSI target ID>d<device-LUN>

Where card is the (SCSI) controller number, target is the SCSI ID number, and device is the logical unit number, or LUN. The LUN is 0 for the majority of devices. An example for a disk at controller 0, target 2, LUN 0, is /dev/dsk/c0t2d0.

A disk is usually divided into file systems, areas that can hold files, or raw data areas such as swap. File systems are created in disk partitions or logical volumes. To view the size of the drive to be configured use the command, diskinfo.

Example:

Creating and Mounting a Filesystem on the new Disk

On HP-UX you can use a disk standalone or as part of a volume group (LVM). You can create a traditional HFS filesysstem on a disk, or you can create a JFS filesystem. JFS is HP's version of the Veritas journaling filesystem . The following example, which shows how to create a filesystem and mount the disk, will use HFS on a standalone disk:

 Please refer to your system's documentation and the man-pages for detailed information about the above commands.

Enable a Disk for Use by MPE/iX

After booting the emulated system with the new disk added to the configuration file, it needs to be enabled for use by the operating system as described below.

Adding the Device via Sysgen

After booting the virtual HP3000, add the device using SYSGEN; specify ID=ST19171N and the path that you specified in the configuration file load command in the previous step. For example:

PATH=0/0/1/0.1.0 for LDEV 2 (specified by "load DKA100" in hp3k.cfg )
PATH=0/0/1/0.2.0 for LDEV 3 (specified by "load DKA200" in hp3k.cfg ), etc.

This example shows one way to add LDEV 2:

When using the SYSGEN adev command, depending on the path chosen and your current configuration, you may first need to create parent controller entries using the SYSGEN apath command. Each disk device is created beneath PCI_DEVICE , A5150A , and PSEUDO path entries as shown in the following example:

You do not need to indicate to SYSGEN how large a disk is. Use the ST19171N device ID whatever size your disk image is; MPE will automatically detect (and use) the size of the physical disk image file.

Creating an MPE Volume

The final stage involves creating the MPE volume (and, if needed, volume set) and initializing the disk. When assigning new volume names, using one of these conventions is recommended:

• Name each volume, starting with the master, as MEMBERx , where ' x ' starts at ' 1 ' for the master volume and is incremented for each additional volume in the set.
• Name each volume MEMBERxxx , where ' xxx ' is the LDev number of the disk

The command :VOLUTIL should be used to create and initialize new volumes, and also (if needed) new volume sets, as shown in the following example. You will need to be logged in as MANAGER.SYS .

The following example shows how to add a new LDev 2 named MEMBER2 to the System Volume Set:

The following example shows how to create a new volume set with LDev 2 as the master:

To display the status of the volumes, use the dstat command as shown below: