VM (operating system)

From Wikipedia, the free encyclopedia

See also: CP/CMS and History of CP/CMS

VM (often: VM/CMS) refers to a family of IBM virtual machine operating systems used on IBM System/370, System/390, zSeries, and System z9 IBM mainframes and compatible systems. (VM also runs under Hercules, a S/370, S/390, and zSeries emulator.) The first version was VM/370 (officially: Virtual Machine Facility/370). This was a System/370 reimplementation of IBM's CP/CMS from the IBM System/360-67. Later major VM versions include VM/ESA and the current z/VM. Other versions have included VM/SEPP, VM/BSEPP, VM/SP, VM/HPO, VMXA/SF, and VMXA/SP.

VM is quite different from other IBM mainframe operating systems, which include:

• The OS family (OS/360, OS/VS1, OS/VS2, MVS, OS/390, and the current z/OS)
• The DOS family (DOS/360, DOS/VSE, and the current z/VSE)
• Specialized systems, like TPF and the current z/TPF
• Systems originating outside IBM, like Linux on zSeries, MTS, and MUSIC/SP

VM's differences are primarily due to the unique circumstances in which CP/CMS was built and distributed. For an historical perspective on the development of VM, see History of CP/CMS.

Contents 1 Overview 2 Hypervisor interface 3 History 4 VM trivia 5 References 6 Family tree

[edit] Overview

The heart of the VM architecture is a control program or hypervisor called VM-CP (usually: CP; sometimes, ambiguously: VM). It runs on the physical hardware, and creates the virtual machine environment. VM-CP provides full virtualization of the physical machine – including all I/O and other privileged operations. It performs the system's resource-sharing, including device management, dispatching, virtual storage management, and other traditional operating system tasks. Each VM user is provided with a separate virtual machine having its own address space, virtual devices, etc., and which is capable of running any software that could be run on a stand-alone machine. A given VM mainframe typically runs hundreds or thousands of virtual machine instances. VM-CP began life as CP-370, a reimplementation of CP-67, itself a reimplementation of CP-40.

Running within each virtual machine is another, "guest" operating system. This might be:

• CMS ("Conversational Monitor System", renamed from the "Cambridge Monitor System" of CP/CMS). Its official name is VM-CMS (confusing, since VM is commonly called VM/CMS). Most virtual machines run CMS, a lightweight, single-user operating system. Its interactive environment is comparable to that of a single-user PC, including a file system, programming services, device access, and command-line processing. (While an earlier version of CMS was uncharitably described as "CP/M on a mainframe", the comparison is an anachronism; the author of CP/M, Gary Kildall, was an experienced CMS user.)

• A "normal" operating system. IBM's mainstream batch-oriented operating systems (i.e. the OS or DOS families) can be loaded and run without modification.

• Another copy of VM. A "second level" instance of VM can be fully-virtualized inside a virtual machine. This is how VM development and testing is done. (A "second-level" VM can potentially implement a different virtualization of the hardware. This technique was used to develop S/370 software before S/370 hardware was available, and it has continued to play a role in new hardware development at IBM. The literature cites practical examples of virtualization five levels deep.)

• A copy of AIX or Linux. In the mainframe environment, these operating systems often run under VM. (They can also run as 'native' operating systems on the bare hardware.)

• A specialized VM subsystem. Several non-CMS systems run within VM-CP virtual machines, providing services to CMS users such as spooling, interprocess communications, and specialized device support. They operate "behind the scenes", extending the services available to CMS without adding to the VM-CP control program. By running in separate virtual machines, they receive the same security and reliability protections as other VM users. Examples include:
  • RSCS ("Remote Spooling and Communication Subsystem") – communication and information transfer facilities between virtual machines^[1]
  • RACF ("Resource Access Control Facility") – a security system [edited by Anand V Shah]
  • VNET – a virtual network interface

[edit] Hypervisor interface

At one time, CMS was capable of running on a bare machine, as a true operating system (though of course nobody would do this). It now only runs as a guest OS under VM. This is because CMS relies on a hypervisor interface to VM-CP, to perform file system operations and request other VM services. This paravirtualization interface:

• Provides a fast path to VM-CP, to avoid the overhead of full simulation.
• Was first developed as a performance improvement for CP/CMS release 2.1, an important early milestone in CP's efficiency.
• Uses a non-virtualized, model-dependent machine instruction as a signal between CMS and CP: DIAG ("diagnose").

Note that the term "hypervisor" was probably coined during IBM's implementation of VM/370, when it was used to refer to the virtual DIAG handler.

[edit] History

The early history of VM is described in the articles CP/CMS and History of CP/CMS. VM/370 was a reimplementation of CP/CMS, made available in 1972 as part of IBM's "System/370 Advanced Function" announcement (which added virtual memory hardware and operating systems to the System/370 series). Early releases of VM continued in open source, and today are considered to be in the public domain. This policy ended in the mid 80s, when VM became a "For-charge Licensed System Product".

VM remained an important platform within IBM, used for operating system development and time-sharing use; but for customers it remained IBM's "other operating system". The OS and DOS families remained IBM's strategic products, and customers were not encouraged to run VM. Those that did formed close working relationships, continuing the community-support model of early CP/CMS users. In the meantime, the system struggled with political infighting within IBM over what resources should be available to the project, as compared with other IBM efforts. A basic "problem" with the system was seen at IBM's field sales level: VM/CMS demonstrably reduced the amount of hardware needed to support a given number of time-sharing users. IBM was, after all, in the business of selling computer systems.

