IBM
S/390 Virtual Image Facility for LINUX
Guide and Reference
Version 1 Release 1.0
Program Number 5739-A01
Document Date: February 9, 2001
Current copy of this document can be found at URL:
http://www.s390.ibm.com/linux/vif
GC24-5930-03
Note
Before using this information and the product it supports, be sure to read the general information under “Notices” on page 33.
| Fourth Edition (February 2001)
| This publication applies to S/390 Virtual Image Facility for LINUX Version 1 Release 1.0 (Virtual Image Facility), Program Number
| 5739-A01 and to all subsequent releases and modifications until otherwise indicated in new editions.
| This edition replaces GC24-5930-02. Changes or additions to the text and illustrations are indicated by a vertical line (|) to the left of
| the change.
 Copyright International Business Machines Corporation 2000, 2001. All rights reserved.
Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to
restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
| Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
| Who Should Read this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
| What You Should Know before Reading this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
| What This Book Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
| Where to Find More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
| How to Send Your Comments to IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
| Chapter 1. Introduction to the S/390 Virtual Image Facility for LINUX . . . . . . . . . . . . . . . . . 1
| Chapter 2. Installing VIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
| Overview of the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
| Planning for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
| Planning Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
| Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Sizing Guidelines for a VIF LPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Storage Sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Processor Sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
| Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
| Installation Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
| Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
| Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
| When You Are Done . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 3. Administering your VIF System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Entering VIF Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
| The Master Linux Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
| Console Access for Other Linux Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 4. Servicing VIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
| Chapter 5. VIF Support Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Problem Determination and Documentation Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Linux Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
VIF Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 6. VIF Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
| Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
HELP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
HYPERVISOR Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
 Copyright IBM Corp. 2000, 2001 iii
HYPERVISOR COLLECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
HYPERVISOR ECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
HYPERVISOR ERRORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
HYPERVISOR EXPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
HYPERVISOR IMPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
HYPERVISOR INSTALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
HYPERVISOR NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
HYPERVISOR RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
HYPERVISOR SERVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
HYPERVISOR SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
HYPERVISOR VERIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
HYPERVISOR VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
IMAGE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
IMAGE CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
IMAGE DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
IMAGE NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
IMAGE SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
IMAGE START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
IMAGE STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
IMAGE STOPALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
PARTITION Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
PARTITION COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
PARTITION CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
PARTITION DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
PARTITION INITIALIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
PARTITION SHARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
PARTITION SWAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
QUERY Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
QUERY ACTIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
QUERY ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
QUERY BOOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
QUERY CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
QUERY ERRORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
QUERY IMAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
QUERY LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
QUERY NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
QUERY PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
QUERY PARTITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
QUERY PERFORMANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
QUERY SHARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
QUERY VOLUMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
| Appendix A. Installation Prompts Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Programming Interface Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
iv Virtual Image Facility
Trademarks and Service Marks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Contents v
| Preface
| This book describes how to use S/390 Virtual Image Facility for LINUX (VIF).
| Who Should Read this Book
| This book is for anyone who wants to learn how to use VIF and has not used VIF before or has had some
| experience with VIF and wants to gain more knowledge.
| What You Should Know before Reading this Book
| Before using this book you should be familiar with S/390 hardware concepts. It would also be helpful if
| you were familiar with Linux and have some experience with Linux, VM and S/390 systems programming.
| What This Book Contains
| Following are some of the topics you can expect to learn about after reading this book:
|
Overview of VIF
|
Installing VIF
|
Administering VIF
|
Servicing VIF
|
Using VIF Support Procedures
|
Using VIF Commands
| Where to Find More Information
| For more information about VIF, refer to:
|
http://www.s390.ibm.com/linux/vif
vi  Copyright IBM Corp. 2000, 2001
| How to Send Your Comments to IBM
| Your feedback is important in helping to provide the most accurate, high-quality information. If you have
| any comments about this publication, you can send them using one of the following means:
|
E-mail to vifserv@vnet.ibm.com
|
Facsimile to telephone number (+1)607-752-1497
|
Postal mail to
| IBM Corporation
| c/o Virtual Image Facility Service - Dept C7NG
| 17 1 North Street
| Endicott, NY 1376
| USA
Preface vii
viii Virtual Image Facility
| Chapter 1. Introduction to the S/390 Virtual Image Facility for
| LINUX
| The S/390 Virtual Image Facility for LINUX (VIF) provides an environment that lets you create and
| manage multiple Linux images on a single S/390 or zSeries platform. If you are familiar with VM, then you
| already understand the underlying concepts of VIF. Much of the internal functions of VIF are the same as
| VM because they are built on the same code base, but VIF has been simplified to eliminate the need for
| in-depth VM skills. If your background is the Linux, Unix or Windows operating system, then VIF
| introduces you to a new level of flexibility and efficiency in managing large numbers of servers.
| Under Unix or Windows, a program can be multithreaded and allocate software resources (such as files)
| among the threads. In a similar way, VIF can allocate resources among multiple Linux servers running on
| one hardware box. The VIF hypervisor manages the assignment of portions of hardware to each
| individual Linux image. A simple Linux client program running on the master Linux image (Linux0) is used
| to send system management commands to the VIF hypervisor. These VIF commands create Linux
| images, assign disk partitions, query, start and stop Linux images, and provide other control functions.
| The VIF commands do not require previous system S/390 skills.
| Figure 1. Sample VIF Environment
 Copyright IBM Corp. 2000, 2001 1
2 Virtual Image Facility
| Chapter 2. Installing VIF
| Overview of the Installation
| Installation of VIF draws on many different skills. It is important to assemble a team of people with
| specific expertise, each ready to contribute in their area at the start of this project. In some projects, these
| jobs may be done by one or two people taking on different roles as required. However, if one of these
| areas is overlooked, it could lead to failure of the project. Good planning and securing necessary
| resources is vital.
| Close cooperation among personnel with the following expertise is crucial to designing and implementing a
| successful VIF installation:
| Personnel with S/390 System Programming Experience
| The S/390 programmer is needed to provide access to the Hardware Management Console
| (HMC), guidance on its use, and to define an LPAR (if VIF is to be run in an LPAR).
| DASD Personnel
| DASD personnel must be able to provide enough disk storage space for the initial install, with
| additional space as required for the proposed total number of Linux images.
| Networking Personnel
| Personnel with knowledge of networking are responsible for network connectivity.
| Linux System Administrator
| The Linux system administrator leads the install of the Linux code distribution, as well as
| manages the Linux servers that are created.
| The process begins with the product tape. Code on the tape is copied to disk and then loaded from the
| disk. This brings up a mini-kernel, which executes an install script. The script prompts you to answer
| basic configuration questions, saves the data, and then boots the first (master) Linux image, called Linux0.
| Once Linux0 is up and you can telnet into it, the installation of VIF is complete, but not all the work is
| done. At this point, you must install the Linux distribution you have chosen to work with.
| Planning for Installation
| Planning Your Network
| Installing the VIF environment also installs an initial Linux image (Linux0, or the master Linux image), so a
| minimum of two IP addresses are required. These IP addresses can be on either of the following:
|
A shared network connection
|
Two separate physical network connections
| The IP address assigned to the VIF hypervisor must be in a different subnet than the IP address assigned
| to Linux0.
Chapter 1. Introduction to the S/390 Virtual Image Facility for LINUX 3
| When choosing the configuration to use, keep these considerations in mind. VIF requires a LAN
| connection. This physical connection can be used to provide network access for Linux images you create,
| although each image still requires its own IP address. You can provide a Linux image with a direct LAN
| connection. An image that you expect to perform a lot of network communication may benefit from having
| its own physical connection. Linux images that communicate mostly with the other images under the
| control of the same VIF environment, that do not use the network extensively, may not require their own
| LAN connection.
| Hardware and Software Requirements
Before installation of VIF can begin, the following must be available for use:

A processor (G5 or later or Multiprise 3000) or a logical partition (LPAR) on such a processor

