DOCSLIB.ORG

Business Hypervisors for Real-Time Applications

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Business Hypervisors for Real-Time Applications Engineering, Technology & Applied Science Research Vol. 5, No. 4, 2015, 832-840 832 Business Hypervisors for Real-time Applications Luc Perneel H. Fayyad-Kazan Long Peng Fei Guan Martin Timmerman Department of Electronics Department of Department of Electronics Department of Department of Electronics and and Informatics, Vrije Electronics and and Informatics, Vrije Electronics and Informatics, Vrije Universiteit Universiteit Brussel, Informatics, Vrije Universiteit Brussel and Informatics, Vrije Brussel, Belgium and Dedicated- Belgium Universiteit Brussel, Dedicated-Systems Universiteit Systems Experts, Belgium luc.perneel Belgium Experts, Belgium Brussel, Belgium martin.timmerman @vub.ac.be [email protected] [email protected] [email protected] @vub.ac.be Abstract— System virtualization is one of the hottest trends in commercial ones as VMware vSphere ESXi, VirtualBox, information technology today. It is not just another nice to use OKL4, Parallels Workstation and Microsoft Hyper-V [3]. technology but has become fundamental across the business world. It is successfully used with many business application classes where Theoretically speaking, as a bare-metal hypervisor has cloud computing is the most visual one. Recently, it started to be direct access to the hardware resources rather than going used for soft Real-Time (RT) applications such as IP telephony, through a hosting operating system, it is more efficient, media servers, audio and video streaming servers, automotive and delivers greater scalability, robustness and performance [4]. communication systems in general. Running these applications on Therefore, bare-metal hypervisors are our focus in this paper. a traditional system (Hardware + Operating System) guarantee their Quality of Service (QoS); virtualizing them means inserting a Virtualization is successfully used with many business new layer between the hardware and the (virtual) Operating System application classes where cloud computing is the most visual (OS), and thus adding extra overhead. Although these applications’ one. However, the growing set of applications also includes areas do not always demand hard time guarantees, they require the soft-real time applications such as media-based ones. It is underlying virtualization layer supports low latency and provide obvious that the hypervisor layer between the hardware and the adequate computational resources for completion within a OS running in a VM incurs extra overhead compared to a non- reasonable or predictable timeframe. These aspects are intimately virtualized system. This overhead can vary from one intertwined with the logic of the hypervisor scheduler. In this paper, hypervisor type to another. Moreover, there is no quantitative a series of tests are conducted on three hypervisors (VMware ESXi, benchmark of these overheads (added latencies), which in turn Hyper-V server and Xen) to provide a benchmark of the latencies makes it difficult for users to choose the hypervisor that fits added to the applications running on top of them. These tests are their requirements. conducted for different scenarios (use cases) to take into consideration all the parameters and configurations of the Currently, there are just some technical publications [5, 6], hypervisors’ schedulers. Finally, this benchmark can be used as a initiated by the hypervisor vendors themselves, comparing reference for choosing the best hypervisor-application combination. mainly the hypervisors’ supported features. More recently, a number of unbiased scientific papers originated by researchers Keywords: ESXi; Hyper-V; Virtualization; Xen; Real-time focused on the I/O performance, network throughput and CPU utilization, using public benchmark tools which are not really I. INTRODUCTION adapted for the comparison job [7, 8]. As a consequence, most System virtualization is a technology that allows the publications are not at all quantifying their statements; others physical machine resources to be shared among different give only a limited scientific proof. Virtual Machines (VMs) via the use of a software layer called Our contribution started from this point. We want to go hypervisor or Virtual Machine Monitor (VMM). The beyond theoretical statements and quantify the performance hypervisor can be either Type-1 which runs directly on the differences (in matters of latencies) between virtualization system hardware and thus is often referred to as bare-metal solutions by focusing on their architectures and internal hypervisor, or Type-2 which runs as an application on top of a components such as scheduling policies. conventional Operating System (OS) and is referred to as hosted hypervisor [1, 2]. To achieve this, different types of tests (explained further on) are executed on the top three market hypervisors: Microsoft Due to the low cost availability of multi-core chips used in (MS) Hyper-V Server 2012R2, Xen 4.2.1 and VMware a symmetrical multiprocessor way, virtualization in the server VSphere ESXi 5.1U1. All these versions were the latest and desktop world has already matured with both software and shipping releases at the time of doing this study. The tests are hardware solutions available for several years [3]. Currently, conducted for different use cases to take into consideration all there are numerous virtualization products ranging from open- the parameters and configurations of the hypervisors’ source hypervisors such as Xen, KVM, and OpenVZ to schedulers. www.etasr.com Perneel et al.: Business Hypervisors for Real-time Applications Engineering, Technology & Applied Science Research Vol. 5, No. 4, 2015, 832-840 833 II. HYPERVISORS ARCHITECTURES VM sits idle at 10% most of the time, the other 90% of the processing time is still unavailable to any other VMs. A. Microsoft Hyper-V Server 2012 R2 Note that using the “reserve” setting limits the amount of Microsoft Hyper-V is a bare-metal micro-kernerlized virtual processors that can be shared on a physical machine, hypervisor that enables platform virtualization on x86-64 and therefore limits the number of concurrent virtual machines systems [9]. It exists in two variants: as a stand-alone product you can power on. For example, if you have 20 VMs where called Hyper-V Server [10] and as an installable feature in each one is configured to have one single virtual processor Windows Server OS. In both versions, the hypervisor is exactly whose “reserve” value is 100%, and the physical machine has the same and must have at least one parent, or root VM, four cores, then you can only power on only four virtual running Windows OS 64-bit Edition [11]. The difference machines. If you try to start a 5th VM, you would get an error between the two products are the features and components message stating that you cannot initialize the virtual machine. found in the parent (privileged) VM guest OS. Note that you will get this error even if all four running virtual Once Hyper-V is installed, VMs atop it are created. All the machines are completely idle and are not using any CPU VMs except the parent VM are called child VMs (un- resource (reason mentioned before). privileged). Hyper-V supports a number of different types of A final interesting note about the virtual machine reserve is guest OSs running in the child VMs. They can be either Hyper- that by default it is set to “0%” – which means the reserve is V Aware (enlightened/para-virtualized) Windows OSs, Hyper- disabled. Furthermore – if you have a configuration like the V Aware non-Windows OSs and Non Hyper-V Aware OSs one where all CPUs are reserved, you can still start extra virtual [12]. The hypervisor needs to deal with CPU scheduling. The machines as long as their CPU reserve is set to 0% [13]. CPU scheduler shares the same role as conventional operating systems. This role is to assign execution contexts to processors Virtual machine limit: This setting is the opposite of in a way that meets system objectives such as responsiveness, “virtual machine reserve” setting. It allows you to specify the throughput, and utilization. On conventional operating systems, maximum amount of processing power that a virtual machine the execution context corresponds to a process or a thread; on can consume and is relative to the number of processors hypervisor, it corresponds to a VM. assigned to a VM. When a VM is created atop Hyper-V, several Relative Weight: It specifies how Hyper-V allocates configurations have to be set to define its behaviour when resources to a VM when more than one VMs are running and accessing hardware resources. The basic ones are shown in compete for resources. This value ranges from 0-10000 and the Figure 1 below followed by their explanations. VM with high value receives more CPU time. By default, all VMs are assigned the same weight value (100). There is no official document explaining the scheduling algorithms of Hyper-V. Fortunately, Ben Armstrong, virtualization program manager at Microsoft, posted a four part article about CPU scheduling in Hyper-V [13]. From these articles, the scheduling algorithm of Hyper-V can be summarized as follow: If there is only one VM which has one virtual CPU (vCPU), and the hosting machine has many physical cores, then this vCPU shares the processing resources of all the physical cores. It runs on all the cores in round-robin way. The parent VM is the only VM that stays parked on the first core (core 0) [14]. Thus, Hyper-V uses a weighted round-robin scheduling algorithm. The time a vCPU spends on one physical core before being scheduled to another is not specifically mentioned in any of the public resources. This is something we measured in the testing phase. Fig. 1. Hyper-V VM configuration for resources access B. Xen Virtual machine reserve: This setting specifies the Xen is an open source hypervisor developed by Barham et percentage of the physical machine’s overall CPU resources al. [30] at the University of Cambridge in 2003. It is released reserved for this particular VM.
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]