DOCSLIB.ORG

Exercise 1: Virtualization with Virtualbox Duration: 45Min Maximum Points: 10

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Exercise 1: Virtualization with Virtualbox Duration: 45Min Maximum Points: 10 RUHR-UNIVERSITY BOCHUM Chair for Exercises Operating System Security System Security WS2009/10 Exercise 1: Virtualization with VirtualBox Duration: 45min Maximum Points: 10 Introduction Virtualization is mainly used for two reasons: To enable (hardware) resource sharing and to isolate various computing environments (isolation). While the first increases efficiency, the latter can strengthen security by enforcing process- and resource separation. The Virtual Machine Monitor (VMM) is a software component that is located between the hardware and the Virtual Machine (VM) respectively between the Host Operating Sytem (Host OS) and the VM, depending on the type of virtualization. Goldberg [1] defined two types of VMMs: Type I VMMs run on the bare machine hardware. Type II VMMs run on a Host OS. VirtualBox is a virtualization software of Type II. It allows to run 32-bit as well as 64-bit operating systems in a VM on top of a Host OS. It allows to use the hardware virtualization features of modern Intel and AMD processors as well as to virtualize the VM entirely in software. As the practical exercises of this course will make use of VirtualBox, it is essential that you are familiar with it. You will find an exhaustive introduction to virtualization in general at http://www.kernelthread.com/publications/virtualization/. The VirtualBox User Manual [2] is also a good guide for the practical exercises. Don't hesitate to use it! 1 Homework (3 Points) 1. In which scenarios is virtualization useful? Give a short explanation why. 2. What is a snapshot and what does the virtualization software do when you take a snapshot? How does it handle the virtual disk? 3. Think of the following two scenarios and explain what kind of virtualization soft- ware (full virtualization, hardware-assisted virtualization or para-virtualization) you would choose! Justify your decision! a) You have an old, closed-source OS for which vendor support has expired. Your supervisor asks you to run two instances of it (one as a mail and one as a database server) on an older, unused server. b) The IT Department wants to use this brand new open-source OS. They need to run several instances of this OS. Unfortunately, they spend most of their money for lightsabers, USB-coffeecup heaters and so forth. Your job is to buy hardware and make the VMs as fast as possible for the least amount of money. 1 RUHR-UNIVERSITY BOCHUM Chair for Exercises Operating System Security System Security WS2009/10 2 Practical Exercises 2.1 Creating a Virtual Machine and Installing an Operating System (2 Points) • Start VirtualBox. • Create a virtual machine with the following configuration: Name: DSL OS Type: Linux 2.4 Base Memory Size: 256 Virtual Hard Disk: dynamically expanding, Image file name: dsl, Image size: 1 GB • Mount the isofile dsl-4.4.6.iso to the virtual CD-ROM. • Now, start the VM and boot from CD-ROM. • You will see the DSL boot prompt. Type install and hit Enter. • Before you can install the OS, you need to prepare the hard drive. Create a partition table with the following partitions: (Attention: the keyboard layout setting for the started system is en-US! So the letter y is on the german key z.) part. type: FS type: size: flag: 1. partition: primary linux swap (type 82) 256MB 2. partition: primary linux (type 83) the rest Bootable • Go back to the DSL install options screen. Choose: install to hard drive • When you are asked for a bootloader, choose GRUB. • During the reboot process the system wants you to eject the CD. Unmount the CD and press enter. • During the first boot, DSL will ask you for some passwords. Just leave them blank and cancel the DSL X Setup dialog. • If you like, you can now change the keyboard layout to DE in the control panel. Congratulations! You have just installed a DamnSmallLinux into your VM. 2.2 Getting Familiar with Snapshots (1 Point) • Create a snapshot of your running VM. • We simulate an attack or system failure in the following. Therefore, open a terminal and type: sudo rm /boot/linux24 2 RUHR-UNIVERSITY BOCHUM Chair for Exercises Operating System Security System Security WS2009/10 • Reboot. • You will notice that the system is not able to boot. • Revert to the previously taken snapshot and start the VM again. • Your system should run again now. 2.3 Networking (4 Points) Prepare the following steps: • Assign a network interface in Network Address Translation (NAT) mode to one VM (choose one of the available VMs from your VirtualBox installation). • Assign a network interface in Host Interface Networking (HIF) mode to another VM. Start the VMs and copy a file directly from one VM to the other VM using a direct network connection. For example, use protocols like the File Transfer Protocol (FTP) or the Secure Copy Protocol (SCP). 1. Which direction did you choose: NAT ! HIF or HIF! NAT? 2. Is the other way round also possible? If it is possible, what would you have to do to make it work? 3. Sniff the network interface of the host. Which traffic can you see? 4. Set up a network between the two VMs so the host cannot see the traffic of this network by sniffing its network interface. (! Be aware that this is not a secure way to share data. If someone has control over the host, he can control every software running on this host and can therefore change the virtualization software to reveal this data. Also the information has to be stored somewhere in the hardware (e.g., RAM). Others can just access this hardware to read the data.) 3 Bonus Exercises (+3 Points) An interesting area using VM technology is the application of so-called honeypot envi- ronments ("honeypots"). A honeypot is only apparently an exact copy of a productive computing environment. It is used to attract the adversaries' interest in attacking com- puter systems to collect data about their techniques and behaviour. However, adversaries may be able to detect that the target system is running in a VM and thus may let their malware behave differently to counter analysis. But not only adversaries are interested in VM detection. Think of malware that uses virtualization technology. It may be hard 3 RUHR-UNIVERSITY BOCHUM Chair for Exercises Operating System Security System Security WS2009/10 to detect by conventional malware scanners. You can use http://bluepillproject.org as a starting point for your research. Keep in mind that Rutkowska has a hacker-centric point of view which is not always scientific. List all the references you refer to. 1. Name the four different categories of methods to detect that you are running inside a VM and give a short explanation of each one of them. 2. At the BlackHat 2006 conference, Rutkowska introduced a VM technology called "BluePill". BluePill claims to prevent VM detection. Discuss each of the four different VM detection approaches in the context of their effect on BluePill. 3. Think of the following scenario: You assume that you have a VMM running di- rectly on the platform's hardware (no Host OS). Inside this VMM runs an operating sytem. An adversary has managed to install a bluepilled VMM between the hard- ware and the VMM. Can you detect the bluepilled VMM from inside the Guest OS? Explain! 4. Where else can you place the bluepilled VMM detection software? Will this ap- proach be more promising and is there a drawback in this approach? References [1] R. P. Goldberg, Cambridge, Massachusetts, United States. Architecture of virtual machines. In Proceedings of the ACM Workshop on Virtual Computer Systems, 1973 Pages 74-112. [2] Sun Microsystems, Inc. VirtualBox User Manual, Version 3.08. Available online at http://download.virtualbox.org/virtualbox/3.0.8/UserManual.pdf. 4.
Load more

