DOCSLIB.ORG

HVX: Virtualizing the Cloud

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
HVX: Virtualizing the Cloud HVX: Virtualizing the Cloud Alex Fishman, Mike Rapoport, Evgeny Budilovsky, Izik Eidus Ravello Systems Abstract execution of unmodified operating systems. Guest de- privileging is performed using trap-and-simulate tech- Nowadays there is significant diversity in Infrastructure nique ([8]). Full virtualization hypervisors for x86 ar- as a Service (IaaS) clouds. The differences span from chitecture require hardware assistance available in recent virtualization technology and hypervisors, through stor- AMD and Intel processors ([2, 10]). By contrast, in the age and network configuration, to the cloud management para-virtualized environment, the guest operating system APIs. These differences make migration of a VM (or is aware that it is executed on a VM and it should contain a set of VMs) from a private cloud into a public cloud, modifications necessary to interface with the underlying or between different public clouds, complicated or even hypervisor instead of performing privileged operations impractical for many use-cases. ([1]). HVX is a virtualization platform that enables complete Virtual hardware devices. Different hypervisors ex- abstraction of underlying cloud infrastructure from the pose different sets of virtual hardware devices such as application virtual machines. HVX allows deployment CPU, chipset, network and storage controllers. Migrat- of existing VMs into the cloud without any modifica- ing a VM from one hypervisor to another resembles tions, mobility between the clouds and easy duplication transfer of a hard disk between different computers. of the entire deployment. Image formats. Each hypervisor supports its own HVX can be deployed on almost any existing IaaS proprietary image format, for example, VMware’s cloud. Each instance of the HVX deployment packs in VMDK, or KVM qcow and qcow2. a nested hypervisor, virtual hardware, network and stor- The situation in the IaaS world is even more com- age configuration. plex. Different cloud providers utilize different hyper- Combined with image store and management APIs, visors. For instance, the leading cloud operator Amazon the HVX can be used for the creation of a virtual cloud EC2 is based on Xen hypervisor, the HP cloud is built on that utilizes existing cloud provider infrastructure as the top of KVM, while the leading private cloud platform is hardware rather than using physical servers, switches and VMware ESX ([4, 9, 11, 20, 23]). In addition, IaaS cloud storage. providers offer incompatible APIs for VM provisioning, configuration and monitoring. Network and storage con- 1 Introduction figuration is different as well and varies from operator to operator. There are many virtualization solutions available today: Such levels of complexity pose significant challenges VMware ESX, KVM, Xen, just to name a few. These for the development and deployment of enterprise appli- solutions lack interoperability with each other, meaning cations in a public cloud. that a VM running on one hypervisor cannot be easily Migration of an existing application to the public migrated to another hypervisor. cloud requires provisioning and reconfiguration of VMs The existing virtualization solutions differ in several for virtualization technology used in cloud, adaptation aspects: for different storage infrastructure, and customization of Virtualization technique. There are two major ap- the networking stack. Development of new applications proaches to virtualization: full virtualization and para- requires analysis of existing cloud architecture, selection virtualization. The full virtualization hypervisors present of the appropriate public cloud, and creation of manage- their guest a complete virtual system and therefore allow ment software tailored for that particular cloud. There are efforts to resolve those issues. For instance, Cloud VM Xen-Blanket ([22]) uses nested virtualization to run ap- Unmodified plication VMs allowing thus to cope with virtualization application VM technology differences between IaaS providers - but it Guest VM hardware can only run PV guests. Another nested virtualization solution, the Turtles Project ([5]) provides an ability to Network Storage run unmodified guests, however it requires modifications HVX Hypervisor of the cloud provider infrastructure. Linux Most current commercial and open-source attempts to Cloud VM hardware ease the pains of cloud migration, interoperability and duplication are trying to meet these challenges by ap- Figure 1: HVX Architecture plying management only solutions. Typically, they re- build the VMs from scratch for each copy of the appli- cation, thus creating different VMs for each copy and agement and the networking stack significantly simpli- each cloud provider. These VMs are usually created ei- fies overall system design and implementation. ther using manually written scripts, or using a configura- HVX comprises three major components: nested hy- tion management tool ([6, 15]). The main disadvantages pervisor, virtual networking layer and cloud storage ab- of these solutions are that they require in-depth knowl- straction layer. HVX hypervisor provides its own set of edge regarding the application (meaning one cannot just virtual hardware, independent of the hardware supplied use unmodified VM images), and eventually the result- by the cloud operator. This enables complete isolation of ing VMs differ from the original ones, rendering these cloud specific virtualization technology and I/O configu- solutions problematic for many use-cases. ration details from the application VMs. The support for We propose a novel solution to these problems by in- the wide range of virtual storage and network devices al- troducing HVX - a thin virtualization layer running on lows reuse of existing VM images without the necessity top of the already virtualized hardware, providing unified of installing additional drivers and tools. The network- hardware, network and storage configuration to a guest ing layer provides an ability to define complex network VM and capable of running on top of most existing vir- topologies by creating an overlay virtual network on top tual machine monitors (VMM), including both full and of the cloud provider’s physical network. para-virtualized environments. The HVX layer supports Figure 1 illustrates HVX running inside a cloud virtual most of the existing image formats and contains imple- machine and executing an unmodified application VM. mentation of ESX, KVM and XEN VMMs virtual hard- ware thus allowing to run any existing VM without any modification on top of any cloud. For example, an un- 3 The Hypervisor modified guest VM with para-virtualized ESX devices can be run in EC2 cloud on top of a para-virtualized Xen 3.1 CPU Virtualization host. Moreover, the VM images can be exported back to The heart of HVX technology is the hypervisor. The hy- the original hypervisor format facilitating migration be- pervisor is responsible for execution of the application tween public and private clouds. HVX also contains a VM in a nested virtual environment. The HVX hyper- network abstraction layer that provides an overlay net- visor cannot rely on hardware virtualization extensions work to guest VMs making it possible, for example, to such as Intel VT ([19]) or AMD SVM ([3]) because it run several VMs in different public clouds that commu- already runs inside a virtual machine. On the other hand, nicate on the same network subnet as if they were physi- the nested virtualization support in hardware is not yet cally connected to the same L2 switch. mainstream and there is no guarantee that it will be avail- HVX management system provides convenient and able in public clouds in the near future. Hence, the HVX easy to use interface for creating, configuring and man- hypervisor implements full virtualization using binary aging the entire multi-VM deployment including appli- translation ([18]). cation virtual machines, storage and the logical network. The HVX hypervisor binary translation and simula- tion engine emulates the x86 processor ISA. It compiles 2 The HVX Architecture the original guest ring-0 machine code into another ma- chine code sequence that can be executed without alter- HVX is a thin virtualization layer running on Linux. ing privileged state of the physical CPU. HVX hypervi- Linux was chosen because of its support for para- sor fetches a basic block of the guest machine code and virtualization and the availability of device drivers for all replaces privileged instructions with a simulation code VMMs. Utilization of Linux scheduler, memory man- that operates on the emulated software CPU state rather than on the physical CPU. The original basic block exit Overlay network point is replaced with jump to HVX to return control to the hypervisor after execution of the translated basic block. The HVX repeats the algorithm again and again until the application VM is terminated. Guest 1 Guest 2 Guest 3 Guest 4 Guest 5 One of the most difficult challenges for nested virtu- 10.0.0.1 10.0.0.2 10.0.0.3 10.0.0.4 10.0.0.5 alization is achieving a high performance level. HVX utilizes many advanced techniques to accomplish this, HVX HVX HVX including basic block chaining, caching and reusing of 50.16.178.19 23.22.39.65 173.203.197.94 translated code, fast shadow MMU and APIC implemen- tation, direct execution of user space code (Ring 3), im- plementation of para-virtualized devices for network and Cloud provider Cloud provider network network IO, fast context switching between guest VM and the host kernel, and the use of Linux for guest VM schedul-
Load more

