mkwpar Command

Automatically resolves conflicting static settings if required. Resolvable settings are base directory, host name, and network configuration.

Specifies that the workload partition must be started each time /etc/rc.wpars is run, which is added to the global /etc/inittab to run each time that the system starts. The default is not to start the workload partition automatically.

devname=device name

Specifies the device name to allocate to the workload partition. For pseudo and clone type devices, this command is the full path to the device (that is, /dev/pty10). For storage type devices, it is the logical device short name.

devid=device identifier

Specifies the unique device identifier of a disk type device to allocate to the workload partition. This attribute applies only to disk, cdrom, or tape type devices.

devtype=[clone | pseudo | disk | adapter | cdrom | tape]

Specifies the device type of the device to allocate to the workload partition.

rootvg= [yes | no]

Used to indicate whether the specified disk device is to be used as a rootvg workload partition device. If the rootvg attribute is not specified, the command takes the default of number.

The volume group for file systems that you specified in the image.data file, supersedes the volume group that is specified with the -g flag.

A default route is not created automatically. The -I flag is used to specify routes, including the default route.

• Traffic between addresses that are hosted on the same global system is sent through the loopback interface.
• Routing table entries that are configured in the global system, including the default route, are used to transmit workload partition traffic.

If you enable WPAR specific routing by specifying the -i flag, the workload partition creates and uses its own routing table for outgoing traffic.

Routing entries are created automatically for each of the network addresses of the workload partition to accommodate broadcast, loopback, and subnet routes. For more information about the network attributes, see the -N flag. You can create explicit additions to the routing table of the workload partition using the -I flag.

You can specify the following attributes with the -I flag:

image_data

Specifies the path to the image.data file to be used for logical volume and file system options. The format of the image.data file is described in Files Reference and the /usr/lpp/bosinst/image.template file. File system specifications in the image.data file supersede file system specifications in the Specifications File. The -c flag and -L image_data= flags are mutually exclusive.

shrink

Specifies that the LV_MIN_LPS attribute, rather than the LPs attribute, must be used to determine the number of logical partitions for the logical volume. The LV_MIN_LPS attribute is from the lv_data stanzas from the file that the image_data attribute specifies. This attribute can minimize the amount of disk space that is required for a workload partition file system. This attribute has no effect if the image_data attribute is not specified.

ignore_maps

Specifies that the MAPFILES attribute must not be used to provide a disk mapping for the logical volumes that are associated with a workload partition. The MAPFILES attribute is from the lv_data stanzas from the file that the image_data attribute specifies. This attribute has no effect if the image_data attribute is not specified.

ignore_lvs

Specifies that the information from the lv_data stanzas is not used when the image.data file is being processed. The logical volumes are created with the default characteristics when the file systems are created. This attribute has no effect if the image.dita attribute is not specified. If this attribute is specified, the ignore_maps attribute is ignored.

File system specifications in the -M flag supersede file system specifications in the image.data file.

There are 4 basic workload partition mount forms:

localfs

Disk-based file system (vfs=jfs or vfs=jfs2) to be created at the location that is specified by the value of the directory within the directory structure of the workload partition. If you specify a dev attribute, it denotes an existing logical volume in the global environment, which is to be used to host the file system. For localfs file systems, you must specify the size attribute. Other optional attributes, which are of the form attr=value, include those attributes in the following list:

logname

Specifies the log device to use for this file system. This attribute must be specified only if the default log device that the file system uses is insufficient.

• For vfs=jfs2, the default is to use an inline log.
• For vfs=jfs, the default is that the file system uses an existing log device if available. Otherwise, it creates one. When the logname attribute is being specified, make sure that the named log device exists.

mode

Specifies the octal permission mode to assign to the base directory of this file system. The default is 755.

size

Specifies the size of the file system that is created in a format acceptable to the crfs command.

vg

Specifies the volume group in which the file system (if no existing logical volume device is specified by using the dev attribute) is created. If you do not specify a value, the volume group that is specified in the -g flag is used. If you do not specify the -g flag, rootvg is assumed.

Specifies other options to pass to the crfs command when the file system is being created. Options are passed directly to the crfs command so the value must be in the form that is required by the crfs command.

mountopts

Specifies the mount options (corresponding to the "options" attribute in an /etc/filesystems stanza). If you do not specify a mount option, by default, no mount flags are used. Option values that you can specify correspond to the -o options of the mount command.

namefs

Specifies that the global directory that is specified by the dev attribute is mounted over the directory that is specified by the directory attribute in the file system structure of the workload partition. The only other attribute that is applicable to a namefs mount is mountopts. For the namefs type, you cannot map the /, /var, /opt, /usr, /tmp, or /proc file system of a workload partition with write privileges to a real /, /var, /opt, /usr, /tmp, or /proc file system.

The namefs mount can also be used with rootvg workload partitions. In this case, the content of the namefs mount is not saved by using the savewpar command.

nfs

Specifies that the directory that is specified by the dev attribute on the system that is exported by the host attribute is mounted over the workload partition directory. The only other attribute that is applicable to a nfs mount is mountopts.

