ZVM17: z/vm Device Support Overview

Transcription

1 IBM System z Technical University Berlin, Germany May ZVM17: z/vm Device Support Overview Eric Farman, IBM

2 Trademarks The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both. Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market. For a complete list of IBM Trademarks, see The following are trademarks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce. * All other products may be trademarks or registered trademarks of their respective companies. Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-ibm products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography. 2

3 Agenda Overview Dedicated OSAs QDIO Protocol Dedicated FCP QIOASSIST Tape DASD MDC VDISK Guest Coupling References 3

4 Overview Various areas of z/vm device support will be presented Both device support provided for guest operating systems and for managing and running the z/vm hypervisor (commonly known as 'native' support) will be covered; many times there ARE differences This information is intended for audiences not deeply familiar with z/vm device support, or for those wanting an overview of what is new 4

5 Levels of Device Support z/vm provides device support via the Control Program (CP) Dedicated or ATTACHed A guest has exclusive use of the entire real device CP involvement is minimal Virtualized CP presents an image of a real device to multiple virtual machines; or CP subdivides a real device such that a portion appears real to a guest (e.g., minidisk) CP is more involved with a virtualized device, but benefits (such as minidisk cache) may outweigh the drawbacks Emulated or Simulated CP emulates a piece of real hardware as some other type of hardware; or CP completely simulates a device without the existence of real hardware Examples: SCSI LUNs emulated as 9336 FBA DASD Virtual disks in storage (VDISK) Guest LAN CP involvement is the highest with emulated or simulated devices 5

6 Queued Direct I/O (QDIO) Protocol OSA Express, FCP, and HiperSockets subchannels use QDIO protocol for data transmission, rather than traditional z/architecture Start Subchannel The QDIO protocol provides: Memory mapped data transmission Direction communication between guest and adapter Data transmission via a set of queues allocated in guest storage 6

7 OSA OSA Express Provides IP Ethernet connectivity to/from a physical LAN Data transmission is done by an OSA Express Adapter Card Requires OSA Express CHPIDs on Adapter Card to be installed and defined in IOCP Each CHPID contains 240 or more subchannels, depending on hardware HiperSockets Provides IP Ethernet connectivity between Logical Partitions (LPARs) without a physical LAN or hardware adapter card Devices defined by IOCP Data transmission is performed by hardware millicode Subchannels dedicated to a guest virtual machine for its sole use by CP ATTACH command or DEDICATE User Directory Statement Used by guest running a z/vm TCP/IP Stack Use CP Query Virtual OSA or Query <virtual device> to display connection status 7

8 IP QDIO Connection Minimum of 3 QDIO-capable subchannels are required to establish an IP QDIO connection on a Guest IP Stack Dynamically (Class B): ATTACH TO HIPER1 At LOGON: DEDICATE DEDICATE DEDICATE z/vm LPAR HIPER1 Virtual Machine Device 100 Read Control Device 101 Write Control Device 102 Data z/vm CCW Translation OSA/HiperSockets Adapter 8

9 FCP QDIO Connection Provides connectivity to Fibre-channel Storage Area Network (SAN) via FICON Express Adapter Card Provides access to SCSI devices Requires FCP CHPIDs on Adapter Card to be installed and defined in IOCP Each CHPID contains 240 or more subchannels, depending on hardware Subchannels dedicated to a guest virtual machine for its sole use by CP ATTACH command or DEDICATE User Directory Statement Guest is responsible for FCP and SCSI protocol drivers z/vm attaches subchannels to SYSTEM during EDEVice processing for host connections; see Session ZVM14 Use CP Query Virtual FCP or Query <virtual device> to display connection status 9

10 Hardware I/O Assist Allows guest I/O instructions to go directly to the device without the need for z/vm to intercept the instructions, translate addresses, perform validity checks, or perform other types of simulation Allows I/O interrupts to go directly to the guest without the need for z/vm to take interrupts, translate addresses, perform validity checks, or perform other simulation Improves guest I/O performance to near-native performance by avoiding I/O instruction interceptions and I/O interrupts for assisted subchannels 10

11 Queued Direct I/O Assist (QIOASSIST) Benefits all V=V guests with QDIO OSA or FCP subchannels Provides virtual interrupt passthru beginning with z/vm Enhanced in z/vm to provide assists for z/vm page translation, page locking, and shadow queue processing Minimum hardware is z890 or z990, in LPAR-mode only Enabled by default Can be disabled on a per-device basis with the NOQIOAssist operand on the CP ATTACH command or DEDICATE User Directory Statement Can be disabled on a per-guest basis with the CP SET QIOAssist command 11

12 Tape z/vm uses FICON-attached tape drives for native system functions Backing up disk volumes with DASD Dump/Restore (DDR) utility Backing up system spool data with CP SPXTAPE command Backing up CMS Minidisk files with CMS TAPE command Storing system trace data with the CP TRSAVE command Managing volumes from an Automated Tape Library (ATL) with the DFSMS/VM RMS Service Virtual Machine (SVM) A single tape drive can be dedicated to a guest virtual machine for its sole use by CP ATTACH command or DEDICATE User Directory Statement A single tape drive can be serially shared by multiple guest virtual machines with the MULTIUSER option of the CP ATTACH command or DEDICATE User Directory Statement Specifically for guests that manage their own assignment of tape drives, such as z/os JES 2 Static Vary and Tape Auto-Switching 12