Recommended publications
  • Effective Virtual CPU Configuration with QEMU and Libvirt
    Effective Virtual CPU Configuration with QEMU and libvirt Kashyap Chamarthy <[email protected]> Open Source Summit Edinburgh, 2018 1 / 38 Timeline of recent CPU flaws, 2018 (a) Jan 03 • Spectre v1: Bounds Check Bypass Jan 03 • Spectre v2: Branch Target Injection Jan 03 • Meltdown: Rogue Data Cache Load May 21 • Spectre-NG: Speculative Store Bypass Jun 21 • TLBleed: Side-channel attack over shared TLBs 2 / 38 Timeline of recent CPU flaws, 2018 (b) Jun 29 • NetSpectre: Side-channel attack over local network Jul 10 • Spectre-NG: Bounds Check Bypass Store Aug 14 • L1TF: "L1 Terminal Fault" ... • ? 3 / 38 Related talks in the ‘References’ section Out of scope: Internals of various side-channel attacks How to exploit Meltdown & Spectre variants Details of performance implications What this talk is not about 4 / 38 Related talks in the ‘References’ section What this talk is not about Out of scope: Internals of various side-channel attacks How to exploit Meltdown & Spectre variants Details of performance implications 4 / 38 What this talk is not about Out of scope: Internals of various side-channel attacks How to exploit Meltdown & Spectre variants Details of performance implications Related talks in the ‘References’ section 4 / 38 OpenStack, et al. libguestfs Virt Driver (guestfish) libvirtd QMP QMP QEMU QEMU VM1 VM2 Custom Disk1 Disk2 Appliance ioctl() KVM-based virtualization components Linux with KVM 5 / 38 OpenStack, et al. libguestfs Virt Driver (guestfish) libvirtd QMP QMP Custom Appliance KVM-based virtualization components QEMU QEMU VM1 VM2 Disk1 Disk2 ioctl() Linux with KVM 5 / 38 OpenStack, et al. libguestfs Virt Driver (guestfish) Custom Appliance KVM-based virtualization components libvirtd QMP QMP QEMU QEMU VM1 VM2 Disk1 Disk2 ioctl() Linux with KVM 5 / 38 libguestfs (guestfish) Custom Appliance KVM-based virtualization components OpenStack, et al.
    [Show full text]
  • A Virtual Machine Environment for Real Time Systems Laboratories
    AC 2007-904: A VIRTUAL MACHINE ENVIRONMENT FOR REAL-TIME SYSTEMS LABORATORIES Mukul Shirvaikar, University of Texas-Tyler MUKUL SHIRVAIKAR received the Ph.D. degree in Electrical and Computer Engineering from the University of Tennessee in 1993. He is currently an Associate Professor of Electrical Engineering at the University of Texas at Tyler. He has also held positions at Texas Instruments and the University of West Florida. His research interests include real-time imaging, embedded systems, pattern recognition, and dual-core processor architectures. At the University of Texas he has started a new real-time systems lab using dual-core processor technology. He is also the principal investigator for the “Back-To-Basics” project aimed at engineering student retention. Nikhil Satyala, University of Texas-Tyler NIKHIL SATYALA received the Bachelors degree in Electronics and Communication Engineering from the Jawaharlal Nehru Technological University (JNTU), India in 2004. He is currently pursuing his Masters degree at the University of Texas at Tyler, while working as a research assistant. His research interests include embedded systems, dual-core processor architectures and microprocessors. Page 12.152.1 Page © American Society for Engineering Education, 2007 A Virtual Machine Environment for Real Time Systems Laboratories Abstract The goal of this project was to build a superior environment for a real time system laboratory that would allow users to run Windows and Linux embedded application development tools concurrently on a single computer. These requirements were dictated by real-time system applications which are increasingly being implemented on asymmetric dual-core processors running different operating systems. A real time systems laboratory curriculum based on dual- core architectures has been presented in this forum in the past.2 It was designed for a senior elective course in real time systems at the University of Texas at Tyler that combines lectures along with an integrated lab.
    [Show full text]
  • 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]
  • 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]
  • Oracle® Linux Virtualization Manager Getting Started Guide
    Oracle® Linux Virtualization Manager Getting Started Guide F25124-11 September 2021 Oracle Legal Notices Copyright © 2019, 2021 Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Virtualizationoverview
    VMWAREW H WHITEI T E PPAPERA P E R Virtualization Overview 1 VMWARE WHITE PAPER Table of Contents Introduction .............................................................................................................................................. 3 Virtualization in a Nutshell ................................................................................................................... 3 Virtualization Approaches .................................................................................................................... 4 Virtualization for Server Consolidation and Containment ........................................................... 7 How Virtualization Complements New-Generation Hardware .................................................. 8 Para-virtualization ................................................................................................................................... 8 VMware’s Virtualization Portfolio ........................................................................................................ 9 Glossary ..................................................................................................................................................... 10 2 VMWARE WHITE PAPER Virtualization Overview Introduction Virtualization in a Nutshell Among the leading business challenges confronting CIOs and Simply put, virtualization is an idea whose time has come. IT managers today are: cost-effective utilization of IT infrastruc- The term virtualization broadly describes the separation
    [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]
  • Oracle Virtualbox Installation, Setup, and Ubuntu Introduction
    ORACLE VIRTUALBOX INSTALLATION, SETUP, AND UBUNTU INTRODUCTION • VirtualBox is a hardware virtualization program. • Create virtual computers aka virtual machines. • Prototyping, sandboxing, testing. • The computer that VirtualBox is installed on is called the “host”, and each virtual machine is called a “guest”. PREREQUISITES Since virtual machines share resources with the host computer, we need to know what resources we have available on our host. • Click “Type here to search”. • Search for “System Information”. • Note the number of processor cores and the amount of RAM installed in your host. PREREQUISITES • Expand “Components”. • Expand “Storage”. • Select “Drives”. • Note the amount of free space available on your host. Every computer is different, so how we will need to balance these resources between our host and guest systems will differ. DOWNLOADING VIRTUALBOX • VISIT VIRTUALBOX.ORG • SELECT THE CORRECT PACKAGE • CLICK THE DOWNLOAD LINK. FOR YOUR HOST. INSTALLING VIRTUALBOX • Browse to where you downloaded VirtualBox and run the installer. • All default options will be fine. Simply follow the prompts. INSTALLING VIRTUALBOX • CLICK “FINISH”. • VIRTUALBOX INSTALLED! SETTING THINGS UP Before we build our first virtual machine, we need to download an operating system to install as our “guest”. • Visit Ubuntu.com • Click “Download”. • Select the current Ubuntu Desktop “LTS” release. • LTS releases focus on stability rather than cutting edge features. SETTING THINGS UP • IN VIRTUALBOX, CLICK “NEW”. • NAME THE VIRTUAL MACHINE. SETTING THINGS UP Here’s where we will need the system resources information that we looked up earlier. Each virtual machine functions like a separate computer in and of itself and will need to share RAM with the host.
    [Show full text]
  • Container and Kernel-Based Virtual Machine (KVM) Virtualization for Network Function Virtualization (NFV)
    Container and Kernel-Based Virtual Machine (KVM) Virtualization for Network Function Virtualization (NFV) White Paper August 2015 Order Number: 332860-001US YouLegal Lines andmay Disclaimers not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein. No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest Intel product specifications and roadmaps. The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Copies of documents which have an order number and are referenced in this document may be obtained by calling 1-800-548-4725 or by visiting: http://www.intel.com/ design/literature.htm. Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Learn more at http:// www.intel.com/ or from the OEM or retailer. Results have been estimated or simulated using internal Intel analysis or architecture simulation or modeling, and provided to you for informational purposes. Any differences in your system hardware, software or configuration may affect your actual performance. For more complete information about performance and benchmark results, visit www.intel.com/benchmarks. Tests document performance of components on a particular test, in specific systems.
    [Show full text]
  • Introduction to Real-Time Virtualization (Hypervisor)
    Introduction to the NI Real-Time Hypervisor 1 Agenda 1) NI Real-Time Hypervisor overview 2) Basics of virtualization technology 3) Configuring and using Real-Time Hypervisor systems 4) Performance and benchmarks 5) Case study: aircraft arrestor system NI Real-Time Hypervisor Overview NI Real-Time Hypervisor • Run NI LabVIEW Real-Time Windows XP LabVIEW Real-Time and Windows XP in parallel • Partition I/O devices, RAM, NI Real-Time Hypervisor and CPUs between OSs • Uses virtualization I/O RAM CPUs technology and Intel VT Benefits of the Real-Time Hypervisor • Capability: make use of real-time processing and Windows XP services Applications Determinism Graphics Real-Time I/O Services Timing Benefits of the Real-Time Hypervisor • Consolidation: reduce hardware costs, wiring, and physical footprint Virtualized System with NI Real-Time Hypervisor Benefits of the Real-Time Hypervisor • Efficiency: take advantage of multicore processors effectively Quad-Core Controller with Virtualization Windows XP LabVIEW Real-Time Basics of Virtualization Technology What Is Virtualization? • The term: refers to abstraction of OSs from hardware resources • In practice: running multiple OSs simultaneously on a single computer Virtualization Software Architectures • Software: virtual machine monitor (VMM) or Hypervisor • Two main variations: hosted and bare-metal Hosted (VMWare) Bare-Metal (NI Real-Time Hypervisor) How Does Virtualization Software Work? • OSs are “unaware” of being virtualized • Hypervisor is called only when needed • Various mechanisms for
    [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]