DOCSLIB.ORG

Virtualization Security

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Virtualization Security GRD Journals- Global Research and Development Journal for Engineering | Volume 1 | Issue 12 | November 2016 ISSN: 2455-5703 Virtualization Security Abhinav Mishra Rishabh Mishra Scientist C Assistant Professor NIELIT, Gorakhpur, India DSITM, Ghaziabad, India Abstract The recent form of change in working on resources and platform introduced the term virtualization. Virtualization comes with its own merits and challenges. As it hides physical characteristics of the resources and the concept of encapsulation comes into picture. Hypervisor based architecture requires fewer hardware resources and can communicate more efficiently. All major players have introduced their hypervisor based solution to the virtualization. One of the challenges comes with it is the virtualization security. Keywords- Virtualization, attacks, sniffing, hypervisor, vm, vdi I. INTRODUCTION Accessing number of machines from one single host machine is basically server or platform virtualization. Accessed machines are referred as Virtual guest machines and the physical machine on which the machines are hosted is referred as host machine. Later the virtualization expanded its area and it involved resources such as network and memory resources and it is then termed as resource virtualization. Various players have introduced their virtualization software that are drastically being used by the organizations. Top companies in this field are:- 1) VMware: It dominates the server virtualization market with its Enterprise Virtualization Product VSphere 5.1. 2) Microsoft: Being a new entrant in virtualization race, Microsoft has come up with its Enterprise Virtualization Product Hyper-V. 3) Citrix: Known for its Para virtualized hyper visor Xen, Citrix dominates the desktop virtualization sector. 4) Oracle: Being a database giant Oracle is also offering Enterprise Virtualization Product Vbox It’s the IBM who actually introduced the concept of virtualization in the early 1964 with the development of CP-40 followed by CP [-67]/CMS at Cambridge Scientific Center. Which Is a virtual machine/virtual memory time- Sharing operating system for the IBM System. But it was VMware who took the lead with its Enterprise Level Virtualization Product VMware Server released on July 12, 2006, a free machine-level virtualization product followed by GSX, ESX and ESXi. II. HYPERVISOR ARCHITECTURE Hypervisor/Virtual Machine Monitor is software used to create and run virtual machines. Hypervisors can be categorized into two categories ie. Type-I and Type-II. A. Type-I Hypervisor Type-I hypervisor installs directly on the hardware like any other OS and is also known as bare metal hypervisor. It directly controls the physical hardware and manage requests from guest OS. In this environment guest machine operating system/Virtual machine operating system is runs above the hypervisor layer. Fig. 1: Type 1 Hypervisor All rights reserved by www.grdjournals.com 20 Virtualization Security (GRDJE/ Volume 1 / Issue 12 / 003) B. Type-II Hypervisor Type–II hypervisor does not installs directly on the physical hardware like Type-I hypervisor rather it installs within the conventional OS environment and forms a second software layer above which guest operating systems runs. Hosted hypervisors comes in this category. Fig. 2: Type 2 Hypervisor Depending upon the level of abstraction Virtualization is characterized into three main categories. 1) Full Virtualization In full virtualization environment Guest Operating System is totally isolated from the Physical hardware layer by the hypervisor. All the OS-to-hardware requests are handled by the hypervisor. Virtual machine OS is totally unaware of being virtualized. This is the most secure virtualization environment. 2) Hardware Assisted Virtualization In this type of virtualization environment some specific CPU calls from Guest Operating System/Virtual machine are directly handled by the CPU instead of being translated by hypervisor. This reduces the load on hypervisor by removing the time required to translate system calls and hence increases the performance. 3) Para virtualization In this type of virtualization, kernel of the guest OS is modified in a way so that the instruction which cannot be virtualized are replaced by the methods so that they can interact directly with the hypervisor. This type of virtualiFzation is mainly seen in Linux environments like Xen, KVM. III. DIFFERENCE BETWEEN TYPE 1 AND TYPE 2 HYPERVISOR Type 1 hypervisors run directly on the system hardware. Type 2 hypervisors run on a host operating system that provides virtualization services, such as I/O device support and memory management. Figure 2 shows how type 1 and type 2 hypervisors differ. All rights reserved by www.grdjournals.com 21 Virtualization Security (GRDJE/ Volume 1 / Issue 12 / 003) Fig. 3: Difference between Type 1 and Type 2 Hypervisor IV. FACTORS SHOULD BE EXAMINED BEFORE CHOOSING A SUITABLE HYPERVISOR One of the best ways to determine which hypervisor meets your needs is to compare their performance metrics. These include CPU overhead, amount of maximum host and guest memory, and support for virtual processors. But metrics alone should not determine your choice. In addition to the capabilities of the hypervisor, you must also verify the guest operating systems that each hypervisor supports. If you are running heterogeneous systems in your service network, then you must select the hypervisor that has support for the operating systems you currently run. If you run a homogeneous network based on Windows or Linux, then support for a smaller number of guest operating systems might fit your needs. All hypervisors are not made equal, but they all offer similar features. Understanding the features they have as well as the guest operating systems each supports is an essential aspect of any hardware virtualization hypervisor selection process. Matching this data to your organization's requirements will be at the core of the decision you make. (To get started with this process, explore the details of each hypervisor). The following factors should be examined before choosing a suitable hypervisor. A. Virtual Machine Performance Virtual systems should meet or exceed the performance of their physical counterparts, at least in relation to the applications within each server. Everything beyond meeting this benchmark is profit. Ideally, you want each hypervisor to optimize resources on the fly to maximize performance for each virtual machine. The question is how much you might be willing to pay for this optimization. The size or mission-criticality your project generally determines the value of this optimization. B. Memory Management Look for support for hardware-assisted memory virtualization. Memory overcommit and large page table support in the VM guest and hypervisor are preferred features; memory page sharing is an optional bonus feature you might want to consider. C. High Availability Each major vendor has its own high availability solution and the way each achieves it may be wildly different, ranging from very complex to minimalist approaches. Understanding both the disaster prevention and disaster recovery methods for each system is critical. You should never bring any virtual machine online without fully knowing the protection and recovery mechanisms in place. D. Live Migration Live migration is extremely important for users; along with support for live migration across different platforms and the capability to simultaneously live migrate two or more VMs, you need to carefully consider what the individual hypervisor offers in this area. E. Networking, Storage, and Security In networking, hypervisors should support network interface cards (NICs) teaming and load balancing, Unicast isolation, and support for the standard (802.1Q) virtual local area network (VLAN) trucking. Each hypervisor should also support iSCSI- and Fiber Channel-networked storage and enterprise data protection software support with some preferences for tools and APIs, Fiber Channel over Ethernet (FCoE), and virtual disk multi- hypervisor compatibility. All rights reserved by www.grdjournals.com 22 Virtualization Security (GRDJE/ Volume 1 / Issue 12 / 003) F. Management Features Look for such management features as Simple Network Management Protocol (SNMP) trap capabilities, integration with other management software, and fault tolerance of the management server — these features are invaluable to a hypervisor. V. BENEFITS OF VIRTUALIZATION Virtualization has proven to be a revolutionary technology for Enterprise Networks. Here are some of the benefits offered by Virtualization Technology. Virtualization reduces the infrastructure cost by reducing the physical hardware. Less hardware leads to less maintenance costs. Also known as Green Technology as less physical hardware in data center means less heat and less power consumption. More control with Virtual Data Centers. Server Deployment is never been an easy task for administrators but with virtualization server machines can be imported, exported or migrated with so much ease. Faster Re-deployment and Backups as virtual machines are stored in a file format so it becomes easier for administrators to backup virtual machines in open virtualization formats and recover or redeploy them. Features like snapshot can be used to revert the virtual machines to previous states. No Vender Dependencies, with Virtualization it really doesn’t matter what physical hardware you use as machine runs in a virtual environment. With Snapshots and migration of virtual
Load more

