Misplaced Pages

#273726

33-711: VM 2000 is a hypervisor from Fujitsu (formerly Siemens Nixdorf Informationssysteme ) designed specifically for use with the BS2000 operating system. It is an EBCDIC -based operating system. It allows multiple images of BS2000 and Linux to operate on a S-series computer, which is based on the IBM System/390 architecture. It also supports BS2000, Linux and Microsoft Windows on x86-based SQ-series mainframes. Additionally, it can virtualize BS2000 guests on SR- and SX-series mainframes, based on MIPS and SPARC respectively. This operating-system -related article

66-662: A S/360-40 modified at the Cambridge Scientific Center to support dynamic address translation , a feature that enabled virtualization. Prior to this time, computer hardware had only been virtualized to the extent to allow multiple user applications to run concurrently, such as in CTSS and IBM M44/44X . With CP-40, the hardware's supervisor state was virtualized as well, allowing multiple operating systems to run concurrently in separate virtual machine contexts. Programmers soon implemented CP-40 (as CP-67 ) for

99-559: A hypervisor is a microkernel implementing virtualization infrastructure that must run in kernel-space for technical reasons, such as Intel VMX . Microkernels implementing virtualization mechanisms are also referred to as microhypervisor . Applying this terminology to Linux , KVM is a hypervisor and QEMU or Cloud Hypervisor are VMMs utilizing KVM as hypervisor. In his 1973 thesis, "Architectural Principles for Virtual Computer Systems," Robert P. Goldberg classified two types of hypervisor: The distinction between these two types

132-699: A further requirement for small memory-size and low overhead. Finally, in contrast to the ubiquity of the x86 architecture in the PC world, the embedded world uses a wider variety of architectures and less standardized environments. Support for virtualization requires memory protection (in the form of a memory management unit or at least a memory protection unit) and a distinction between user mode and privileged mode , which rules out most microcontrollers . This still leaves x86 , MIPS , ARM and PowerPC as widely deployed architectures on medium- to high-end embedded systems. As manufacturers of embedded systems usually have

165-413: A global view of scheduling and power management, and fine-grained control of information flows. The use of hypervisor technology by malware and rootkits installing themselves as a hypervisor below the operating system, known as hyperjacking , can make them more difficult to detect because the malware could intercept any operations of the operating system (such as someone entering a password) without

198-542: A series of disputed and bitter battles , time-sharing lost out to batch processing through IBM political infighting, and VM remained IBM's "other" mainframe operating system for decades, losing to MVS . It enjoyed a resurgence of popularity and support from 2000 as the z/VM product, for example as the platform for Linux on IBM Z . As mentioned above, the VM control program includes a hypervisor-call handler that intercepts DIAG ("Diagnose", opcode x'83') instructions used within

231-450: A single kernel, though the guest operating systems can differ in user space , such as different Linux distributions with the same kernel. The term hypervisor is a variant of supervisor , a traditional term for the kernel of an operating system : the hypervisor is the supervisor of the supervisors, with hyper- used as a stronger variant of super- . The term dates to circa 1970; IBM coined it for software that ran OS/360 and

264-463: A virtual machine. This provides fast-path non-virtualized execution of file-system access and other operations (DIAG is a model-dependent privileged instruction, not used in normal programming, and thus is not virtualized. It is therefore available for use as a signal to the "host" operating system). When first implemented in CP/CMS release 3.1, this use of DIAG provided an operating system interface that

297-434: Is a stub . You can help Misplaced Pages by expanding it . Hypervisor A hypervisor , also known as a virtual machine monitor ( VMM ) or virtualizer , is a type of computer software , firmware or hardware that creates and runs virtual machines . A computer on which a hypervisor runs one or more virtual machines is called a host machine , and each virtual machine is called a guest machine . The hypervisor presents

330-722: Is heavily discouraged, because Integrity VM implements its own memory management, scheduling and I/O policies that are tuned for virtual machines and are not as effective for normal applications. HPE also provides more rigid partitioning of their Integrity and HP9000 systems by way of VPAR and nPar technology, the former offering shared resource partitioning and the latter offering complete I/O and processing isolation. The flexibility of virtual server environment (VSE) has given way to its use more frequently in newer deployments. IBM provides virtualization partition technology known as logical partitioning (LPAR) on System/390 , zSeries , pSeries and IBM AS/400 systems. For IBM's Power Systems,

363-516: Is not always clear. For instance, KVM and bhyve are kernel modules that effectively convert the host operating system to a type-1 hypervisor. The first hypervisors providing full virtualization were the test tool SIMMON and the one-off IBM CP-40 research system, which began production use in January 1967 and became the first version of the IBM CP/CMS operating system. CP-40 ran on

SECTION 10

#1732801294274

396-540: The IBM System/360-67 , the first production computer system capable of full virtualization. IBM shipped this machine in 1966; it included page-translation-table hardware for virtual memory and other techniques that allowed a full virtualization of all kernel tasks, including I/O and interrupt handling. (Note that the "official" operating system, the ill-fated TSS/360 , did not employ full virtualization.) Both CP-40 and CP-67 began production use in 1967. CP/CMS