Access to the Hardware Management Console (HMC) for the processor
|
One entire volume of 3390 model 3 DASD (You will need all 3,339 cylinders of the volume.)

One 3480 or 3490 tape drive
|
One or two token ring or 10 Mb ethernet ports on an IBM Open System Adapter, IBM 3172s, or
| equivalent devices, connected to a Local-Area Network (LAN)

An IP address on the LAN and its associated network mask to be used by the VIF hypervisor

A second IP address in a different subnet to be used by the master Linux image (Linux0)

The IP address of a gateway on the LAN

S/390 Virtual Image Facility for LINUX installation tape

The IP address of an FTP server with access to the contents of a Linux distribution
|
The user name, password, account (if known), file path and file name needed to retrieve the Linux
| installation file and associated materials using this FTP server. The FTP server must support
| Unix-style (forward slash) path names.
| Note: These requirements are only for installing VIF. Linux hardware and software prerequisites should
| be fulfilled prior to installing VIF or Linux.
Sizing Guidelines for a VIF LPAR
Use the guidelines in this section to help determine the processor and storage requirements for your VIF
environment. These guidelines can be used as starting points, but actual requirements depend on the
particular Linux workloads and the level of responsiveness you want for your system. For a more detailed
analysis, contact your IBM representative or IBM Business Partner to engage the SIZE390 program of the
S/390 Performance team.
4 Virtual Image Facility
Storage Sizing: Use the following formula to determine the amount of real storage required for your
VIF system:
real storage =
(Linux_Images × 0.5) + Active_Images × (15MB + (Mean_File_Size × Active_Files))
Paging_Factor
Where:
Linux_Images is the number of Linux images.
Active_Images is the average number of Linux images that will be active at one time.
Mean_File_Size is the average size of file being accessed by a Linux image.
Active_Files is the average number of files being accessed by a Linux image.
Paging_Factor is a number between 1 and 5, which represents the level of paging activity you are willing
to accept. A low value selects low paging activity and produces better performance. A high
value allows more paging activity and gives lower performance.
For example, if 25 of 100 images are active, and each is using ten files that average 0.3 MB in size, then
the storage requirement would range from 104 MB to 519 MB, depending on the Paging_Factor selected.
Processor Sizing: VIF shares processors among Linux images. The number and speed of
processors you need is workload-specific. However, if you are going to have n Linux images always
active and ready to run, then a configuration with n processors allows them to run with minimal wait time
for processor resources.
| Installation Checklist
| Complete this checklist prior to loading the installation tape. Keep a copy of this checklist for your
| records. First, ensure you make note of the following:
| Installation Prompts: Below is a list of the VIF installation prompts you will use for configuring VIF.
| Use the copy of this checklist in Appendix A, “Installation Prompts Checklist” on page 31 to fill in the
| answers to these prompts:
| Real address of the 3480 or 3490 tape drive
| The tape drive that will be used to read the VIF product tape.
__________
| Real address of the 3390 Mod 3 DASD
| The dasd (disk) device where the code will be installed.
__________
| Installation Prompts
| 1. Your choice of sysres volid for VIF (1-6 characters)
| The label to be assigned to the 3390 volume where VIF will be installed.
Chapter 2. Installing VIF 5
| Installation Prompts
| 2. OSA device address for VIF hypervisor
| The even address of the network device pair that is assigned to the VIF hypervisor for network
| access.
| 3. And the OSA device port number
| The number of the port associated with the network device pair that is assigned to the VIF
| hypervisor.
| 4. VIF hypervisor network type (Ethernet, Token-Ring, 802.3, or FDD)
| The type of local-area network (LAN) to which the hypervisor is connected.
| 5. VIF hypervisor network MTU size (576, 1492, 1500, 2000, or 4096)
| The Maximum Transmission Unit (MTU) of the VIF hypervisor LAN.
| 6. VIF hypervisor IP address
| The IP address assigned to the hypervisor.
| 7. And the hypervisor subnet mask
| The IP mask associated with the hypervisor IP address.
| 8. IP address of gateway to be used by VIF
| The IP address of the default gateway on the VIF hypervisor LAN.
| 9A. Master Linux network type (Internal or External)
| The type of network connection to be used by the master Linux image. If a network device pair
| is available, specify "External"; otherwise, specify "Internal".
| 9B. Enter master Linux network device address:
| Note: If an External network connection is provided for the master Linux image, specify the
| even address of the network device pair.
| 10. IP address of the master Linux image
| The IP address assigned to the master Linux image.
| Note: This address must be in a subnet different than the subnet where the IP address is for
| the LAN gateway that you are using.
| 11. And the subnet mask for the master Linux image
| The IP mask associated with the master Linux image IP address.
| 12. The IP address of the FTP Server for the Linux distribution
| The IP address of the FTP server where the Linux distribution files are located.
| 13. The user name for the FTP server
| The user name to be used to connect to the FTP server where the Linux distribution files are
| located.
| 14. And the password for the FTP server
| The password to be used to connect to the FTP server.
| 15. The FTP account information, if needed
| The account number to be used to access the FTP server, or null if no account information is
| required.
| 16. The path and file name of the Linux installation file on the FTP server
| The path and file name on the FTP server of the Linux installation file.
6 Virtual Image Facility
| Before You Start
| The following steps must be completed before installation is attempted:
|
The IOCDS must be configured and must include the required devices listed above.
|
The OSA or other network device must be configured with the IP addresses listed above.
|
The TOD clock must be set.
|
The installation target DASD must be initialized.
|
The installation checklist must be completed.
| Installation Procedure
Install VIF as follows:
1. Mount the Installation tape on the tape drive.
2. Use the HMC to load from the tape drive with a load type of clear and the load parameter
| AUTOxxxx
Where xxxx is the address of the 3390 DASD on which VIF is to be installed.
3. Wait for the system to enter a disabled wait state. This will be signified by the flashing of the
| Hardware Messages function icon. In-house installations have ranged from 15 minutes to just under
| one hour.
4. When the disabled wait state occurs, display the PSW and ensure that it is 000A0000 00000000. To
check the PSW, double click on the flashing hardware messages icon. Then double click on the
| selected Disabled wait message and then check the PSW. If it is not as stated above, refer to
| “Troubleshooting” on page 16 for guidance.
5. Load from the VIF DASD volume.
6. Activate the Operating System Messages function on the S/390 Hardware Management Console. You
will not see any output for about two minutes.
| Note that the following message is a normal informational message:
| Error report may be produced using the HYPERVISOR ERROR command
| 7. Reply to the installation prompts with the appropriate parameters from your checklist. (Reply
RESTART to any prompt to restart the configuration process. Enter a null line to accept the default
value enclosed in angle brackets after a prompt.):
Enter system residence volume Label:
Enter Hypervisor network device address:
Enter Hypervisor network port number:
Enter Hypervisor network type (Ethernet, 802.3, TokenRing, FDDI):
Chapter 2. Installing VIF 7
Enter Hypervisor network MTU size (576, 1492, 1500, 2000, 4096):
Enter Hypervisor IP address:
Enter Hypervisor IP mask:
Enter Hypervisor gateway IP address:
Enter master Linux network type (External, Internal):
| Enter master Linux network device address:
| Note: This prompt appears only if you specified “External” for the previous prompt.
Enter master Linux IP address:
Enter master Linux IP mask:
Enter FTP server IP address:
Enter FTP server user name:
Enter FTP server password:
Enter FTP server account or null:
Enter installation file path and name:
The configuration information that you entered is redisplayed followed by a message asking if it is
correct or not. If you reply yes to say it is correct, then install continues with step 8 below. If you say
no, then the configuration prompts are redisplayed in order for you to change any value you previously
entered.
| If this installation step is interrupted, you will have to begin again from the point where you loaded VIF
| from DASD. (Step 5 on page 7.)
8. Wait for the master Linux image to boot. This may take up to two minutes to start producing output.
The following resources are provided to the master Linux image automatically:

One processor.

128 megabytes of storage.