Varian provides this fascinating quote, illustrating VM's unexpected success:

The marketing forecasts for VM/370 predicted that no more than one 168 would ever run VM during the entire life of the product. In fact, the first 168 delivered to a customer ran only CP and CMS. Ten years later, ten percent of the large processors being shipped from Poughkeepsie would be destined to run VM, as would a very substantial portion of the mid-range machines that were built in Endicott. Before fifteen years had passed, there would be more VM licenses than MVS licenses.^[2]

VM's role changed within IBM when hardware evolution led to significant changes in processor architecture. Backward compatibility remained a cornerstone of the IBM mainframe family, which still used the basic instruction set introduced with the original System/360; but the need for efficient use of the 64-bit zSeries made the VM approach much more attractive. VM was also useful when running mainframe AIX and Linux, platforms that were to become increasingly important. The current z/VM platform has finally achieved the recognition within IBM that VM users long felt it deserved. Some z/VM sites run thousands of simultaneous virtual machine users on a single system.

IBM and third parties have offered many applications and tools that run under VM. Examples include RAMIS, FOCUS, SPSS, NOMAD, DB2, REXX, RACF, and OfficeVision. Current VM offerings run the gamut of mainframe applications, including HTTP servers, database managers, analysis tools, engineering packages, and financial systems.

[edit] VM trivia

• VM teddy bear: In the early 80s, the VM group within SHARE (the IBM user group) sought a mascot or logo for the community to adopt. This was in part a response to IBM's MVS users selecting the turkey as a mascot (hilariously chosen, according to legend, by the MVS Performance Group in the early days of MVS, when its performance was...a sore topic). In 1983, the teddy bear became VM's de facto mascot at SHARE 60, when teddy bear stickers were attached to the nametags of "cuddlier oldtimers" to flag them for newcomers as "friendly if approached." The bears were a hit and soon appeared widely. Bears were awarded to inductees of the "Order of the Knights of VM," individuals who made "useful contributions" to the community.^[3][4] See the references section for links to bear images.^[5]

[edit] References

VM sources (also see CP/CMS sources below)

• Bob DuCharme, Operating Systems Handbook, Part 5: VM/CMS (available online at www.snee.com)
  – a fairly detailed user's guide to VM/CMS

• E. C. Hendricks and T. C. Hartmann, "Evolution of a Virtual Machine Subsystem", IBM Systems Journal Vol. 18, pp. 111-142 (1979)
  – RSCS design and implementation

• IBM Corporation, IBM Virtual Machine Facility/370 Introduction, GC20-1800, (1972)
  – the original manual

External VM links

• www-03.ibm.com – IBM: z/VM manuals

Citations

1. ^ Creasy, op. cit., p. 483 – role of RSCS
2. ^ Varian, op. cit., p. 30 – extent of VM use; more VM licenses than MVS licenses
3. ^ Varian, op. cit., p. 2 – the teddy bear story
4. ^ ppewww.ph.gla.ac.uk – another version of the bear origin story, by physicist Alan Flavell, with an image
5. ^ www.vm.ibm.com – VM bear images on an IBM site, contributed by VM developer Pam Christina

Primary CP/CMS sources

• R. J. Creasy, "The origin of the VM/370 time-sharing system", IBM Journal of Research & Development, Vol. 25, No. 5 (September 1981), pp. 483-490, available on-line at research.ibm.com
  – perspective on CP/CMS and VM history by the CP-40 project lead, also a CTSS author

• E.W. Pugh, L.R. Johnson, and John H. Palmer, IBM's 360 and early 370 systems, MIT Press, Cambridge MA and London, ISBN 0-262-16123-0
  – extensive (819 pp.) treatment of IBM's offerings during this period; the limited coverage of CP/CMS in such a definitive work is telling

• Melinda Varian, VM and the VM community, past present, and future, SHARE 89 Sessions 9059-9061, 1977; available online at www.princeton.edu/~melinda
  – and outstanding source for CP/CMS and VM history

Additional CP/CMS sources

Background CP/CMS sources

Additional on-line CP/CMS resources

• febcm.club.fr – Information Technology Timeline, 1964-1974
• www.multicians.org – Tom Van Vleek's short essay The IBM 360/67 and CP/CMS
• www.cap-lore.com – Norman Hardy's Short history of IBM's virtual machines]
• www.cap-lore.com – Norman Hardy's short description of the "Blaauw Box"

[edit] Family tree

CP/CMS family relationships:    → derivation    >> strong influence    > some influence/precedence
CTSS
	> IBM M44/44X
	>> CP-40/CMS → CP[-67]/CMS	→ VM/370 → VM/XA versions → VM/ESA → z/VM
		→ VP/CSS
	> TSS/360
	> OS/MVT-TSO → OS/VS2-TSO → MVS-TSO → z/OS-TSO
	>> MULTICS and most other time-sharing platforms

This simplified framework provides links to major time-sharing systems that influenced or were influenced by CP/CMS. Many other important systems emerged during this period; cf. Manchester/Ferranti Atlas, Burroughs, Control Data Corporation, DEC, and Honeywell for examples. Also see time-sharing system evolution.