429-583: The POWER6 processor. LPAR and MSPP capacity allocations can be dynamically changed. Memory is allocated to each LPAR (at LPAR initiation or dynamically) and is address-controlled by the POWER Hypervisor. For real-mode addressing by operating systems ( AIX , Linux , IBM i ), the Power processors ( POWER4 onwards) have designed virtualization capabilities where a hardware address-offset is evaluated with

462-745: The 1960s-era IBM S/360 line. The 1972 announcement also included VM/370 , a reimplementation of CP/CMS for the S/370. Unlike CP/CMS , IBM provided support for this version (though it was still distributed in source code form for several releases). VM stands for Virtual Machine , emphasizing that all, not just some, of the hardware interfaces are virtualized. Both VM and CP/CMS enjoyed early acceptance and rapid development by universities, corporate users, and time-sharing vendors, as well as within IBM. Users played an active role in ongoing development, anticipating trends seen in modern open source projects. However, in

495-575: The 7090 emulator concurrently on the 360/65 and later used it for the DIAG handler of CP-67. In the earlier CP/CMS (1967) system, the term Control Program was used instead. Some literature, especially in microkernel contexts, makes a distinction between hypervisor and virtual machine monitor (VMM). There, both components form the overall virtualization stack of a certain system. Hypervisor refers to kernel-space functionality and VMM to user-space functionality. Specifically in these contexts,

528-541: The Integrity VM hypervisor layer that allows for many important features of HP-UX to be taken advantage of and provides major differentiation between this platform and other commodity platforms - such as processor hotswap, memory hotswap, and dynamic kernel updates without system reboot. While it heavily leverages HP-UX, the Integrity VM hypervisor is really a hybrid that runs on bare-metal while guests are executing. Running normal HP-UX applications on an Integrity VM host

561-466: The KVM interface including kvmtool, crosvm and Firecracker and numerous specialised VMMs build with frameworks such as rust-vmm. Internally, KVM uses SeaBIOS as an open source implementation of a 16-bit x86 BIOS . KVM has had support for hot swappable vCPUs , dynamic memory management, and Live Migration since February 2007. It also reduces the impact that memory write-intensive workloads have on

594-905: The OS address-offset to arrive at the physical memory address. Input/Output (I/O) adapters can be exclusively "owned" by LPARs or shared by LPARs through an appliance partition known as the Virtual I/O Server (VIOS). The Power Hypervisor provides for high levels of reliability, availability and serviceability (RAS) by facilitating hot add/replace of many parts (model dependent: processors, memory, I/O adapters, blowers, power units, disks, system controllers, etc.) Similar trends have occurred with x86/x86-64 server platforms, where open-source projects such as Xen have led virtualization efforts. These include hypervisors built on Linux and Solaris kernels as well as custom kernels. Since these technologies span from large systems down to desktops, they are described in

627-483: The POWER Hypervisor (PHYP) is a native (bare-metal) hypervisor in firmware and provides isolation between LPARs. Processor capacity is provided to LPARs in either a dedicated fashion or on an entitlement basis where unused capacity is harvested and can be re-allocated to busy workloads. Groups of LPARs can have their processor capacity managed as if they were in a "pool" - IBM refers to this capability as Multiple Shared-Processor Pools (MSPPs) and implements it in servers with

660-589: The VirtIO API . This includes a paravirtual Ethernet card , disk I/O controller, balloon driver , and a VGA graphics interface using SPICE or VMware drivers. Avi Kivity began the development of KVM in mid-2006 at Qumranet , a technology startup company that was acquired by Red Hat in 2008. KVM surfaced in October 2006 and was merged into the Linux kernel mainline in kernel version 2.6.20, which

693-533: The anti-malware software necessarily detecting it (since the malware runs below the entire operating system). Implementation of the concept has allegedly occurred in the SubVirt laboratory rootkit (developed jointly by Microsoft and University of Michigan researchers ) as well as in the Blue Pill malware package. However, such assertions have been disputed by others who claim that it would be possible to detect

SECTION 20

#1732801294274

726-529: The guest operating systems with a virtual operating platform and manages the execution of the guest operating systems. Unlike an emulator , the guest executes most instructions on the native hardware. Multiple instances of a variety of operating systems may share the virtualized hardware resources: for example, Linux , Windows , and macOS instances can all run on a single physical x86 machine. This contrasts with operating-system–level virtualization , where all instances (usually called containers ) must share