13 Supported Tape Units / Libraries 3480, 3490 Tape Subsystems 3590, 3592, TS11x0 Enterprise Tape Subsystems 3494, 3495 Automated Tape Libraries 3494 Virtual Tape Server (VTS) TS3500 (3584) Tape Library TS7700 Virtualization Engine z/vm Host support requires ESCON/FICON connection FCP connection supported for guest use E 3592 J1A TS1120 (3592-E05) Raw capacity 200 MB 800 MB 20.5 GB 300 GB 500 GB 4 TB TS1140 (3592 E07) Bandwidth 3 MB/s 4 MB/s 14 MB/s 40 MB/s 100 MB/s 250 MB/s 13

14 3592 Tape Encryption Hardware-based encryption provided for encryption-capable TS1120 (and later) tape drives z/vm support present in all supported releases If z/vm is managing encryption with drive, requires a key manager running on a separate machine (or z/os LPAR), connected to drives via TCP/IP Encryption information needs to be specified when writing a tape For details of z/vm support, see 14

15 DASD Primary device for z/vm System and Guest data Can be given to a guest operating system with CP ATTACH command or DEDICATE User Directory Statement Can be given to z/vm system itself with CP ATTACH command or at IPL time with System Configuration File statements SYSTEM_RESIDENCE CP_OWNED USER_VOLUME_LIST System-attached DASD provides: Checkpoint and Warmstart data Paging and Spooling data Guest minidisks (MDISK User Directory Statement) Guest temporary disks (CP DEFINE Txxxx command) 15

16 IBM System Storage Support Models supported IBM Enterprise Storage Server (ESS) 750 or 800 IBM System Storage DS6000 or DS8000 series IBM XIV, Storwize V7000, SAN Volume Controller (all FCP-only) Connections supported ESCON (excluding DS6000) FICON FCP ESCON/FICON Controller: 3990 Model 3 or 6, 1750 (DS6000), 2105 (ESS), 2107 (DS8000) Disks: 3390 Model 2, 3, 9, A FCP z/vm uses SCSI LUNs emualted as 9336 Model 20 16

17 Advanced Disk Functions FlashCopy Instant copy of source disk to one or more target disks Guest support via CCW Channel Programs Restricted to dedicated devices or fullpack (0-END) minidisks Native support with CP FLASHCOPY commands See Session ZVM18 for more information 17

18 Advanced Disk Functions Peer-to-Peer Remote Copy (PPRC) Continuous copy of source disk changes to target Guest support via CCW Channel Programs Restricted to dedicated devices and fullpack (0-END) minidisks Native support via ICKDSF running in a CMS Virtual Machine PPRC Hardware Metro Mirror (synchronous changes between source and target) Global Copy (asynchronous changes between source and target) Metro/Global Copy (3-volume PPRC link; Metro Mirror between source and intermediate, Global Copy between intermediate and target) Global Mirror (asynchronous changes between source and target; software managed consistency groups for failover to point-in-time copy during disaster) CP Query DASD DETAILS <rdev> command displays PPRC volume status when a link is active for the disk 18

19 Parallel Access Volumes (PAV) and HyperPAV Base volume shadowed by one or more Alias subchannels Looks like multiple separate, real DASD to host operating systems z/architecture allows only one active I/O to a single subchannel Alias subchannels overcome this restriction by allowing concurrent I/O to data mapped by Base volume, serialized by the Control Unit HyperPAV is a licensed feature of the DS8000 that removes static binding between Base and Alias subchannels found in traditional PAV Alias subchannels are grouped by LSS; any Alias can be associated with any Base subchannel within the pool for a single I/O operation For more details, see Session ZVM20 19

20 Minidisk Cache (MDC) Minidisk Cache is a host-based, full-track, write-through cache for partial and fullpack minidisks linked by guest virtual machines When one record of a track is read from disk, the entire track is brought into the cache Records are kept in cache based on last reference; unreferenced records are aged out of the cache Works well with XSTORE, but XSTORE is not explicitly required A Fair Share Insertion algorithm prevents one user from monopolizing the cache By default, MDC is active for all minidisks 20

21 Virtual Disk in Storage (VDISK) A VDISK is a fully-simulated FBA 9336 Model 20 DASD, where all data resides in main memory Great for applications that use temporary files (e.g., assembly, VSE lock file, sort applications), since data resides in volatile, not permanent, storage z/vm simulates all I/O commands, interrupts, and CCWs associated with the VDISK Any guest OS that supports FBA DASD can use VDISK Created by CP DEFINE VFB-512 command or the MDISK User Directory Statement VDISKS created in User Directory can be shared by multiple guests CP SET VDISK command or FEATURES VDISK System Configuration File Statement controls the amount of memory available for VDISKs 21

22 Guest Coupling z/vm Guest Coupling Support simulates the Coupling Facility hardware and software required to run a z/os Sysplex Environment within guest virtual machines Simulates advanced CF (Coupling Facility) and MF (Message Facility) hardware functions Provides a pre-production test platform for couple-system installation NOT intended for production, as the single point-of-failure at z/vm negates the intent of the z/os Parallel Sysplex Environment SSI does not address this, as it is designed for planned outages 32 User CF virtual machines can be coupled within a simulated Sysplex Each can be coupled with 8 CF Service Virtual Machines (SVM) Each CF SVM can connect to 7 Peer CF SVM 22

23 Guest Coupling Coupled Guest Coupled Guest Coupled Guest CFUSER CFUSER CFUSER CF Service Machine CF Service Machine CF Service(LIC) Machine (LIC) (LIC) CFVM CFVM CFVM Three components Service Machines Coupled Guests (User Machines) Simulated Message Facility Enabled with CFUSER and CFVM included on OPTION User Directory Statement Message Facility Simulation User Interface z/vm 23

24 Important Reference Manuals CP Commands and Utilities Reference CP Planning and Administration Important PAV, HyperPAV, SCSI, Tape Encryption information Configuration File Statements User Directory Statements All available at 24

25 Fin Eric Farman z/vm I/O Development