A console (the system console device, accessible through the Operating System Messages task of
the S/390 Hardware Management Console).
|
An 840-megabyte unformatted read/write DASD partition at device number 201. Depending on
| the Linux distribution you are using, this partition may not be large enough for a full Linux
| installation. Linux0 only needs a “minimum” Linux install to function.

A 3.5-megabyte read-only DASD partition at device number 203 (refer to Chapter 6, “VIF
Command Reference” on page 19 for more information about the contents and use of this
partition).

A network connection, as selected during system configuration.
9. Complete the installation of the master Linux image by following the configuration procedures for the
distribution you used. This installs a permanent copy of Linux on your DASD volume.
8 Virtual Image Facility
| When You Are Done
| Once you have completed the installation, you should change the Linux system that will be booted by the
| master Linux image on your newly configured system. To boot from DASD, enter the vif command:
| IMAGE SET LINUX BOOT xxxx
| where xxxx is the device number of the DASD partition containing the Linux system you wish to boot. For
| example, if you install your Linux system on device 201, you would enter:
| IMAGE SET LINUX BOOT 2 1
| This will start Linux0 using your configured Linux system on device 201 instead of the ramdisk image.
| Refer to Chapter 6, “VIF Command Reference” on page 19 for information on using the vif commands.
| With VIF installed and Linux0 configured and saved to disk, you are now ready to define and configure
| images and save the image configuration. Refer to the Chapter 6, “VIF Command Reference” on
| page 19 for information about these functions. Also refer to the “How-to” section of the VIF web site at
| http://www.s390.ibm.com/linux/vif/procs.html for an overview of setting up new images under VIF.
| Note: Anytime you configure images, you should make a back-up copy of the resulting configuration.
| Refer to “HYPERVISOR EXPORT” on page 21.
| If you encounter problems during VIF installation or configuration, refer to Chapter 5, “VIF Support
| Procedures” on page 15 for guidance.
Chapter 2. Installing VIF 9
10 Virtual Image Facility
Chapter 3. Administering your VIF System
Using VIF involves employing its administrative interface.
Entering VIF Commands
After you have installed VIF, it initializes itself and installs the master Linux image, known as LINUX0, from
the FTP location you specified during the system configuration process. LINUX0 provides the
administration interface to the VIF environment in the form of the vif command. The general command
syntax is:
vif address command function [operands]
| Where:
| address is the IP address of the VIF hypervisor.
| command is the command to be executed.
| function is the function to be executed.
| operands are the parameters of the command.
For example, you can issue
vif 1.2.3.4 query level
(where 1.2.3.4 is the VIF system IP address) to determine the current level of VIF. Or, you can define a
new Linux image named mailhost with the command
vif 1.2.3.4 image create mailhost
Issue
vif 1.2.3.4 help
to list the available commands, or
vif 1.2.3.4 help image
for a brief explanation of the syntax and purpose of the IMAGE command.
The vif command resides in a separate, read-only file system on LINUX0's device 203. It may be
convenient to create a mount point for it, for example,
mkdir /usr/local/vif39
and to update /etc/fstab to mount it automatically, rather than issuing the mount command
mount /dev/dasdb1 /usr/local/vif39 -r
manually.
Chapter 2. Installing VIF 11
Create a symbolic link to the vif command by issuing
ln -s /usr/local/vif39 /vif /usr/sbin/vif
To make using vif more convenient, a simple shell script might be helpful. For example,
#!/bin/bash
vif 1.2.3.4 $@
(with the appropriate IP address substituted for 1.2.3.4) could provide an interface that is easier to use.
| The commands used for administering VIF are described in Chapter 6, “VIF Command Reference” on
| page 19.
| The Master Linux Image
The master Linux image (Linux0) console is always on the hardware system console. It can be accessed
by using the HMC Operating System Messages task. Linux0 provides the interface to VIF administration
functions, so access to it should be limited and care should be taken to ensure that this image does not
become unusable. In general, it is advisable to limit your use of Linux0 to essential system management
functions and to create other images for other purposes.
| Console Access for Other Linux Images
| Once you have defined additional Linux images, you access the console of any started Linux image
| through VIF by connecting to the VIF hypervisor using telnet and entering the following command:
| LOGON image
| specifying the name of the image whose console you want to access.
12 Virtual Image Facility
Chapter 4. Servicing VIF
| Service for VIF is shipped as a full product replacement. It is always a good practice to make a backup
| copy of your configuration file before you start the service process. (Refer to steps 3 and 4 below.)
| However, applying service should not affect the configuration information that you provided during
| installation and information about the images you already have defined.
| Before applying service, please read the documentation that is shipped with your service tape. That
| document often contains important and special instructions concerning service.
After you receive your VIF service tape, do the following:
| 1. Access the master Linux image, known as LINUX0. (Refer to “The Master Linux Image” on page 12.)
2. Mount the S/390 Virtual Image Facility for LINUX Service tape on a tape drive accessible to the VIF
system. Make a note of the tape drive address.
3. Make sure that the file system where the vif command resides is mounted:
mount /dev/dasdb1 /usr/local/vif39 -r
4. Enter the following command to save the configuration in file /config.save.
vif address HYPERVISOR EXPORT
Where:
address is the VIF hypervisor IP address.
5. Enter the following command to service VIF:
vif address HYPERVISOR SERVICE device
Where:
address is the VIF hypervisor IP address.
device is the device address of the tape drive where the service tape is mounted.
| 6. If you receive the message:
At your convenience, use the RESTART function to restart the system
and bring the service online
then you may complete the service process, when it is convenient, by issuing the following command
from the master Linux image:
vif address HYPERVISOR RESTART
Where:
address is the VIF hypervisor IP address.
 Copyright IBM Corp. 2000, 2001 13
7. If the system was not restarted, issue the following commands to re-access the file system where the
vif command resides:
umount /dev/dasdb1
mount /dev/dasdb1 /usr/local/vif39 -r
If you encounter problems during the VIF service process, refer to Chapter 5, “VIF Support Procedures”
on page 15 for guidance.
14 Virtual Image Facility
| Chapter 5. VIF Support Procedures
There are two levels of support for VIF:
1. Program services are provided as part of the IBM basic Warranty services for VIF. Problems can be
reported via e-mail, facsimile, or regular mail. Anyone with a VIF license is entitled to this support.
Refer to the License Information Document (GC24-5933) and the Reader's Comments section of this
document for specific mailing information.
2. If SW Subscription and Support was ordered, via program number 5739-SPT for VIF, then service
support is provided as documented in the Addendum for Linux for S/390 Programs (Z125-6284). Also
refer to section “Service Information” on page 17 for further service information.
Problem Determination and Documentation Collection
Linux Problems
If you are experiencing problems with Linux itself, contact your Linux distributor or Linux service
organization.
VIF Problems
| Before you contact IBM, ensure that you are running the latest service level of VIF. New service levels of
| VIF are periodically made available. You can check the service level by issuing the following command:
| vif address query level
| Where address is the VIF hypervisor IP address.
| Informational APAR II12642 lists the latest service level available. If you are not running the latest service
| level of VIF, you can determine if your problem was resolved by a subsequent service level by reading the
| informational APAR. If this is the case, the latest service level should be ordered.
| If you are still experiencing problems, refer to “Troubleshooting” on page 16 for a possible cause of the
| problem you are experiencing. If the troubleshooting guide does not help with your problem then you
need to collect problem determination information to help figure out what the problem is.
If you are receiving error messages when running the vif command, do the following:
1. Access the master Linux image, known as LINUX0.
2. Make sure that the file system where the vif command resides is mounted.
mount /dev/dasdb1 /usr/local/vif39 -r
Also make sure the current directory is read/write.
 Copyright IBM Corp. 2000, 2001 15
