Jump to: navigation, search

Difference between revisions of "Obsolete:Nova-zVM"

Line 6: Line 6:
 
[http://www-03.ibm.com/systems/z/ System z] is a family name used by IBM for all of its mainframe computers. IBM System z, now includes the IBM System z9, the IBM System z10 and the newer IBM zEnterprise.
 
[http://www-03.ibm.com/systems/z/ System z] is a family name used by IBM for all of its mainframe computers. IBM System z, now includes the IBM System z9, the IBM System z10 and the newer IBM zEnterprise.
  
[http://www.vm.ibm.com/ z/VM] is an IBM VM hypervisor based on 64-bit z/Architecture, and now with multi-system virtualization and virtual server mobility. z/VM virtualization technology is designed to allow the capability for clients to run hundreds to thousands of Linux servers on a single mainframe running with other System z operating systems, such as z/OS, or as a large-scale inux-only enterprise server solution.  
+
[http://www.vm.ibm.com/ z/VM] is an IBM VM hypervisor based on 64-bit z/Architecture, and now with multi-system virtualization and virtual server mobility. z/VM is designed to allow the capability for clients to run hundreds to thousands of Linux servers on a single mainframe running with other System z operating systems, such as z/OS, or as a large-scale linux-only enterprise server solution.  
  
System z, as with all computing systems, is built on hardware components. Most
+
[http://sourceforge.net/apps/mediawiki/xcat/index.php?title=Main_Page xCAT] can be used to manage virtual servers spanning across multiple z/VM partitions. The xCAT management node (MN) runs on any Linux virtual server. It manages each z/VM partition using a System z hardware control point (zHCP) running on a privileged Linux virtual server. The zHCP interfaces with z/VM systems management API (SMAPI), directory manager (DirMaint), and control program layer (CP) to manage the z/VM partition. It utilizes a C socket interface to communicate with the SMAPI layer and VMCP Linux module to communicate with the CP layer.  
of those components were introduced early in the mainframe era, and were
 
developed over the years. As a user of z/VM, you will often need to interact with
 
the hardware or speak in terms of the terminology prevalent in the mainframe
 
world.
 
 
 
[http://www.vm.ibm.com/ z/VM] is a VM hypervisor based on 64-bit z/Architecture, and now with multi-system virtualization and virtual server mobilit. z/VM provides a wide range of networking and connectivity options and adheres to many of the industry. For z/VM network concepts and references, please refer to http://www.vm.ibm.com/networking/
 
  
 
= Architecture =
 
= Architecture =

Revision as of 06:35, 8 June 2013

Overview

Code Links

System z and z/VM

System z is a family name used by IBM for all of its mainframe computers. IBM System z, now includes the IBM System z9, the IBM System z10 and the newer IBM zEnterprise.

z/VM is an IBM VM hypervisor based on 64-bit z/Architecture, and now with multi-system virtualization and virtual server mobility. z/VM is designed to allow the capability for clients to run hundreds to thousands of Linux servers on a single mainframe running with other System z operating systems, such as z/OS, or as a large-scale linux-only enterprise server solution.

xCAT can be used to manage virtual servers spanning across multiple z/VM partitions. The xCAT management node (MN) runs on any Linux virtual server. It manages each z/VM partition using a System z hardware control point (zHCP) running on a privileged Linux virtual server. The zHCP interfaces with z/VM systems management API (SMAPI), directory manager (DirMaint), and control program layer (CP) to manage the z/VM partition. It utilizes a C socket interface to communicate with the SMAPI layer and VMCP Linux module to communicate with the CP layer.

Architecture

Prerequisites

Configure Examples

Code Structure

References

  1. z/VM
  2. xCAT on z/VM