Winter 2010 Presentations/VMs+Emulation

Title

Virtual Machines By: Daniel Gilloch (dgilloch@learn.senecac.on.ca)

Introduction

--Slide*********************:
Is Virtualization what we need?

• Cost
• Setup
• Performance

--What I'll be saying**************:
The goal was to attempt to install a hypervisor, a piece of emulation software that's used to run guest operating systems, on an already existing hongkong machine for our koji build farm and determine whether or not this would be a viable developement solution. Some issues taken into consideration:

• Cost
• Setup
• Performance

Determining and comparing the cost of buying arm machines, vs utilizing already existing hardware.
Determining the process of setting up virtual machines and the setup of an arm machine.
A Performance benchmark using koji build as this is a real world example of the exact type of developement that will be done on the machines. Also taken into consideration is if other environmental effects on the machine could interfer with build times.

-Slide***************************************:
What is Virtualization? http://www.ok-labs.com/_assets/image_library/diagram-virtualization-stack-thumb.png [picture]

--What I'll be saying**************:

Virtualization is technology for supporting execution of computer program code, from applications to entire operating systems, in a software-controlled environment. Such a Virtual Machine (VM) environment abstracts available system resources (memory, storage, CPU core(s), I/O, etc.) and presents them in a regular fashion, such that “guest” software cannot distinguish VM-based execution from running on bare physical hardware.

Process

Cost

Slide *************: OpenRD-Base: 149.00 - http://www.globalscaletechnologies.com/images/Product/icon/20.gif [picture]
OpenRD-Client: 249.00 - http://www.open-rd.org/images/teaser/openrd_product_sm.png [picture]
SheevaPlug: 99.00 - http://www.twine.com/_b/12y98tf35-2rn/b0kw7kcd088fsf3n6v140p8prw5plhcvjwqpr7h077/12/y9/8t/f3/5-/2r/n/b0kw7kcd088fsf3n6v140p8prw5plhcvjwqpr7h077/marvell_sheevaplug_1-480x425.jpeg [picture]
Q6600 Existing Machine: apprx, $700 CAD - http://www.cty.ca/image/image250/250-2009.jpg [picture]

Installation

-Slide **********:
Arm Emulation http://blog.laptopmag.com/wpress/wp-content/uploads/2009/03/arm-processor.jpg [picture]

-What I will be saying ***********:
The hypervisor that was chosen was QEMU because it supported the ARM architecture and was already available for Fedora. Although QEMU can be run directly from the command line, there are advantages to using the libvirt management layer provided by Fedora, such as automatic start of virtual machines when the system boots, the ability to disconnect and later reconnect to a virtual machine, and a graphical mangement and monitoring tool, libvirt. After installing QEMU, and libvirt the ARM root file system and an xml file that contains instructions on how to install the fedora arm operating system. There was an issue involving SELinux, in order to solve this we had to HonkKong to permissive mode. After this point The virtual machine was able to boot.

Slide **************:
Performance
http://www.aykew.com/images/aboutwork/speed.jpg [picture]

-What I will be saying************:
In order to benchmark the virtual machines and the openrd client the most ideal situation was to run time along with building in koji as this is the intended purpose of the machines and virtual machines. I selected a package and built it multiple times on both the virtual machine and the openrd client to ensure consistancy. The Openrd client's results were very consistant at a build time of about 17 minutes, however the virtual machine's build times were sparatic. They ranged from 25 minutes to an hour depending on the work being done.

Discovery

-Slide**************:
Discovery http://www.phillyist.com/attachments/philly_jill/exclamation-mark-yellow.gif [ picture ]

-What I will be saying***********:
The ARM virtual machines are not a viable solution for our Fedora-Arm Koji Farm. The additional compilation times from the virtual machines can amount to ten times slower than that of the OpenRD client, which can really come into affect when compiling large packages which is not acceptable. The OpenRD clients were inexpensive and almost three OpenRD clients can be purchased at the cost of one of the existing machines. Another solution would be a SheevaPlug, which is generally cheaper than the OpenRD client. The SheevaPlug hardware is identical to the OpenRD, so similar performance should be expected. The SheevaPlug, however has less ports such as video or sata. Though, the OpenRD client out performs the virtual machines they do have a practical use. If an individual or organization could not afford to buy additional hardware and wishes to develop applications or is required to support them and performance is not an issue, virtualization for ARM would be a viable solution.

Images

http://www.twine.com/_b/12y98tf35-2rn/b0kw7kcd088fsf3n6v140p8prw5plhcvjwqpr7h077/12/y9/8t/f3/5-/2r/n/b0kw7kcd088fsf3n6v140p8prw5plhcvjwqpr7h077/marvell_sheevaplug_1-480x425.jpeg - SheevaPlug
http://www.newit.co.uk/store/images/OpenRD3.jpg - OpenRD client showing available ports
http://www.phillyist.com/attachments/philly_jill/exclamation-mark-yellow.gif - exclaimation mark
http://www.aykew.com/images/aboutwork/speed.jpg - speedometer
http://blog.laptopmag.com/wpress/wp-content/uploads/2009/03/arm-processor.jpg - arm processor
http://www.cty.ca/image/image250/250-2009.jpg - pc case
http://www.ok-labs.com/_assets/image_library/diagram-virtualization-stack-thumb.png - simplified virtualization stack diagram