3. Enter the following command to collect problem determination information (which will be saved in file
/collect.data):
vif address HYPERVISOR COLLECT
Where:
address is the VIF hypervisor IP address.
4. Contact IBM, based on the type of service support to which you are entitled. Be prepared to provide
the /collect.data file to IBM (for example, by sending it to a designated FTP dropoff site).
Troubleshooting
The following problems may occur when installing or running VIF.
Figure 2 (Page 1 of 2). Troubleshooting
Problem Probable Cause Possible Solution
Incorrect configuration data
entered during installation
Typographical error or erroneous
information
Obtain corrected information and
reinstall the system.
Wait state 1040 on IPL of VIF
installation tape
Device address specified in the
load parameter (AUTOxxxx) does
not exist
Correct the device address and
re-IPL the installation tape.
Wait state 9010 during VIF
initialization
TOD Clock is not set IPL a S/390 operating system to
set the clock.
Wait state 7002 during VIF
initialization
System verification failed Ensure all required hardware and
network resources are online.
Wait state 7004 during VIF
initialization
Paging volume could not be
mounted
Ensure hypervisor paging volumes
are online.
Wait state 7005 during VIF
initialization
Linux installation did not complete
successfully
Verify that the designated Linux
installation FTP server is running
and configured properly.
Wait state 7006 during VIF
initialization
System configuration could not be
created
Report the problem to IBM.
Wait state 7007 during VIF
initialization
Internal network could not be
started
Report the problem to IBM.
Wait state 7008 during VIF
initialization
Master Linux or other Linux images
could not be started
Report the problem to IBM.
Wait state 700B during VIF
initialization
Disk initialization error Initialize the installation volume
using ICKDSF and reinstall.
| Disabled wait PSW 000E0000
| 00000000
An old level of VIF is being used. Order the latest service tape for
VIF. Refer to informational APAR
| II12642 for details.
16 Virtual Image Facility
Service Information
If you have ordered 5739-SPT, SW Subscription and Support for S/390 Virtual Image Facility for LINUX,
on the processor where a problem is occurring, you can report any difficulties you encounter with VIF to
IBM using the contact information in the Addendum for Linux for S/390 Programs. In order to report a
problem to IBM you may need the following information.
Figure 3 lists the RETAIN component identifier (COMPID) and release for VIF.
| If you are having problems with VIF, refer to “VIF Problems” on page 15 for assistance.
Figure 2 (Page 2 of 2). Troubleshooting
Problem Probable Cause Possible Solution
| Any other disabled wait PSW Depends on the actual code
| causing the problem
Report the problem to your IBM
support personnel, if necessary.
Figure 3. Component IDs
Retain
COMPID Release Component Name
5739A0100 110 S/390 Virtual Image Facility for LINUX
Note: The VIF service process only supports tapes. When ordering service,
make sure you order a physical tape media that is supported by VIF.
Chapter 5. VIF Support Procedures 17
18 Virtual Image Facility
Chapter 6. VIF Command Reference
Notation
The following syntactic notation conventions are used in this chapter:
1. The required portion of a keyword is shown in upper case; the optional portion is shown in lower case
(for example, PARtition).
2. Alternative command operands are separated by vertical bars (|) or are shown one under another in a
column.
3. Optional command operands are enclosed in brackets ([ ]).
The general command syntax is:
vif address command function [operands]
Where:
address is the IP address of the VIF hypervisor.
command is the command to be executed.
function is the function to be executed.
operands are the parameters of the command.
VIF is managed using the following commands:
HELP displays command syntax.
HYPERVISOR manages VIF.
IMAGE manages Linux images.
PARTITION manages Linux DASD partitions.
QUERY displays configuration and activity information.
Each command is described below.
| Objects
The VIF administrative interface lets you manipulate several different kinds of objects. These objects, their
descriptions and how they are specified are as follows:
address an IP address in dotted-decimal form (for example, 9.130.58.78).
device a one- to four-digit hexadecimal number identifying a device.
Chapter 5. VIF Support Procedures 19
image an individual Linux system, with a one-to-eight character alphanumeric name that begins
| with an alphabetic character. Restrictions: Linux0 is reserved for use by VIF.
mask an IP mask in dotted-decimal form (for example, 255.255.240.0).
mtu a network Maximum Transmission Unit size in characters (for example, 1500).
partition an area of 3390 disk storage, identified by a device number and associated with an
image.
port a network device adapter number (for example, 0).
size a device or storage capacity in megabytes (for example, 100M).
string a sequence consisting of any printable characters.
type a local-area network type (ETHernet, TR, IBMTR, 802.3, FDDI, or CTCA).
| volid a 3390 disk storage volume serial number with a valid one-to-six character label (for
example, VIFPG7).
HELP Command
HELP reminds you what commands are available or summarizes the syntax of a particular command. The
command format is:
| Help [command]
| Help HYPERVISOR [function]
Where:
command is the command about which information is required. Omit the command name to obtain
a list of valid commands.
| function is a function of the HYPERVISOR command about which information is required. Omit
| the function name to obtain a list of valid HYPERVISOR functions.
HYPERVISOR Command
HYPERVISOR manages the VIF hypervisor. The format is:
HYPervisor function [operands]
Where:
function is the name of the function to be performed and can be COLLECT, ECHO, ERRORS,
EXPORT, IMPORT, INSTALL, NETWORK, RESTART, SERVICE, SHUTDOWN, VERIFY,
or VOLUME.
The HYPERVISOR command functions are described below.
20 Virtual Image Facility
HYPERVISOR COLLECT
HYPERVISOR COLLECT gathers VIF problem determination information and transfers it to Linux file
/collect.data. The current directory must be read/write. Use COLLECT under the direction of the IBM
Support Center to provide information to assist in problem diagnosis. The format is:
HYPervisor COLLect
| Note: The collect.data file is overwritten each time the HYPERVISOR COLLECT command is issued.
| Therefore, it is recommended to make a backup copy of this file if the iteration of the VIF problem
| determination information it contains needs to be saved.
HYPERVISOR ECHO
HYPERVISOR ECHO verifies connectivity with the VIF hypervisor. The format is:
HYPervisor ECHO
HYPERVISOR ERRORS
HYPERVISOR ERRORS creates a report of hardware errors for IBM service personnel in file
/ereprept.yyyymmdd, where yyyymmdd is the current date. The current directory must be read/write. The
format is:
HYPervisor ERRors
HYPERVISOR EXPORT
HYPERVISOR EXPORT creates a backup of the system configuration in Linux file /config.save. The
current directory must be read/write. The format is:
HYPervisor EXPort
| Note: The config.save file is overwritten each time the HYPERVISOR EXPORT command is issued.
| Therefore, it is recommended to make a backup copy of this file if the iteration of the VIF system
| configuration information it contains needs to be saved.
HYPERVISOR IMPORT
HYPERVISOR IMPORT restores a backup of the system configuration from Linux file /config.save. The
format is:
HYPervisor IMPort
Chapter 6. VIF Command Reference 21
HYPERVISOR INSTALL
HYPERVISOR INSTALL replaces the Linux installation configuration file and the files it references (usually
a Linux kernel, parameter file, and RAM disk). You specify the network location of the installation
configuration file to be used. Use INSTALL to create a new Linux recovery system to replace one that
was created during VIF installation or by a previous use of the INSTALL function. The format is:
| HYPervisor INSTall address user password [account] location
Where:
address is the IP address of the FTP server where the files to be installed reside.
user is the user name to be supplied to the FTP server.
password is the password to be supplied to the FTP server.
| account is the account, if required, to be supplied to the FTP server. This operand is optional.
location is the path and file name of the Linux installation file to be installed.
HYPERVISOR NETWORK
HYPERVISOR NETWORK is used to ADD, CHANGE, or DELETE hypervisor or internal network
connections or to change the hypervisor GATEWAY. The format is:
HYPervisor NETwork ADD device port type mtu address mask
ADD image address mask
CHAnge device port type mtu address mask
CHAnge image address mask
DELete device
DELete image
GATEway address
Where:
device is the even device number of the even-odd network device pair to be added to, changed
in, or deleted from the VIF hypervisor network configuration.
port is the port number associated with the device.
type is the network type.
mtu is the MTU size.
address is the IP address associated with the device or with the network gateway.
mask is the IP mask associated with the address.
image is the name of the image whose internal network connection is to be added, changed, or
deleted.
22 Virtual Image Facility
HYPERVISOR RESTART
HYPERVISOR RESTART restarts the hypervisor and all Linux images. The format is:
HYPervisor RESTART
Note: Prior to issuing this command you should do a halt on the active Linux images, if possible, in order
to avoid startup delays due to Linux file system validation. This would require logging on to the console of
each Linux image.
HYPERVISOR SERVICE
HYPERVISOR SERVICE installs hypervisor service from a service tape mounted on a tape drive. The
format is:
HYPervisor SERVice device
Where:
device specifies the device number of the tape drive where the service tape is mounted.
HYPERVISOR SHUTDOWN
HYPERVISOR SHUTDOWN shuts down the hypervisor and all Linux images. The format is:
HYPervisor SHUTDOWN RECONFigure
Where:
RECONFigure causes reconfiguration of the system.
HYPERVISOR VERIFY
HYPERVISOR VERIFY performs consistency checks of the VIF environment or verifies that there is
network connectivity with a particular Linux image. The format is:
HYPervisor VERify FULL
BRIef
NETwork image
Where:
FULL causes a complete verification of the environment.
BRIef causes a partial verification of the environment that is suitable for establishing its overall
consistency.
NETwork verifies connectivity between the VIF hypervisor and a particular Linux image.
image is the name of the image whose connectivity is to be verified.
Chapter 6. VIF Command Reference 23
HYPERVISOR VOLUME
HYPERVISOR VOLUME adds paging or image DASD volumes to the hypervisor configuration, removes
these volumes from the configuration, reports the utilization of such volumes, or initializes a new volume.
The format is:
HYPervisor VOLume ADD IMAGE|PAGING device volid
DELete IMAGE|PAGING device|volid
MAP USED|FREE [device|volid]
INITialize device
Where:
IMAGE specifies that volumes for image use are to be added or deleted.
PAGING specifies that volumes for paging use are to be added or deleted.
USED specifies that space in use on an image volume is to be reported.
FREE specifies that available space on an image volume is to be reported.
device is the number of the device to be added, deleted, mapped, or initialized.
volid is the volid of the device to be added, deleted, or mapped.
IMAGE Command
IMAGE manages Linux system images. The format is:
IMAGE function [operands]
Where:
function is the image management function to be performed and can be CREATE, DELETE,
NETWORK, SET, START, or STOP.
The functions of the IMAGE command are described below.
IMAGE CREATE
IMAGE CREATE defines a new Linux image. The format is:
IMAGE CREATE image
Where:
image is the name to be assigned to the new image.
24 Virtual Image Facility
IMAGE DELETE
IMAGE DELETE removes a Linux image and all its associated resources. The format is:
IMAGE DELete image
Where:
image is the name of the image to be deleted.
IMAGE NETWORK
IMAGE NETWORK adds or deletes network connections for a Linux image. The format is:
IMAGE NETwork image ADD|DELete device
Where:
image is the name of the image whose network device is to be added or deleted.
ADD specifies that the network device is to be added to the image configuration.
DELete specifies that the network device is to be removed from the image configuration.
device is the even device number of the even-odd network device pair to be added or deleted.
IMAGE SET
IMAGE SET changes the storage size, number of processors, or the boot device for a Linux image. The
format is:
IMAGE SET image STOrage size
CPUs number
BOOT device|DEFAULT
Where:
image is the name of the image whose storage size, number of CPUs, or boot device is to be
changed.
STOrage specifies that the image storage size is to be changed.
size is the new image storage size in megabytes.
CPUs specifies that the number of image CPUs is to be changed.
number is the new number of image CPUs.
BOOT specifies that the image boot device is to be changed.
device is the number of the device from which the image is to boot.
DEFAULT specifies that the image is to boot from the recovery system installed either during system
configuration or using the HYPERVISOR command INSTALL function.
Chapter 6. VIF Command Reference 25
IMAGE START
IMAGE START activates and boots a Linux image. The format is:
IMAGE START image
Where:
image is the name of the image to be started.
Note: To automate activating Linux images at system startup, you can write a shell script to control the
order and number of Linux images started at one time. It is recommended that you do not start all your
Linux images at one time.
IMAGE STOP
IMAGE STOP terminates a Linux image. The format is:
IMAGE STOP image
Where:
image is the name of the image to be stopped.
Note: Before stopping an image using this command it is recommended that you shut down Linux first.
This will avoid delays when the Linux image is restarted.
IMAGE STOPALL
IMAGE STOPALL terminates all the Linux images on your system. The format is:
IMAGE STOPALL
Note: Before stopping your Linux images, it is recommended that you shut down the Linux systems first.
This will avoid delays when the images are restarted.
PARTITION Command
PARTITION manages DASD partitions. The format is:
PARtition function [operands]
Where:
function specifies the function to be performed and can be COPY, CREATE, DELETE,
INITIALIZE, SHARE, or SWAP.
The PARTITION command functions are described below.
26 Virtual Image Facility
PARTITION COPY
PARTITION COPY adds a partition to a Linux image and initialize its contents from a partition that belongs
to the same or another image. The format is:
PARtition COPY image1 device1 [TO] image2 device2
Where:
image1 is the name of the image whose partition is to be copied.
device1 is the device number of the partition to be copied.
TO is an optional keyword
image2 is the name of the image to which the partition is to be added.
device2 is the device number of the new partition.
PARTITION CREATE
PARTITION CREATE adds a partition to a Linux image. The format is:
PARtition CREATE image device size
Where:
image is the name of the image to which the partition is to be added.
device is the device number of the new partition.
size is the size of the new partition in megabytes.
PARTITION DELETE
PARTITION DELETE removes a partition from a Linux image. The format is:
PARtition DELete image device
Where:
image is the name of the image from which the partition is to be deleted.
device is the device number of the partition to be deleted.
PARTITION INITIALIZE
PARTITION INITIALIZE initializes a partition for use by Linux. The format is:
PARtition INITialize image device
Where:
image is the name of the image whose partition is to be initialized.
device is the device number of the partition to be initialized.
Chapter 6. VIF Command Reference 27
PARTITION SHARE
PARTITION SHARE gives one Linux image read-only access to another's partition. The format is:
PARtition SHARE image1 device1 [WITH] image2 device2
Where:
image1 is the name of the image whose partition is to be shared.
device1 is the device number of the shared partition.
WITH is an optional keyword
image2 is the name of the image that is to share the partition.
device2 is the device number of the sharing partition.
PARTITION SWAP
PARTITION SWAP interchanges the device numbers of two partitions that belong to one Linux image.
The format is:
PARtition SWAP image device1 [WITH] device2
Where:
image is the name of the image whose partitions are to be interchanged.
device1 is the device number of the first partition.
WITH is an optional keyword
device2 is the device number of the second partition.
QUERY Command
QUERY displays information about your VIF configuration and activity. The command format is:
Query function [operands]
Where:
function specifies the information to be displayed and can be ACTIVE, ALL, BOOT,
CONFIGURATION, ERRORS, IMAGE, LEVEL, NETWORK, PAGING, PARTITIONS,
PERFORMANCE, SHARED, or VOLUMES
operands further qualify the information to be displayed for some functions.
The functions of the QUERY command are described below.
28 Virtual Image Facility
QUERY ACTIVE
QUERY ACTIVE reports which Linux images are running. The format is:
Query ACTive
QUERY ALL
QUERY ALL invokes all the functions of the QUERY command. The format is:
Query ALL
QUERY BOOT
QUERY BOOT reports when the VIF hypervisor was booted. The format is:
Query BOOt
QUERY CONFIGURATION
QUERY CONFIGURATION displays the current configuration settings of the VIF system. The format is:
Query CONFiguration
QUERY ERRORS
QUERY ERRORS indicates whether there are hardware errors that need to be reported. The format is:
Query ERRors
QUERY IMAGE
QUERY IMAGE displays the configuration of a Linux image. The format is:
Query IMAGE [image]
Where:
image is the name of the image whose configuration is to be displayed. If the image name is
omitted, all image configurations are displayed.
QUERY LEVEL
QUERY LEVEL reports the level of the VIF hypervisor. The format is:
Query LEVel
Chapter 6. VIF Command Reference 29
QUERY NETWORK
QUERY NETWORK displays the network configuration. The format is:
Query NETwork
QUERY PAGING
QUERY PAGING displays the hypervisor paging configuration. The format is:
Query PAGING
QUERY PARTITIONS
QUERY PARTITIONS displays information about the Linux image DASD utilization. The format is:
Query PARtitions
Note: To see the layout of partitions on the DASD volumes, use the HYPervisor VOLumes MAP USED
volid command.
QUERY PERFORMANCE
QUERY PERFORMANCE displays the current performance levels of the system that is running VIF. The
format is:
Query PERformance
QUERY SHARED
QUERY SHARED displays the names of the images that share another image's partitions. The format is:
Query SHARED [image]
Where:
image is the name of the image whose shared partitions are to be listed. If the image name is
omitted, the shared partitions of all images are listed.
QUERY VOLUMES
QUERY VOLUMES displays the image and paging DASD volumes volid and device number. The format
is:
Query VOLumes
30 Virtual Image Facility
| Appendix A. Installation Prompts Checklist
| Installation Prompts Fill In Answers
| 1. Your choice of sysres volid for VIF (1-6 characters)
| The label to be assigned to the 3390 volume where VIF will be installed.
| 2. OSA device address for VIF hypervisor
| The even address of the network device pair that is assigned to the VIF hypervisor for network
| access.
| 3. And the OSA device port number
| The number of the port associated with the network device pair that is assigned to the VIF
| hypervisor.
| 4. VIF hypervisor network type (Ethernet, Token-Ring, 802.3, or FDD)
| The type of local-area network (LAN) to which the hypervisor is connected.
| 5. VIF hypervisor network MTU size (576, 1492, 1500, 2000, or 4096)
| The Maximum Transmission Unit of the VIF hypervisor LAN.
| 6. VIF hypervisor IP address
| The IP address assigned to the hypervisor.
| 7. And the hypervisor subnet mask
| The IP mask associated with the hypervisor IP address.
| 8. IP address of gateway to be used by VIF
| The IP address of the default gateway on the VIF hypervisor LAN.
| 9A. Master Linux network type (Internal or External)
| The type of network connection to be used by the master Linux image. If a network device pair
| is available, specify External. Otherwise, specify Internal.
| 9B. Enter master Linux network device address:
| Note: If an External network connection is provided for the master Linux image, specify the
| even address of the network device pair.
| 10. IP address of the master Linux image
| The IP address assigned to the master Linux image.
| Note: This address must be in a subnet different than the subnet where the IP address is for the
| LAN gateway that you are using.
| 11. And the subnet mask for the master Linux image
| The IP mask associated with the master Linux image IP address.
| 12. The IP address of the FTP Server for the Linux distribution
| The IP address of the FTP server where the Linux distribution files are located.
| 13. The user name for the FTP server
| The user name to be used to connect to the FTP server where the Linux distribution files are
| located.
| 14. And the password for the FTP server
| The password to be used to connect to the FTP server.
| 15. The FTP account information, if needed
| The account number to be used to access the FTP server, or null if no account information is
| required.
| 16. The path and file name of the Linux installation file on the FTP server
| The path and file name on the FTP server of the Linux installation file.
 Copyright IBM Corp. 2000, 2001 31