Recommended publications
  • Using EMC VNX Storage with Vmware Vsphere Techbook CONTENTS
    Using EMC® VNX® Storage with VMware vSphere Version 4.0 TechBook P/N H8229 REV 05 Copyright © 2015 EMC Corporation. All rights reserved. Published in the USA. Published January 2015 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com). 2 Using EMC VNX Storage with VMware vSphere TechBook CONTENTS Preface Chapter 1 Configuring VMware vSphere on VNX Storage Technology overview................................................................................... 18 EMC VNX family..................................................................................... 18 FLASH 1st.............................................................................................. 18 MCx multicore optimization..................................................................
    [Show full text]
  • 5 Ways Vmware Vsphere Improves Backup and Recovery
    5 Ways VMware vSphereChapter1. Improves An Introduction Backup and to VMware Recovery Virtualization CONTENTS CONTENTS..............................................................................................................2 INTRODUCTION......................................................................................................2 A BRIEF HISTORY OF VMWARE ..............................................................................3 VIRTUALIZATION ARCHITECTURE...........................................................................4 THE HYPERVISOR............................................................................................................................4 RINGS IN VIRTUALIZATION..............................................................................................................7 CPU SCHEDULER............................................................................................................................9 DIFFERENCES BETWEEN ESX & ESXI.............................................................................................9 WHAT IS A VIRTUAL MACHINE?...........................................................................12 ENCAPSULATION.......................................................................................................................... 12 VIRTUAL MACHINE HARDWARE ................................................................................................. 13 VIRTUAL MACHINE FILES ...........................................................................................................
    [Show full text]
  • Introduction to Virtualization Virtualization
    Introduction to Virtualization Prashant Shenoy Computer Science CS691D: Hot-OS Lecture 2, page 1 Virtualization • Virtualization: extend or replace an existing interface to mimic the behavior of another system. – Introduced in 1970s: run legacy software on newer mainframe hardware • Handle platform diversity by running apps in VMs – Portability and flexibility Computer Science CS691D: Hot-OS Lecture 2, page 2 Types of Interfaces • Different types of interfaces – Assembly instructions – System calls – APIs • Depending on what is replaced /mimiced, we obtain different forms of virtualization Computer Science CS691D: Hot-OS Lecture 2, page 3 Types of Virtualization • Emulation – VM emulates/simulates complete hardware – Unmodified guest OS for a different PC can be run • Bochs, VirtualPC for Mac, QEMU • Full/native Virtualization – VM simulates “enough” hardware to allow an unmodified guest OS to be run in isolation • Same hardware CPU – IBM VM family, VMWare Workstation, Parallels,… Computer Science CS691D: Hot-OS Lecture 2, page 4 Types of virtualization • Para-virtualization – VM does not simulate hardware – Use special API that a modified guest OS must use – Hypercalls trapped by the Hypervisor and serviced – Xen, VMWare ESX Server • OS-level virtualization – OS allows multiple secure virtual servers to be run – Guest OS is the same as the host OS, but appears isolated • apps see an isolated OS – Solaris Containers, BSD Jails, Linux Vserver • Application level virtualization – Application is gives its own copy of components that are not shared • (E.g., own registry files, global objects) - VE prevents conflicts – JVM Computer Science CS691D: Hot-OS Lecture 2, page 5 Examples • Application-level virtualization: “process virtual machine” • VMM /hypervisor Computer Science CS691D: Hot-OS Lecture 2, page 6 The Architecture of Virtual Machines J Smith and R.
    [Show full text]
  • IBM Virtual Machine Facility/370 : Systems Introduction
    GC20-1800-0 IBM Virtual Machine Facility/370 : Systems Introduction The IBM Virtual Machine Facility/370 (VM/370) is a System Control Program (SCP) that has been designed specifically for the IBM System/370. VM/370 manages the IBM System/370 in such a way that mUltiple remote terminal users appear to have a dedicated computing system at their disposal. Within this "virtual machine" the user may run the operaHng system of his choice, subject to the restrictions noted in "Appendix C: VM/370 Restrictions" of this manual. The design of VM/370 is based on the IBM Control Program-67/Cam­ bridge Monitor System (CP-67/CMS) which is executed on an IBM System/360 Model 67. The Conversational Monitor System (CMS) is the major subsystem ofVM/370. CMS provides problem solving and program development services to the user, as well as supporting facilities for a remote user who chooses to run some other operating system in his virtual machine. This manual provides introductory information about the facilities provided by VM/370, and defines the min­ imum equipment configuration necessary for execution. Preface This manual provides introductory information on the IBM Virtual Machine Facility/370 (VM/370) and its associated subsystem, the Conversational Monitor Sys­ tem (CMS), as well as an overview of the purpose and functions of VM/370. It is assumed that the user has a prior knowledge of virtual storage concepts as implemented on the IBM System/370 via dynamic address translation. The reader is referred to Part I of the student text publication Introduction to Virtual Storage in System/370, Order No.
    [Show full text]
  • System Administration Guide
    Experion PKS Release 516 System Administration Guide EPDOC-X139-en-516A August 2020 DISCLAIMER This document contains Honeywell proprietary information. Information contained herein is to be used solely for the purpose submitted, and no part of this document or its contents shall be reproduced, published, or disclosed to a third party without the express permission of Honeywell International Sàrl. While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The information and specifications in this document are subject to change without notice. Copyright 2020 - Honeywell International Sàrl 2 Contents CONTENTS Contents 3 Chapter 1 - About this guide 9 Before reading this guide 10 Chapter 2 - System administration 11 Administering users 12 Windows user accounts 12 Users and groups 12 Passwords administration 13 Deleting a user 13 Experion Operator accounts 14 Control Builder client licenses 14 Administering displays 15 Changing service account passwords 16 Service account scope types 18 Changing passwords for single-machine scope accounts 21 Changing passwords for multi-machine scope accounts 22 Preparing to change passwords for system-wide scope accounts 23 Changing passwords for system-wide scope accounts 26 Changing DSA Advanced Security
    [Show full text]
  • Virtual Machine Benchmarking Kim-Thomas M¨Oller Diploma Thesis
    Universitat¨ Karlsruhe (TH) Institut fur¨ Betriebs- und Dialogsysteme Lehrstuhl Systemarchitektur Virtual Machine Benchmarking Kim-Thomas Moller¨ Diploma Thesis Advisors: Prof. Dr. Frank Bellosa Joshua LeVasseur 17. April 2007 I hereby declare that this thesis is the result of my own work, and that all informa- tion sources and literature used are indicated in the thesis. I also certify that the work in this thesis has not previously been submitted as part of requirements for a degree. Hiermit erklare¨ ich, die vorliegende Arbeit selbstandig¨ und nur unter Benutzung der angegebenen Literatur und Hilfsmittel angefertigt zu haben. Alle Stellen, die wortlich¨ oder sinngemaߨ aus veroffentlichten¨ und nicht veroffentlichten¨ Schriften entnommen wurden, sind als solche kenntlich gemacht. Die Arbeit hat in gleicher oder ahnlicher¨ Form keiner anderen Prufungsbeh¨ orde¨ vorgelegen. Karlsruhe, den 17. April 2007 Kim-Thomas Moller¨ Abstract The resurgence of system virtualization has provoked diverse virtualization tech- niques targeting different application workloads and requirements. However, a methodology to compare the performance of virtualization techniques at fine gran- ularity has not yet been introduced. VMbench is a novel benchmarking suite that focusses on virtual machine environments. By applying the pre-virtualization ap- proach for hypervisor interoperability, VMbench achieves hypervisor-neutral in- strumentation of virtual machines at the instruction level. Measurements of dif- ferent virtual machine configurations demonstrate how VMbench helps rate and predict virtual machine performance. Kurzfassung Das wiedererwachte Interesse an der Systemvirtualisierung hat verschiedenartige Virtualisierungstechniken fur¨ unterschiedliche Anwendungslasten und Anforde- rungen hervorgebracht. Jedoch wurde bislang noch keine Methodik eingefuhrt,¨ um Virtualisierungstechniken mit hoher Granularitat¨ zu vergleichen. VMbench ist eine neuartige Benchmarking-Suite fur¨ Virtuelle-Maschinen-Umgebungen.
    [Show full text]
  • Virtualization with Cisco UCS, Nexus 1000V, and Vmware Technology Design Guide
    Virtualization with Cisco UCS, Nexus 1000V, and VMware TECHNOLOGY DESIGN GUIDE August 2013 Table of Contents Preface ........................................................................................................................................1 CVD Navigator .............................................................................................................................2 Use Cases .................................................................................................................................. 2 Scope ......................................................................................................................................... 2 Proficiency .................................................................................................................................. 3 Introduction .................................................................................................................................4 Technology Use Cases ............................................................................................................... 4 Use Case: Reduce Application Deployment Time ................................................................... 5 Use Case: Simplify Network Management in the Data Center ................................................ 5 Use Case: Increase Network Performance in the Hypervisor Environment ............................. 5 Design Overview ........................................................................................................................
    [Show full text]
  • Simuboost: Scalable Parallelization of Functional System Simulation
    SimuBoost: Scalable Parallelization of Functional System Simulation Zur Erlangung des akademischen Grades eines Doktors der Ingenieurwissenschaften von der KIT-Fakultät für Informatik des Karlsruher Instituts für Technologie (KIT) genehmigte Dissertation von Dipl.-Inform. Marc Rittinghaus aus Iserlohn Tag der mündlichen Prüfung: 19.07.2019 Hauptreferent: Prof. Dr. Frank Bellosa Karlsruher Institut für Technologie Korreferent: Prof. Dr. Hans P. Reiser Universität Passau KIT – Universität des Landes Baden-Württemberg und nationales Forschungszentrum in der Helmholtz-Gemeinschaft www.kit.edu Abstract Gathering detailed run-time information such as memory access traces in operating system and security research often involves functional full system simulation (FFSS). The simulator runs the workload of interest in a virtual machine (VM), gradually interpreting or translating instructions so that they operate on the state of the VM and allow for comprehensive instrumentation. While functional full system simulation is a powerful tool, a severe limitation is its immense slowdown. For QEMU, we have measured average slowdowns of 30x and 60x for plain simulation and tracing of memory accesses, respectively. Simulators offering more advanced instrumentation capabilities can even be an order of magnitude slower. This quickly renders functional simulation impractical for long-running, networked, or interactive workloads. Furthermore, the slowdown creates unrealistic timing behavior whenever activities external to the virtual machine (e.g., I/O) are involved. In this thesis, we present SimuBoost, a method for drastically accelerating func- tional full system simulation. SimuBoost runs the workload in a fast and interactive hardware-assisted virtual machine while periodically taking checkpoints. These checkpoints then serve as starting points for simulations, enabling to simulate and analyze each interval simultaneously in one job per interval.
    [Show full text]
  • Understanding Abstraction and Virtualization
    12/07/2016 Understanding Abstraction and Virtualization Víctor J. Sosa S. [email protected] VIRTUALIZATION Virtualization is a technology that allows creating an abstraction (a virtual version) of computer resources , such as hardware architecture, operating system, storage, network, etc. With this abstraction, for example, a single machine can act like many machines working independently. The usual goal of virtualization is to centralize administrative tasks while improving scalability and workloads. It is not a new concept or technology in computer sciences. Virtual machine concept was in existence since 1960s when it was first developed by IBM to provide concurrent, interactive access to a mainframe computer. 1 12/07/2016 VIRTUALIZATION Reduce power consumption (air conditioning needs, trim the building space and land requirements associated with server farm growth), High availability for critical applications , and streamlines application deployment and migrations, Simplifies IT operations and allow IT organizations to respond faster to changing business demands , Greenhouse gas reduction The socio-political ramifications of global warming requiring good corporate citizens to meet targets, creates an added incentive for virtualization. 2 12/07/2016 EXAMPLE OF USE OF A VIRTUAL MACHINE MONITOR (VMM) APPLICATION PROGRAMMING INTERFACE , A PPLICATION BINARY INTERFACE , AND INSTRUCTION SET ARCHITECTURE . A N APPLICATION USES LIBRARY FUNCTIONS (A1), MAKES SYSTEM CALLS (A2), AND EXECUTES MACHINE INSTRUCTIONS (A3). 3 12/07/2016 VIRTUAL MACHINE MONITOR : EXAMPLES VM technology allows multiple virtual machines to run on a single physical machine. App App App App App Xen Guest OS Guest OS Guest OS (Linux) (NetBSD) (Windows) VMWare VM VM VM Virtual Machine Monitor (VMM) / Hypervisor UserModeLinux Hardware Denali etc.
    [Show full text]
  • Block-Level Storage Virtualization
    Virtulization Nelson L. S. da Fonseca IEEE ComSoc Summer Scool Albuquerque, July 17-21, 2017 Acknowledgement • Some slides in this set of slides were kindly provided by: • Luiz Fernando Bittencourt, University of Campinas • EMC Corporation Virtualization “Virtualization means to create a virtual version of a device or resource, such as a server, storage device, network or even an operating system where the framework divides the resource into one or more execution environments. Devices, applications and human users are able to interact with the virtual resource as if it were a real single logical resource.” http://www.webopedia.com/TERM/V/virtualization.html Virtualization - Features • Sharing of resources • Isolation • Agregation Virtualization - advantages • Fast deployment • Scalability • Load consolidation • Flexibility • Mobility • Green Virtualized Data Center (VDC) Virtualize Network Virtualize Storage Virtualize Compute Classic Data Center (CDC) Server Virtualization Compute Virtualization • It is a technique of masking or abstracting the physical compute hardware and enabling multiple operating systems (OSs) to run concurrently on a single or clustered physical machine(s). • Virtual Machine is a logical entity that looks and behaves like physical machine • Virtualization layer resides between hardware and VMs (hypervisor) • VMs are provided with standardized hardware resources Process Virtual Machine X System Virtual Machine Virtual Machine • From a user’s perspective, a logical compute system • Runs an operating system (OS) and
    [Show full text]
  • Implementation of Nested Virtual Laboratory System
    Jaakko Nurmi Implementation of Nested Virtual Laboratory System Bachelor thesis Information Technology March 2016 Tekijä/Tekijät Tutkinto Aika Jaakko Nurmi Insinööri (AMK) maaliskuu 2016 Opinnäytetyön nimi 39 sivua Implementation of nested Virtual Laboratory System 3 liitesivua Toimeksiantaja Kymenlaakson ammattikorkeakoulu Ohjaaja Lehtori Vesa Kankare Tiivistelmä Tämän opinnäytetyön tarkoituksena oli luoda helppokäyttöinen virtualisoitu laboratorio- alusta tietoverkkotekniikan ja kyberturvallisuuden käytännön harjoituksiin. Työssä hyö- dynnettiin paljon jo olemassa olevaa teknologiaa ja lisäksi luotiin muutamia omia tek- nologioita. Yksi niistä on virtuaalinen kytkentäkaapeli, joka kykenee simuloimaan kaa- pelissa tapahtuvia häiriöitä. Työssä käsitellään sisäkkäistä virtualisointia (Nested virtualization) ja muita käytettyjä teknologioita sekä niiden ominaisuuksia. Käytännön osuudessa käsitellään virtuaalisen laboratorioympäristön toimintaa, ominaisuuksia ja etuja verrattuna fyysisiin laitteisiin sekä muutamia kehitysideoita tulevaisuuden varalle. Lopputuloksena syntyi helppokäyttöinen virtualisoitu tietoverkkolaboratorioympäristö, joita käytettiin ja kokeiltiin muun muassa Advanced routing-, Network security equip- ment ja Service provider networks -kursseilla pääsääntöisesti hyvin lopputuloksin. Si- vutuotteena syntyi kaksi virtuaalista demoskenaariota kyberturvallisuuden opettami- seen. Näitä skenaarioita kokeiltiin penetraatiotestaus-kurssilla. Työn loppupuolella toteutettiin pieni käyttäjäkysely, jolla mitattiin loppukäyttäjien
    [Show full text]
  • Dynamic Load Balancing of Virtual Machines Hosted on Xen
    Brigham Young University BYU ScholarsArchive Theses and Dissertations 2008-12-10 Dynamic Load Balancing of Virtual Machines Hosted on Xen Terry Clyde Wilcox Brigham Young University - Provo Follow this and additional works at: https://scholarsarchive.byu.edu/etd Part of the Computer Sciences Commons BYU ScholarsArchive Citation Wilcox, Terry Clyde, "Dynamic Load Balancing of Virtual Machines Hosted on Xen" (2008). Theses and Dissertations. 1654. https://scholarsarchive.byu.edu/etd/1654 This Thesis is brought to you for free and open access by BYU ScholarsArchive. It has been accepted for inclusion in Theses and Dissertations by an authorized administrator of BYU ScholarsArchive. For more information, please contact [email protected], [email protected]. DYNAMIC LOAD BALANCING OF VIRTUAL MACHINES HOSTED ON XEN by Terry C. Wilcox Jr. A thesis submitted to the faculty of Brigham Young University in partial fulfillment of the requirements for the degree of Master of Science Department of Computer Science Brigham Young University April 2009 Copyright c 2009 Terry C. Wilcox Jr. All Rights Reserved BRIGHAM YOUNG UNIVERSITY GRADUATE COMMITTEE APPROVAL of a thesis submitted by Terry C. Wilcox Jr. This thesis has been read by each member of the following graduate committee and by majority vote has been found to be satisfactory. Date Phillip J. Windley, Chair Date Kelly J. Flanagan Date Tony R. Martinez BRIGHAM YOUNG UNIVERSITY As chair of the candidate’s graduate committee, I have read the thesis of Terry C. Wilcox Jr. in its final form and have found that (1) its format, citations, and bibli- ographical style are consistent and acceptable and fulfill university and department style requirements; (2) its illustrative materials including figures, tables, and charts are in place; and (3) the final manuscript is satisfactory to the graduate committee and is ready for submission to the university library.
    [Show full text]