Abstract
The aim of this paper is to compare the performance between three hypervisors: XEN-PV, XEN-HVM and Open-VZ. We have simulated the migration of a virtual machine by using a warning failure approach. Based on some experiments we have compared CPU Consumption, Memory Utilization, Total Migration Time and Downtime. We have also tested the hypervisor’s performance by changing the packet’s size from 1500 byte to 64 byte. From these tests we have concluded that Open-VZ has a bigger CPU Consumption than XEN-PV, but the Total Migration time is smaller than in XEN-PV. XEN-HVM has a worse performance than XEN-PV, especially regarding to Downtime parameter.
Highlights
One of the most interesting technologies in the field of information technology nowadays is Virtualization
In our article we have studied three types of hypervisors and we have measured their performance regarding the file‟s time of transfer, CPU efficiency and memory utilization from a virtual machine to another in the same physical host or between virtual machines in different physical hosts
Referred to figure 3, initially we will prepare a warning failure of x0 virtual machine. It means that x0 virtual machine in reality is operating, but the hypervisor and the other virtual machine built above the hypervisor are informed from heartbeat tool which is included in CentOS 5.5, that it is stopped as we explained in section 3.To simulate a warning failure we should create a script in C programming language and we call it heartcare
Summary
One of the most interesting technologies in the field of information technology nowadays is Virtualization. It is required that the processors have the same characteristics In this way, the communication between applications in virtual machines and I/O devices will be realized through virtual I/O drivers which rise above the hypervisor. There are some methods of its migration, but the most used is the iteration method with Pre-Copy approach In this method, at first the modified pages are transferred, which are registered from a table in memory which is managed by XEN. Since every GuestOS is a process in OpenVZ hypervisor, this method offers a better possibility than Xen in scalability but weaker in isolation. All the above hypervisors support the SMP (Symmetric Multi-Processor) technique This means that some GuestOS can use some host processors at the same time
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