32 Virtual Image Facility
Notices
IBM may not offer the products, services, or features
described in this document in other countries. Consult
your local IBM representative for information on the
products and services currently available in your area.
Any reference to an IBM product, program, or service is
not intended to state or imply that only that IBM
product, program, or service may be used. Any
functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility
to evaluate and verify the operation of any non-IBM
product, program, or service.
IBM may have patents or pending patent applications
covering subject matter described in this document.
The furnishing of this document does not give you any
license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 1 5 4-1785
U.S.A.
For license inquiries regarding double-byte (DBCS)
information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing,
to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 1 6, Japan
The following paragraph does not apply to the
United Kingdom or any other country where such
provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES
CORPORATION PROVIDES THIS PUBLICATION “AS
IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. Some
states do not allow disclaimer of express or implied
warranties in certain transactions; therefore, this
statement may not apply to you.
This information could include technical inaccuracies or
typographical errors. Changes are periodically made to
the information herein; these changes will be
incorporated in new editions of the publication. IBM
may make improvements and/or changes to the
product(s) and/or the program(s) described in this
publication at any time without notice.
IBM may use or distribute any of the information you
supply in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who wish to have information
about it for the purpose of enabling: (i) the exchange of
information between independently created programs
and other programs (including this one) and (ii) the
mutual use of the information that has been exchanged,
should contact:
IBM Corporation
Mail Station P3
2455 South Road
Poughkeepsie, NY 126 1-54
U.S.A.
Such information may be available subject to
appropriate terms and conditions, including in some
cases payment of a fee.
The licensed program described in this document and
all licensed material available for it are provided by IBM
under terms of the IBM Customer Agreement, IBM
International Program License Agreement or any
equivalent agreement between us.
Any performance data contained herein was determined
in a controlled environment. Therefore, the results
obtained in other operating environments may vary
significantly. Some measurements may have been
made on development-level systems and there is no
guarantee that these measurements will be the same
on generally available systems. Furthermore, some
measurement may have been estimated through
extrapolation. Actual results may vary. Users of this
document should verify the applicable data for their
specific environment.
 Copyright IBM Corp. 2000, 2001 33