Recommended publications
  • Understanding Full Virtualization, Paravirtualization, and Hardware Assist
    VMware Understanding Full Virtualization, Paravirtualization, and Hardware Assist Contents Introduction .................................................................................................................1 Overview of x86 Virtualization..................................................................................2 CPU Virtualization .......................................................................................................3 The Challenges of x86 Hardware Virtualization ...........................................................................................................3 Technique 1 - Full Virtualization using Binary Translation......................................................................................4 Technique 2 - OS Assisted Virtualization or Paravirtualization.............................................................................5 Technique 3 - Hardware Assisted Virtualization ..........................................................................................................6 Memory Virtualization................................................................................................6 Device and I/O Virtualization.....................................................................................7 Summarizing the Current State of x86 Virtualization Techniques......................8 Full Virtualization with Binary Translation is the Most Established Technology Today..........................8 Hardware Assist is the Future of Virtualization, but the Real Gains Have
    [Show full text]
  • Paravirtualization (PV)
    Full and Para Virtualization Dr. Sanjay P. Ahuja, Ph.D. Fidelity National Financial Distinguished Professor of CIS School of Computing, UNF x86 Hardware Virtualization The x86 architecture offers four levels of privilege known as Ring 0, 1, 2 and 3 to operating systems and applications to manage access to the computer hardware. While user level applications typically run in Ring 3, the operating system needs to have direct access to the memory and hardware and must execute its privileged instructions in Ring 0. x86 privilege level architecture without virtualization Technique 1: Full Virtualization using Binary Translation This approach relies on binary translation to trap (into the VMM) and to virtualize certain sensitive and non-virtualizable instructions with new sequences of instructions that have the intended effect on the virtual hardware. Meanwhile, user level code is directly executed on the processor for high performance virtualization. Binary translation approach to x86 virtualization Full Virtualization using Binary Translation This combination of binary translation and direct execution provides Full Virtualization as the guest OS is completely decoupled from the underlying hardware by the virtualization layer. The guest OS is not aware it is being virtualized and requires no modification. The hypervisor translates all operating system instructions at run-time on the fly and caches the results for future use, while user level instructions run unmodified at native speed. VMware’s virtualization products such as VMWare ESXi and Microsoft Virtual Server are examples of full virtualization. Full Virtualization using Binary Translation The performance of full virtualization may not be ideal because it involves binary translation at run-time which is time consuming and can incur a large performance overhead.
    [Show full text]
  • Full Virtualization on Low-End Hardware: a Case Study
    Full Virtualization on Low-End Hardware: a Case Study Adriano Carvalho∗, Vitor Silva∗, Francisco Afonsoy, Paulo Cardoso∗, Jorge Cabral∗, Mongkol Ekpanyapongz, Sergio Montenegrox and Adriano Tavares∗ ∗Embedded Systems Research Group Universidade do Minho, 4800–058 Guimaraes˜ — Portugal yInstituto Politecnico´ de Coimbra (ESTGOH), 3400–124 Oliveira do Hospital — Portugal zAsian Institute of Technology, Pathumthani 12120 — Thailand xUniversitat¨ Wurzburg,¨ 97074 Wurzburg¨ — Germany Abstract—Most hypervisors today rely either on (1) full virtua- a hypervisor-specific, often proprietary, interface. Full virtua- lization on high-end hardware (i.e., hardware with virtualization lization on low-end hardware, on the other end, has none of extensions), (2) paravirtualization, or (3) both. These, however, those disadvantages. do not fulfill embedded systems’ requirements, or require legacy software to be modified. Full virtualization on low-end hardware Full virtualization on low-end hardware (i.e., hardware with- (i.e., hardware without virtualization extensions), on the other out dedicated support for virtualization) must be accomplished end, has none of those disadvantages. However, it is often using mechanisms which were not originally designed for it. claimed that it is not feasible due to an unacceptably high Therefore, full virtualization on low-end hardware is not al- virtualization overhead. We were, nevertheless, unable to find ways possible because the hardware may not fulfill the neces- real-world quantitative results supporting those claims. In this paper, performance and footprint measurements from a sary requirements (i.e., “the set of sensitive instructions for that case study on low-end hardware full virtualization for embedded computer is a subset of the set of privileged instructions” [1]).
    [Show full text]
  • Taxonomy of Virtualization Technologies Master’S Thesis
    A taxonomy of virtualization technologies Master’s thesis Delft University of Technology Faculty of Systems Engineering Policy Analysis & Management August, 2010 Paulus Kampert 1175998 Taxonomy of virtualization technologies Preface This thesis has been written as part of the Master Thesis Project (spm5910). This is the final course from the master programme Systems Engineering, Policy Analysis & Management (SEPAM), educated by Delft University of Technology at the Faculty of Technology, Policy and Management. This thesis is the product of six months of intensive work in order to obtain the Master degree. This research project provides an overview of the different types of virtualization technologies and virtualization trends. A taxonomy model has been developed that demonstrates the various layers of a virtual server architecture and virtualization domains in a structured way. Special thanks go to my supervisors. My effort would be useless without the priceless support from them. First, I would like to thank my professor Jan van Berg for his advice, support, time and effort for pushing me in the right direction. I am truly grateful. I would also like to thank my first supervisor Sietse Overbeek for frequently directing and commenting on my research. His advice and feedback was very constructive. Many thanks go to my external supervisor Joris Haverkort for his tremendous support and efforts. He made me feel right at home at Atos Origin and helped me a lot through the course of this research project. Especially, the lectures on virtualization technologies and his positive feedback gave me a better understanding of virtualization. Also, thanks go to Jeroen Klompenhouwer (operations manager at Atos Origin), who introduced me to Joris Haverkort and gave me the opportunity to do my graduation project at Atos Origin.
    [Show full text]
  • Virtualization Basics: Understanding Techniques and Fundamentals
    Virtualization Basics: Understanding Techniques and Fundamentals Hyungro Lee School of Informatics and Computing, Indiana University 815 E 10th St. Bloomington, IN 47408 [email protected] ABSTRACT example of growing involvement in virtualization technolo- Virtualization is a fundamental part of cloud computing, gies with the cloud. Early technologies and developments especially in delivering Infrastructure as a Service (IaaS). in the virtualization have been accomplished by some com- Exploring different techniques and architectures of the vir- panies such as IBM from 1967 and VMware from 1998. In tualization helps us understand the basic knowledge of virtu- open source communities, Xen, KVM, Linux-vServer, LXC alization and the server consolidation in the cloud with x86 and others have supported virtualization in different plat- architecture. This paper describes virtualization technolo- forms with different approaches. In this paper, x86 archi- gies, architectures and optimizations regarding the sharing tecture virtualization will be discussed with these historical CPU, memory and I/O devices on x86 virtual machine mon- changes. itor. In cloud computing, Infrastructure-as-a-Service (IaaS) pro- vides on-demand virtual machine instances with virtualiza- Categories and Subject Descriptors tion technologies. IaaS has been broadly used to provide re- C.0 [General]: Hardware/software interface; C.4 [Performance quired compute resources in shared resource environments. of systems]: Performance attributes; D.4.7 [Operating Amazon Web Services (AWS), Google Compute Engine, Mi- Systems]: Organization and design crosoft Windows Azure, and HP Cloud offer commercial cloud services. OpenStack, Eucalyptus, SaltStack, Nimbus, General Terms and many others provide private open source cloud plat- Performance, Design forms with community support in development.
    [Show full text]
  • NIST 800-125: Guide to Security for Full Virtualization Technologies
    Special Publication 800-125 Guide to Security for Full Virtualization Technologies Recommendations of the National Institute of Standards and Technology Karen Scarfone Murugiah Souppaya Paul Hoffman NIST Special Publication 800-125 Guide to Security for Full Virtualization Technologies Recommendations of the National Institute of Standards and Technology Karen Scarfone Murugiah Souppaya Paul Hoffman C O M P U T E R S E C U R I T Y Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 January 2011 U.S. Department of Commerce Gary Locke, Secretary National Institute of Standards and Technology Patrick D. Gallagher, Director GUIDE TO SECURITY FOR FULL VIRTUALIZATION TECHNOLOGIES Reports on Computer Systems Technology The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation’s measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL’s responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Special Publication 800-series reports on ITL’s research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-125 Natl. Inst. Stand. Technol. Spec. Publ. 800-125, 35 pages (January 2010) Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately.
    [Show full text]
  • Intro Comparing and Contrasting Virtualization Technologies
    Intro Comparing and Contrasting Virtualization Technologies 9304 Do you knowAbstract the differences Part 1 between Xen and VMware? Abstract Part Two Do you know when it is more advantageous to use one over the other? Abstract Part Three Virtualization can be a complicated subject with many different facets. It is not always easy to choose the strategy that best fits your needs. I am here to help [email protected] Worldwide Design Centers Poughkeepsie, NY Montpellier, France [email protected] [email protected] Makuhari, Japan Boeblingen, Germany 6 [email protected] [email protected] Worldwide Design Centers Our mission – To architect & design innovative end to end solutions with selected worldwide clients that leverage leading-edge IBM technologies to accelerate their IT transformation . Analysis Define and analyze various solution options that meet existing and future requirements . Assessment Review and validate a planned solution, strategy, IT transformation, or architecture, and provide recommendations and roadmaps . Design Define an architecture and high level design for an IT infrastructure to meet business requirements 7 There is no There is no free free lunch lunch Types of Virtualization Hardware Virtualization Partitioned Partitioned OS OS Partition Controller Application Application Physical Machine OS FullHardware Virtualization OS OS Application Application Application Fully Virtualized Hypervisor Physical Machine ModifiedPara Virtualization Modified Modified OS OS OS Application Application Application Para Virtualized
    [Show full text]
  • Virtualization Technology
    Virtualization Technology Zhonghong Ou Data Communications Software Lab, Aalto University 1 Definition • Virtualization refers to a concept in which access to a single underlying piece of hardware, like a server, is coordinated so that multiple guest operating systems can share that single piece of hardware, with no guest operating system being aware that it is actually sharing anything at all. (A guest operating system is an operating system that’s hosted by the underlying virtualization software layer, which is often, you guessed it, called the host system.) • A guest operating system appears to the applications running on it as a complete operating system (OS), and the guest OS itself is completely unaware that it’s running on top of a layer of virtualization software rather than directly on the physical hardware. Source: Virtualization for dummies 2 Four drivers of virtualization • Hardware is underutilized – Moore’s Law: “The complexity for minimum component costs has increased at a rate of roughly a factor of two per year…”, (actually, most people estimate the timeframe at around 18 months) i.e. the number of transistors that can be placed inexpensively on an integrated circuit has doubled approximately every two years. Moore’s law • Data centers run out of space – The net effect of explosion of data is that huge numbers of servers have been put into use over the past decade, which is causing a real -estate problem for companies. • Energy costs go through the roof – The cost of running computers, coupled with the fact that many of the machines filling up data centers are running at low utilization rates, means that virtualization’s ability to reduce the total number of physical servers can significantly reduce the overall cost of energy for companies.
    [Show full text]
  • Notes on Virtualization
    Notes on Virtualization Version 9.0 Andrew Herbert 6th October 2015 Introduction The story of virtualization and the important role it has played in Operating Systems over the past 50 years. The systems and papers mentioned in the text are the author’s choice of exemplars for the concepts being discussed, they not an exhaustive list of all related research and products, nor a statement about precedence over other systems. What is “Virtualization”? In broad terms, “virtualization” in the context of operating systems principles relates to operating systems that give the illusion of efficiently running multiple independent computers known as “virtual machines”. Depending upon the specific requirements and means of virtualization, the virtual machines be directly executed by (i.e., exactly mimic) the underlying physical machine, or they may comprise a more abstract system, parts or all of which are simulated by the physical machine. Origins The term “virtual” originated with “(dynamic) virtual memory” to express the abstraction of having a large contiguously addressed store available to programs, implemented by swapping portions of data and program between main store and magnetic drum. Some of the pioneers of operating systems (Maurice Wilkes, Brian Randell, Bob Nelson) have suggested the use of the word “virtual” was inspired by optics, in the sense of “virtual” versus “real” images. The term “virtual” was then extended to include “virtual devices” with the advent of input-output spooling and file systems. A typical virtual device interface would replace the hardware input-output instructions and device interrupt handling structures with a more convenient abstract interface with functions such as OPEN, CLOSE, READ, WRITE, CREATE, and DELETE.
    [Show full text]
  • Virtualization
    Starting Point: A Physical Machine ! Physical Hardware • Processors, memory, chipset, I/O devices, etc. Virtualization • Resources often grossly underutilized ! Software • Tightly coupled to physical hardware • Single active OS instance Based on materials from: • OS controls hardware Introduction to Virtual Machines by Carl Waldspurger Understanding Intel® Virtualization Technology (VT) by N. B. Sahgal and D. Rodgers Intel Virtualization Technology Roadmap and VT-d Support in Xen by Jun Nakajima A Performance Comparison of Container-based Virtualization Systems for MapReduce Clusters by M. G. Xavier, M. V. Neves, and C.A.F. De Rose 2 © 2010 VMware Inc. All rights reserved What is a Virtual Machine? Virtualization Properties ! Isolation • Fault isolation ! Software Abstraction • Performance isolation • Behaves like hardware ! Encapsulation • Encapsulates all OS and • Cleanly capture all VM state application state • Enables VM snapshots, clones ! Virtualization Layer ! Portability • Extra level of indirection • Independent of physical hardware • Decouples hardware, OS • Enables migration of live, running VMs • Enforces isolation ! Interposition • Multiplexes physical hardware Transformations on instructions, memory, I/O across VMs • • Enables transparent resource overcommitment, encryption, compression, replication … 3 4 1 Virtualization Applications Types of Virtualization ! Process Virtualization • Language-level Java, .NET, Smalltalk • OS-level processes, Solaris Zones, BSD Jails, Docker Containers • Cross-ISA emulation Apple 68K-PPC-x86
    [Show full text]
  • DB2 Virtualization
    Front cover DB2 Virtualization Learn setting up and configuring DB2 on PowerVM, VMware, and Hyper-V Leverage virtualization technologies See best practices Whei-Jen Chen Jason Chan Olaf Mueller Malcolm Singh Tapio Väättänen ibm.com/redbooks International Technical Support Organization DB2 Virtualization September 2009 SG24-7805-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (September 2009) This edition applies to DB2 for Linux, UNIX, and Windows Version 9.1 or later, PowerVM, POWER5, POWER6, VMware Virtual Infrastructure 3 or later, vSphere 4 or later, and Microsoft Windows Server 2008 SP2 with Hyper-V RTM (Update KB950050). © Copyright International Business Machines Corporation 2009. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix The team who wrote this book . x Acknowledgement. xi Become a published author . xi Comments welcome. xii Chapter 1. Introduction . 1 1.1 Overview . 2 1.1.1 What is virtualization . 2 1.1.2 History . 4 1.1.3 Benefits . 4 1.2 Terminology and definitions . 5 1.2.1 Virtual server . 6 1.2.2 Virtual machine monitor . 6 1.2.3 Machine-based virtualization. 8 1.2.4 Operating-system-based virtualization . 11 Chapter 2. Virtualization technologies . 13 2.1 DB2 support for virtualization . 14 2.1.1 Support matrix. 14 2.1.2 Features and functions . 15 2.1.3 Licensing . 28 2.2 PowerVM on Power Systems . 31 2.3 VMware vSphere.
    [Show full text]
  • Virtualization for Cloud Computing
    Virtualization for Cloud Computing Dr. Sanjay P. Ahuja, Ph.D. 2010-14 FIS Distinguished Professor of Computer Science School of Computing, UNF University of CLOUD COMPUTING UNF NORTH FLORIDA • On demand provision of computational resources (Infrastructure, Platform, Software). • Requires high availability of resources and optimum use. • Virtualization is the enabling technology and creates virtual machines that allows a single machine to act as if it were many machines. • Benefits of virtualization for cloud computing: Reduces capital expenses and maintenance costs through server consolidation, reduces physical space needed in data centers. Resource Management, Migration, Maintainability, High availability and Fault tolerance are other benefits. • Virtualization is implemented using hypervisors. 2 University of VIRTUALIZATION UNF NORTH FLORIDA Machine Stack showing virtualization opportunities • Creation of a virtual version of hardware using software. Application • Runs several applications at the same time on a single physical server by hosting each of them inside their own virtual machine. • By running multiple virtual machines Libraries simultaneously, a physical server can be utilized efficiently. Operating Primary approaches to virtualization System • Platform virtualization Ex : Server • Resources virtualization Ex : Storage, Network Hardware 3 University of HYPERVISOR UNF NORTH FLORIDA • Hypervisor plays an important role in the virtualization scenario by virtualization of hardware. It provides support for running multiple operating systems concurrently in virtual servers created within a physical server. • The virtualization layer is the software responsible for hosting and managing all VMs. The virtualization layer is a hypervisor running directly on the hardware. • Example: VMWare, Xen, KVM. 4 University of SERVER WITHOUT VIRTUALIZATION UNF NORTH FLORIDA • Only one OS can run at a time within a server.
    [Show full text]