759-818: The hypervisor (and can all run simultaneously on the same processor, as fully virtualized independent guest OSes). Wind River "Carrier Grade Linux" also runs on Sun's Hypervisor. Full virtualization on SPARC processors proved straightforward: since its inception in the mid-1980s Sun deliberately kept the SPARC architecture clean of artifacts that would have impeded virtualization. (Compare with virtualization on x86 processors below.) HPE provides HP Integrity Virtual Machines (Integrity VM) to host multiple operating systems on their Itanium powered Integrity systems. Itanium can run HP-UX , Linux, Windows and OpenVMS , and these environments are also supported as virtual servers on HP's Integrity VM platform. The HP-UX operating system hosts

792-818: The hypervisor simulates. This is called paravirtualization in Xen , a "hypercall" in Parallels Workstation , and a "DIAGNOSE code" in IBM VM . Some microkernels, such as Mach and L4 , are flexible enough to allow paravirtualization of guest operating systems. Embedded hypervisors , targeting embedded systems and certain real-time operating system (RTOS) environments, are designed with different requirements when compared to desktop and enterprise systems, including robustness, security and real-time capabilities. The resource-constrained nature of many embedded systems, especially battery-powered mobile systems, imposes

825-474: The multimillion-dollar range at the high end), although virtualization has also been available on some low- and mid-range systems, such as IBM pSeries servers, HP Superdome series machines, and Sun / Oracle T-series CoolThreads servers. Although Solaris has always been the only guest domain OS officially supported by Sun/Oracle on their Logical Domains hypervisor, as of late 2006 , Linux (Ubuntu and Gentoo), and FreeBSD have been ported to run on top of

858-509: The next section. X86 virtualization was introduced in the 1990s, with its emulation being included in Bochs . Intel and AMD released their first x86 processors with hardware virtualisation in 2005 with Intel VT-x (code-named Vanderpool) and AMD-V (code-named Pacifica). An alternative approach requires modifying the guest operating system to make a system call to the underlying hypervisor, rather than executing machine I/O instructions that

891-434: The presence of a hypervisor-based rootkit. In 2009, researchers from Microsoft and North Carolina State University demonstrated a hypervisor-layer anti-rootkit called Hooksafe that can provide generic protection against kernel-mode rootkits . Kernel-based Virtual Machine KVM was originally designed for x86 processors but has since been ported to ESA/390 , PowerPC , IA-64 , and ARM . The IA-64 port

924-662: The source code to their operating systems, they have less need for full virtualization in this space. Instead, the performance advantages of paravirtualization make this usually the virtualization technology of choice. Nevertheless, ARM and MIPS have recently added full virtualization support as an IP option and has included it in their latest high-end processors and architecture versions, such as ARM Cortex-A15 MPCore and ARMv8 EL2. Other differences between virtualization in server/desktop and embedded environments include requirements for efficient sharing of resources across virtual machines, high-bandwidth, low-latency inter-VM communication,

957-489: The stable main production system, and without requiring costly additional development systems. IBM announced its System/370 series in 1970 without the virtual memory feature needed for virtualization, but added it in the August 1972 Advanced Function announcement. Virtualization has been featured in all successor systems, such that all modern-day IBM mainframes, including the zSeries line, retain backward compatibility with

990-716: Was analogous to the System/360 Supervisor Call instruction (SVC), but that did not require altering or extending the system's virtualization of SVC. In 1985 IBM introduced the PR/SM hypervisor to manage logical partitions (LPAR). Several factors led to a resurgence around 2005 in the use of virtualization technology among Unix , Linux , and other Unix-like operating systems: Major Unix vendors, including HP , IBM , SGI , and Sun Microsystems , have been selling virtualized hardware since before 2000. These have generally been large, expensive systems (in

1023-577: Was available to IBM customers from 1968 to early 1970s, in source code form without support. CP/CMS formed part of IBM's attempt to build robust time-sharing systems for its mainframe computers. By running multiple operating systems concurrently, the hypervisor increased system robustness and stability: Even if one operating system crashed, the others would continue working without interruption. Indeed, this even allowed beta or experimental versions of operating systems‍—‌or even of new hardware ‍—‌to be deployed and debugged, without jeopardizing

VM2000 - Misplaced Pages Continue

1056-486: Was released on 5 February 2007. KVM is maintained by Paolo Bonzini. KVM provides device abstraction but no processor emulation. It exposes the /dev/kvm interface, which a user mode host can then use to: Originally, a forked version of QEMU was provided to launch guests and deal with hardware emulation that is not handled by the kernel. That support was eventually merged into the upstream project. There are now numerous Virtual Machine Monitors (VMMs) which can utilise

1089-598: Was removed in 2014. KVM supports hardware-assisted virtualization for a wide variety of guest operating systems including BSD , Solaris , Windows , Haiku , ReactOS , Plan 9 , AROS , macOS , and even other Linux systems. In addition, Android 2.2, GNU/Hurd ( Debian K16), Minix 3.1.2a, Solaris 10 U3 and Darwin 8.0.1, together with other operating systems and some newer versions of these listed, are known to work with certain limitations. Additionally, KVM provides paravirtualization support for Linux, OpenBSD , FreeBSD, NetBSD , Plan 9 and Windows guests using

#273726