Information concerning non-IBM products was obtained
from the suppliers of those products, their published
announcements or other publicly available sources.
IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility or any other
claims related to non-IBM products. Questions on the
capabilities on non-IBM products should be addressed
to the suppliers of those products.
All statements regarding IBM's future direction or intent
are subject to change or withdrawal without notice, and
represent goals and objectives only.
Programming Interface
Information
This book documents information NOT intended to be
used as Programming Interfaces of S/390 Virtual Image
Facility for LINUX.
Trademarks and Service Marks
The following terms are trademarks of the International
Business Machines Corporation (IBM) in the United
States, other countries, or both:
IBM
Multiprise
RETAIN
S/390
Virtual Image Facility
LINUX is a registered trademark of Linus Torvalds in
the United States, other countries, or both.
Other company, product, and service names may be
trademarks or service marks of others.
34 Virtual Image Facility
Index
A
administering your VIF system 11
B
before you start 7
C
Commands
entering 11
HELP 20
HYPERVISOR 20
HYPERVISOR COLLECT 21
HYPERVISOR ECHO 21
HYPERVISOR ERRORS 21
HYPERVISOR EXPORT 21
HYPERVISOR IMPORT 21
HYPERVISOR INSTALL 22
HYPERVISOR NETWORK 22
HYPERVISOR RESTART 23
HYPERVISOR SERVICE 23
HYPERVISOR SHUTDOWN 23
HYPERVISOR VERIFY 23
HYPERVISOR VOLUME 24
IMAGE 24
IMAGE CREATE 24
IMAGE DELETE 25
IMAGE NETWORK 25
IMAGE SET 25
IMAGE START 26
IMAGE STOP 26
IMAGE STOPALL 26
PARTITION 26
PARTITION COPY 27
PARTITION CREATE 27
PARTITION DELETE 27
PARTITION INITIALIZE 27
PARTITION SHARE 28
PARTITION SWAP 28
QUERY 28
QUERY ACTIVE 29
QUERY ALL 29
Commands (continued)
QUERY BOOT 29
QUERY CONFIGURATION 29
QUERY ERRORS 29
QUERY IMAGE 29
QUERY LEVEL 29
QUERY NETWORK 30
QUERY PAGING 30
QUERY PARTITIONS 30
QUERY PERFORMANCE 30
QUERY SHARED 30
QUERY VOLUMES 30
syntax 11, 19
configuration data incorrect 16
D
documentation collection 15
E
entering VIF commands 11
H
hardware requirements 4
HELP command 20
HYPERVISOR COLLECT command 21
HYPERVISOR command 20
HYPERVISOR ECHO command 21
HYPERVISOR ERRORS command 21
HYPERVISOR EXPORT command 21
HYPERVISOR IMPORT command 21
HYPERVISOR INSTALL command 22
HYPERVISOR NETWORK command 22
HYPERVISOR RESTART command 23
HYPERVISOR SERVICE command 23
HYPERVISOR SHUTDOWN command 23
HYPERVISOR VERIFY command 23
HYPERVISOR VOLUME command 24
 Copyright IBM Corp. 2000, 2001 35