Requirement: The global system and the workload partition must both have root permissions to the NFS device. You can give the global and the WPAR root permission to the NFS device, when you export the NFS mount, by specifying the root access for the host names of both the global system and the workload partition. When an NFS device is mounted, you cannot map the /, /var, /opt, or /usr file system of a workload partition with write privileges to a real /, /var, /opt, or /usr file system.

directory

Specifies that the directory that is specified by the directory attribute is added to the file system structure of the workload partition. No file system is created. Use this attribute to reduce the number of file systems to manage in a workload partition, such as by eliminating the separate file systems for /tmp and /var. Ensure that the size of the containing file system is adjusted accordingly.

Note: A directory mount cannot be used for /usr or /opt.

• interface= if or interface=namemappedif
• address=A.B.C.D
• netmask=A.B.C.D
• broadcast=A.B.C.D
• address6=S:T:U:V:W:X:Y:Z
• prefixlen=n

# The comments start with '#'
# Each line contains a pair of name-mapped interface 
# and real interface separated by tab or blank spaces.
foo en0
goo en1
soo en2

To define an IPv6 network configuration, specify the -N flag with the address6, prefixlen, and interface attributes. The address6 attribute is a 128-bit address. The address is represented by eight 16-bit integers that are separated by colons. Each integer is represented by 4 hex digits. Leading zeros can be skipped, and consecutive null 16-bit integers can be replaced by two colons (one time per address). The prefixlen attribute is the number of high-order bits that are used to mask the IPv6 address and to comprise the prefix. The value of the prefixlen attribute ranges from 0 through 128. Each -N flag can accept either IPv4 attributes, or IPv6 attributes, but not both.

• Use the name parameter to specify an existing mount group in /etc/filesystems. Such a mount group usually exists because a previous workload partition was removed by using rmwpar -p. If you specify the name parameter, it cannot match the name of an existing workload partition on the system. If you specify the -d flag, the mount points of the file systems are adjusted accordingly. If you do not specify the -d flag, the base directory of the workload partition is determined based on the mount points that are associated with the discovered file systems.
• If the file systems are not defined in /etc/filesystems, use the -p flag with the -M flag or mount stanzas in the specification file to define the attributes of the file systems.

If you specify the -p flag with the name parameter, and no workload partition name is provided by using other means (for example, the -n flag or general.name in the specification file), you can also use the name parameter as the workload partition name.

The -p flag can be used to re-create a versioned workload partition. The workload partition's file systems must be preserved. To re-create such a versioned workload partition, the -f infile flag is included to provide a specification file that is saved from the original workload partition. The specification file is required to preserve the ostype value of the workload partition.

• /etc/resolv.conf
• /etc/hosts
• /etc/netsvc.conf
• /etc/irs.conf
• /etc/networks

If the NSORDER environment variable is defined in the calling environment, it is added to the workload partition's /etc/environment file.

• Active=no means that the resource attributes are defined but the resource controls are not activated when the WPAR is started.
• Active=yes means that the resource control attributes are activated when the WPAR starts.

You can provide privileges in a specification file (see the -f flag), in a separate security attributes file through -S secfile=/path/to/secattrs, or on the command line by using the -S privs=list flag. If you do not provide security attributes through one of these mechanisms, the /etc/wpars/secattrs file is used by default. When you use a separate security attributes file (either the default file or the file that is supplied through -S secfile), this file is read once when the workload partition is created to determine the privileges that are associated with the workload partition. Subsequent changes to the file have no effect on existing workload partitions. The default security attributes file /etc/wpars/secattrs must not be modified directly as it might be overwritten in the future.

/path/to/userScript <action> <wparName>

The second argument is the name of the workload partition. The script can use the lswpar command to obtain any other necessary configuration data.

exportfile=/path/to/file

Specify a file containing valid extension stanzae that will be exported. An extension stanza should contain at least the kext attribute. The local and major attribute can also be specified in the stanza which are described below. The exportfile attribute is mutually exclusive with the kext attribute. It is also mutually exclusive with the local and major attribute because these can be specified for each extension stanza in the exportfile.

This is a file that can be created by a user to use with exportfile=/path/to/file for mkwpar and chwpar. It can contain multiple extension stanzas. The kext attribute is required for each extension stanza. The local and major are optional as they both have default value no. The exportfile will look similar to the following.

extension:

major = "yes"
local = "no"
kext = "/usr/lib/drivers/ldterm"

kext=/path/to/extension

Specify a kernel extension that will be exported. This is a kernel extension located in the global system's filesystem. The keyword ALL can also be specified. This will allow a workload partition to load any extension. When ALL is specified, the local and major attributes are restricted to local=yes and major=no. Additional -X flags can be specified to overide the restricted local and major values. The kext attribute is mutually exclusive with the -X exportfile attribute.

local=yes|no

Specifying local=yes will make an instance of the kernel extension accessible to only the workload partition that is loading it. Specifying local=no will share the instance of the kernel extension loaded in the global system. By default, local=no.

major=yes|no

This attribute should only be used for kernel extensions that have an associated device major. By default, major=no.