Limitations and restrictions for IBM i client partitions on systems managed by the Integrated Virtualization Manager

With the Integrated Virtualization Manager (IVM) version 1.5 and later, you can install IBM® i in a client partition. IBM i client partitions have unique system, storage, networking, and operating system requirements and considerations.

The following limitations and restrictions apply to IBM i client logical partitions of the Virtual I/O Server that are running on systems that are managed by the IVM. IBM i client logical partitions that run on HMC managed systems have fewer limitations and restrictions. For details, see Limitations and restrictions for IBM i client logical partitions.

General notes

Physical tape is not available for IBM i client logical partitions, which impacts how you can back up IBM i and perform mainstore dumps.
IBM i client logical partitions do not own any physical I/O resources. All I/O resources on the IBM i client logical partition are virtual Ethernet and virtual storage (disk and optical).
The IBM i client logical partition has no view of the physical hardware. This affects how certain commands can operate, the amount of data returned by existing CL commands, APIs, and MI instructions, and how you can perform some IBM i operations, such as servicing the logical partition.

Hardware and software prerequisites

The managed system must be one of the following servers:
- Any POWER6™ processor-based server
- BladeCenter® JS12 Express™ Express
- BladeCenter JS22 Express Express
Note: For a complete overview and instructions for running IBM i on a blade server, see the IBM i on POWER™ Blade Read-me First.
The IVM must be at version 1.5 or later.
IBM i must be at 6.1 or later.

I/O, storage, and networking limitations

You cannot assign any physical I/O resources to IBM i client partitions, including the following:
- Host Ethernet Adapter
- Host Connect Adapter
- Virtual OptiConnect
- High-Speed link (HSL) OptiConnect
Instead, the Integrated Virtualization Manager (IVM) management partition manages the physical I/O resources and provides virtual I/O resources to the client partitions.
Virtual SCSI is the storage protocol available to IBM i client partitions.
Virtual disk and virtual optical are the storage devices available to IBM i client partitions. The virtual optical devices can map to physical DVD drives or to files.
The IBM i client partition can have up to 32 virtual SCSI devices under a single virtual adapter. It can have up to 16 disk units (logical volumes, physical volumes, or files) and up to 16 optical units.
The maximum virtual disk size is 2 TB. If you are limited to 1 adapter and you have a storage requirement of 32 TB, for example, you might need to make your virtual disks the maximum size of 2 TB. However, in general, consider spreading the storage over multiple virtual disks with smaller capacities. This can help improve concurrency.
Mirroring is the redundancy option for IBM i client partitions. However, you can use mutipathing and RAID for Virtual I/O Server redundancy.
The communications protocol available to IBM i client partitions is virtual Ethernet.

Technologies that are not supported on IBM i client partitions

High availability using switched disk
Virtual OptiConnect
Cryptographic coprocessors
IBM Facsimile for IBM i licensed program
You can use the IBM Universal Manageability Enablement for IBM i licensed program on IBM i client partitions, with limitations. For details, see Common Information Model.

Differences in IBM i operations

Because the Integrated Virtualization Manager (IVM) management partition manages the physical hardware instead of IBM i, some APIs, machine instructions, and CL, dedicated service tools (DST), and system service tools (SST) commands are not available to IBM i client partitions. Also, the Disk Management graphical user interface enforces some restrictions.
If you plan to configure Electronic Customer Support (ECS) or Electronic Service Agent™ (ESA), you must use a virtual Ethernet connection, such as Hypertext Transfer Protocol (HTTP). You cannot use a modem or dial-up connection.
If you plan to use Operations Console to manage IBM i, consider the following:
- You must configure a local console on a network (LAN). You cannot configure a local console directly attached to the server (with or without remote access allowed), and you cannot configure a remote console through dial-up support.
- You must configure virtual Ethernet bridging on the Integrated Virtualization Manager.
You can perform mainstore dumps in one of the following ways:
1. You can write the data to storage, copy it to virtual tape that is backed by files from the integrated file system, and then send it to IBM service and support using FTP.
2. You can write the data to virtual file-backed optical, transfer the data to physical tape, and then send the physical tape to IBM service and support.
IBM i client partitions use only virtual I/O resources, and do not have a physical tape drive available for backing up and restoring IBM i. You can back up IBM i in one of the following ways:
1. You can write the data to virtual tape that is backed by files from the integrated file system, and then send it to another system using FTP.
2. You can write the data to a file-backed virtual optical device in the management partition, and then save the data to physical tape using the backup command. For more information about the backup command, see Virtual I/O Server and Integrated Virtualization Manager commands. Note that backing up IBM i to optical devices (including file-backed optical devices) is usually slower than backing up IBM i to physical tape.
Because the installation media for IBM i is greater than 2 GB you must use the command line to upload the IBM i installation media to the management partition as follows:
1. Open a virtual terminal session to the Virtual I/O Server command-line interface. For instructions, see Connecting to the Virtual I/O Server command-line interface.
2. Run the following command:
```
mkvopt -name MediaName -file FileName -ro
```
  Where:
  - MediaName is the name of the media that you plan to upload to the management partition. For example, v5r5m0drv250.002
  - FileName is the name of the file that you plan to upload to the management partition. For example, v5r5m0-drv250.002.iso
3. Confirm that the media was uploaded successfully by clicking the Optical / Tape tab in the View/Modify Virtual Storage window to view the media.