I
IMAGE command 24
image console access 12
IMAGE CREATE command 24
IMAGE DELETE command 25
IMAGE NETWORK command 25
IMAGE SET command 25
IMAGE START command 26
IMAGE STOP command 26
IMAGE STOPALL command 26
installation checklist 5
installation procedure 7
installing S/390 Virtual Image Facility for LINUX 3, 7
installing VIF 3, 7
introduction to S/390 Virtual Image Facility for
LINUX 1
L
Linux problems 15
M
master Linux image 12
N
network requirements 4
notation 19
O
objects 19
P
PARTITION command 26
PARTITION COPY command 27
PARTITION CREATE command 27
PARTITION DELETE command 27
PARTITION INITIALIZE command 27
PARTITION SHARE command 28
PARTITION SWAP command 28
planning for installation 3
post-installation tasks 9
prerequisites for installation 7
problem determination 15
processor sizing 5
product tape 3
Q
QUERY ACTIVE command 29
QUERY ALL command 29
QUERY BOOT command 29
QUERY command 28
QUERY CONFIGURATION command 29
QUERY ERRORS command 29
QUERY IMAGE command 29
QUERY LEVEL command 29
QUERY NETWORK command 30
QUERY PAGING command 30
QUERY PARTITIONS command 30
QUERY PERFORMANCE command 30
QUERY SHARED command 30
QUERY VOLUMES command 30
S
S/390 Virtual Image Facility for LINUX
administering your VIF system 11
checklist for installation 5
Commands
entering 11
HELP 20
HYPERVISOR 20
HYPERVISOR COLLECT 21
HYPERVISOR ECHO 21
HYPERVISOR ERRORS 21
HYPERVISOR EXPORT 21
HYPERVISOR IMPORT 21
HYPERVISOR INSTALL 22
HYPERVISOR NETWORK 22
HYPERVISOR RESTART 23
HYPERVISOR SERVICE 23
HYPERVISOR SHUTDOWN 23
HYPERVISOR VERIFY 23
HYPERVISOR VOLUME 24
IMAGE 24
IMAGE CREATE 24
IMAGE DELETE 25
IMAGE NETWORK 25
IMAGE SET 25
IMAGE START 26
36 Virtual Image Facility
S/390 Virtual Image Facility for LINUX (continued)
Commands (continued)
IMAGE STOP 26
IMAGE STOPALL 26
notation 19
PARTITION 26
PARTITION COPY 27
PARTITION CREATE 27
PARTITION DELETE 27
PARTITION INITIALIZE 27
PARTITION SHARE 28
PARTITION SWAP 28
QUERY 28
QUERY ACTIVE 29
QUERY ALL 29
QUERY BOOT 29
QUERY CONFIGURATION 29
QUERY ERRORS 29
QUERY IMAGE 29
QUERY LEVEL 29
QUERY NETWORK 30
QUERY PAGING 30
QUERY PARTITIONS 30
QUERY PERFORMANCE 30
QUERY SHARED 30
QUERY VOLUMES 30
syntax 11, 19
documentation collection 15
hardware requirements 4
HELP command 20
HYPERVISOR COLLECT command 21
HYPERVISOR command 20
HYPERVISOR ECHO command 21
HYPERVISOR ERRORS command 21
HYPERVISOR EXPORT command 21
HYPERVISOR IMPORT command 21
HYPERVISOR INSTALL command 22
HYPERVISOR NETWORK command 22
HYPERVISOR RESTART command 23
HYPERVISOR SERVICE command 23
HYPERVISOR SHUTDOWN command 23
HYPERVISOR VERIFY command 23
HYPERVISOR VOLUME command 24
IMAGE command 24
image console access 12
IMAGE CREATE command 24
IMAGE DELETE command 25
S/390 Virtual Image Facility for LINUX (continued)
IMAGE NETWORK command 25
IMAGE SET command 25
IMAGE START command 26
IMAGE STOP command 26
IMAGE STOPALL command 26
installing 3
introduction 1
Linux problems 15
network requirements 4
objects 19
overview 1
PARTITION command 26
PARTITION COPY command 27
PARTITION CREATE command 27
PARTITION DELETE command 27
PARTITION INITIALIZE command 27
PARTITION SHARE command 28
PARTITION SWAP command 28
planning for installation 3
post-installation tasks 9
prerequisites for installation 7
problem determination 15
problems 15
processor sizing 5
product tape 3
QUERY ACTIVE command 29
QUERY ALL command 29
QUERY BOOT command 29
QUERY command 28
QUERY CONFIGURATION command 29
QUERY ERRORS command 29
QUERY IMAGE command 29
QUERY LEVEL command 29
QUERY NETWORK command 30
QUERY PAGING command 30
QUERY PARTITIONS command 30
QUERY PERFORMANCE command 30
QUERY SHARED command 30
QUERY VOLUMES command 30
sample environment 1
service information 17
servicing 13
sizing guidelines for a VIF LPAR 4
software requirements 4
storage sizing 5
support procedures 15
Index 37
S/390 Virtual Image Facility for LINUX (continued)
troubleshooting 16
wait states 16
sample S/390 Virtual Image Facility for LINUX
environment 1
service information 17
servicing VIF 13
sizing guidelines for a VIF LPAR 4
software requirements 4
storage sizing 5
syntax of VIF commands 11, 19
T
troubleshooting 16
U
using the master Linux image 12
using VIF support procedures 15
V
VIF
administering your VIF system 11
checklist for installation 5
Commands
entering 11
HELP 20
HYPERVISOR 20
HYPERVISOR COLLECT 21
HYPERVISOR ECHO 21
HYPERVISOR ERRORS 21
HYPERVISOR EXPORT 21
HYPERVISOR IMPORT 21
HYPERVISOR INSTALL 22
HYPERVISOR NETWORK 22
HYPERVISOR RESTART 23
HYPERVISOR SERVICE 23
HYPERVISOR SHUTDOWN 23
HYPERVISOR VERIFY 23
HYPERVISOR VOLUME 24
IMAGE 24
IMAGE CREATE 24
IMAGE DELETE 25
IMAGE NETWORK 25
IMAGE SET 25
IMAGE START 26
IMAGE STOP 26
VIF (continued)
Commands (continued)
IMAGE STOPALL 26
notation 19
PARTITION 26
PARTITION COPY 27
PARTITION CREATE 27
PARTITION DELETE 27
PARTITION INITIALIZE 27
PARTITION SHARE 28
PARTITION SWAP 28
QUERY 28
QUERY ACTIVE 29
QUERY ALL 29
QUERY BOOT 29
QUERY CONFIGURATION 29
QUERY ERRORS 29
QUERY IMAGE 29
QUERY LEVEL 29
QUERY NETWORK 30
QUERY PAGING 30
QUERY PARTITIONS 30
QUERY PERFORMANCE 30
QUERY SHARED 30
QUERY VOLUMES 30
syntax 11, 19
documentation collection 15
hardware requirements 4
HELP command 20
HYPERVISOR COLLECT command 21
HYPERVISOR command 20
HYPERVISOR ECHO command 21
HYPERVISOR ERRORS command 21
HYPERVISOR EXPORT command 21
HYPERVISOR IMPORT command 21
HYPERVISOR INSTALL command 22
HYPERVISOR NETWORK command 22
HYPERVISOR RESTART command 23
HYPERVISOR SERVICE command 23
HYPERVISOR SHUTDOWN command 23
HYPERVISOR VERIFY command 23
HYPERVISOR VOLUME command 24
IMAGE command 24
image console access 12
IMAGE CREATE command 24
IMAGE DELETE command 25
IMAGE NETWORK command 25
38 Virtual Image Facility
VIF (continued)
IMAGE SET command 25
IMAGE START command 26
IMAGE STOP command 26
IMAGE STOPALL command 26
installing 3
introduction 1
Linux problems 15
network requirements 4
objects 19
overview 1
PARTITION command 26
PARTITION COPY command 27
PARTITION CREATE command 27
PARTITION DELETE command 27
PARTITION INITIALIZE command 27
PARTITION SHARE command 28
PARTITION SWAP command 28
planning for installation 3
post-installation tasks 9
prerequisites for installation 7
problem determination 15
problems 15
processor sizing 5
product tape 3
QUERY ACTIVE command 29
QUERY ALL command 29
QUERY BOOT command 29
QUERY command 28
QUERY CONFIGURATION command 29
QUERY ERRORS command 29
QUERY IMAGE command 29
QUERY LEVEL command 29
QUERY NETWORK command 30
QUERY PAGING command 30
QUERY PARTITIONS command 30
QUERY PERFORMANCE command 30
QUERY SHARED command 30
QUERY VOLUMES command 30
sample environment 1
service information 17
servicing 13
sizing guidelines for a VIF LPAR 4
software requirements 4
storage sizing 5
support procedures 15
troubleshooting 16
VIF (continued)
wait states 16
Virtual Image Facility
administering your VIF system 11
checklist for installation 5
Commands
entering 11
HELP 20
HYPERVISOR 20
HYPERVISOR COLLECT 21
HYPERVISOR ECHO 21
HYPERVISOR ERRORS 21
HYPERVISOR EXPORT 21
HYPERVISOR IMPORT 21
HYPERVISOR INSTALL 22
HYPERVISOR NETWORK 22
HYPERVISOR RESTART 23
HYPERVISOR SERVICE 23
HYPERVISOR SHUTDOWN 23
HYPERVISOR VERIFY 23
HYPERVISOR VOLUME 24
IMAGE 24
IMAGE CREATE 24
IMAGE DELETE 25
IMAGE NETWORK 25
IMAGE SET 25
IMAGE START 26
IMAGE STOP 26
IMAGE STOPALL 26
notation 19
PARTITION 26
PARTITION COPY 27
PARTITION CREATE 27
PARTITION DELETE 27
PARTITION INITIALIZE 27
PARTITION SHARE 28
PARTITION SWAP 28
QUERY 28
QUERY ACTIVE 29
QUERY ALL 29
QUERY BOOT 29
QUERY CONFIGURATION 29
QUERY ERRORS 29
QUERY IMAGE 29
QUERY LEVEL 29
QUERY NETWORK 30
QUERY PAGING 30
QUERY PARTITIONS 30
Index 39
Virtual Image Facility (continued)
Commands (continued)
QUERY PERFORMANCE 30
QUERY SHARED 30
QUERY VOLUMES 30
syntax 11, 19
documentation collection 15
hardware requirements 4
HELP command 20
HYPERVISOR COLLECT command 21
HYPERVISOR command 20
HYPERVISOR ECHO command 21
HYPERVISOR ERRORS command 21
HYPERVISOR EXPORT command 21
HYPERVISOR IMPORT command 21
HYPERVISOR INSTALL command 22
HYPERVISOR NETWORK command 22
HYPERVISOR RESTART command 23
HYPERVISOR SERVICE command 23
HYPERVISOR SHUTDOWN command 23
HYPERVISOR VERIFY command 23
HYPERVISOR VOLUME command 24
IMAGE command 24
image console access 12
IMAGE CREATE command 24
IMAGE DELETE command 25
IMAGE NETWORK command 25
IMAGE SET command 25
IMAGE START command 26
IMAGE STOP command 26
IMAGE STOPALL command 26
installing 3
introduction 1
Linux problems 15
network requirements 4
objects 19
overview 1
PARTITION command 26
PARTITION COPY command 27
PARTITION CREATE command 27
PARTITION DELETE command 27
PARTITION INITIALIZE command 27
PARTITION SHARE command 28
PARTITION SWAP command 28
planning for installation 3
post-installation tasks 9
prerequisites for installation 7
Virtual Image Facility (continued)
problem determination 15
problems 15
processor sizing 5
product tape 3
QUERY ACTIVE command 29
QUERY ALL command 29
QUERY BOOT command 29
QUERY command 28
QUERY CONFIGURATION command 29
QUERY ERRORS command 29
QUERY IMAGE command 29
QUERY LEVEL command 29
QUERY NETWORK command 30
QUERY PAGING command 30
QUERY PARTITIONS command 30
QUERY PERFORMANCE command 30
QUERY SHARED command 30
QUERY VOLUMES command 30
sample environment 1
service information 17
servicing 13
sizing guidelines for a VIF LPAR 4
software requirements 4
storage sizing 5
support procedures 15
troubleshooting 16
wait states 16
W
when you are done 9
40 Virtual Image Facility
Index 41
Communicating Your Comments to IBM
S/390 Virtual Image Facility for LINUX
Version 1
Publication No. GC24-5930-03
If you especially like or dislike anything about this book, please use one of the methods listed below to send your
comments to IBM. Whichever method you choose, make sure you send your name, address, and telephone number
if you would like a reply.
Feel free to comment on specific errors or omissions, accuracy, organization, subject matter, or completeness of this
book. However, the comments you send should pertain to only the information in this manual and the way in which
the information is presented. To request additional publications, or to ask questions or make comments about the
functions of IBM products or systems, you should talk to your IBM representative or to your IBM authorized
remarketer.
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way
it believes appropriate without incurring any obligation to you.
If you are mailing a readers' comment form (RCF) from a country other than the United States, you can give the RCF
to the local IBM branch office or IBM representative for postage-paid mailing.

If you prefer to send comments by mail, use the RCF at the back of this book.

If you prefer to send comments by FAX, use this number:
1-607-752-2327 (US and Canada)

If you prefer to send comments electronically, use this network ID:
pubrcf@vnet.ibm.com
Make sure to include the following in your note:

Title and publication number of this book

Page number or topic to which your comment applies.
Readers' Comments — We'd Like to Hear from You
S/390 Virtual Image Facility for LINUX
Version 1
Publication No. GC24-5930-03
Overall, how satisfied are you with the information in this book?
How satisfied are you that the information in this book is:
Please tell us how we can improve this book:
Thank you for your responses. May we contact you?  Yes  No
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments
in any way it believes appropriate without incurring any obligation to you.
Name Address
Company or Organization
Phone No.
Very
Satisfied Satisfied Neutral Dissatisfied
Very
Dissatisfied
Overall satisfaction     
Very
Satisfied Satisfied Neutral Dissatisfied
Very
Dissatisfied
Accurate     
Complete     
Easy to find     
Easy to understand     
Well organized     
Applicable to your tasks     
Cut or Fold
Along Line
Cut or Fold
Along Line
Readers' Comments — We'd Like to Hear from You
GC24-5930-03 IBM
Fold and Tape Please do not staple Fold and Tape
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
BUSINESS REPLY MAIL
FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK
POSTAGE WILL BE PAID BY ADDRESSEE
IBM Corporation
Information Development
Department G60G
1701 North Street
Endicott, New York 13760-5553
Fold and Tape Please do not staple Fold and Tape
GC24-5930-03

IBM
Printed in U.S.A.
GC24-593 - 3