Performance Evaluation of Xen Vs. OpenVZ
An anonymous reader writes "Compared to an operating-system-level virtualization technology like OpenVZ, Xen — a hypervisor-level virtualization technology that allows multiple operating systems to be run with and without para-virtualization — trades off performance for much better isolation and security. OpenVZ's performance advantage due to running virtual containers in a single operating system kernel can be significant. A performance evaluation study (PDF) done by researchers at the University of Michigan and HP labs provides insight into how big a performance penalty Zen pays and what causes the overheads (primarily L2 cache misses)." From the report: "We compare both technologies with a base system in terms of application performance, resource consumption, scalability, low-level system metrics like cache misses and virtualization-specific metrics like Domain-0 consumption in Xen. Our experiments indicate that the average response time can increase by over 400% in Xen and only a modest 100% in OpenVZ as the number of application instances grows from one to four... A similar trend is observed in CPU consumptions of virtual containers."
Which I'm sure is feeling the heat from Xen.
Hax-fu?
[Xen]... "trades off performance for much better isolation and security."
No kidding, that's why I use it! Xen's performance ain't so bad. Show me a better performing virtualization solution that matches or bests Xen's isolation security - then we'll talk.
Xen's benchmarks vs. native, VM and UML are pretty decent. Not sure what cleverly crafted scenarios they're using here.
I want to delete my account but Slashdot doesn't allow it.
Kernel VM is based off QEMU -- but doesn't Xen have a similar hypervised Linux kernel. (I personally thought that may be why KVM was created -- to be a better Xen.) As I'll eventually upgrade to a Linux distro with KVM, I wonder if there are similarities in them -- or preferably if KVM could be fully tested and compared with these results.
" hypervisor-level virtualization technology that allows multiple operating systems to be run with and without para-virtualization "
I don't know about you but it still makes my eyes hurt!
09 F9 11 02 9D 74 E3 5B - D8 41 56 C5 63 56 88 C0 45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
Zen's performance issues were fixed by Avon, under Orac's guidance.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
Hypervisor — the software that makes the virtualization happen... sometimes means virtualization that runs on bare-metal, rather than under a host OS.
Paravirtualization — I think this just refers to the cases where the guest OS is modified/recompiled to run work without needing to run in Ring 0, and instead changes those to be explicit calls to the virtualization software.
So translated, I think that means "virtualization software that runs on bare-metal, both using unmodified guest OS's, and modified guest OS's."
I use vserver in combination with unionfs, which just rocks.
I can add and remove (semi) virtual machine at will. Each VM feels barely heavier than just an ordinary process.
I take my normal mount points, and make it the read-only layer. I then add a writable layer on top of that and that's it. I've also created some handy scripts that'll let me manage, add, remove, start, stop, etc, VM's.
From reading the article on hypervisor it still seems ambiguous. It implies that a hypervisor is not exactly a VM but the actual detailed description makes it out to be a VM. Others seem to imply it means the VM is running as an OS basically.
From everything I can see though the word is useless and it amounts to the equivalent of computer scientists being fussy. VM or VM OS are better choices.
OpenVZ works with FreeBSD?
Does anyone have links to show the support?
As somebody that actually has experience setting up and running virtualized systems (I work for a web hosting company) let me add my two cents here.
OpenVZ is ok if all of your child environments run the same OS and you don't care about them stealing each other's resources. We constantly have problems with customers overloading their VPS and causing problems with the other environments, this doesn't happen with Xen. I've fork bombed child environments and caused the load to spike to over 700 until it crashed, dom0 and the rest of my domUs just kept running like nothing was even happening.
OpenVZ also wins if you want to oversell hardware, Xen doesn't have "burstable" memory like OpenVZ does. Personally I prefer Xen for the jailing that it does and you can also run multiple OSes at the same time. I have a server at work that's running CentOS, Windows 2003, Windows Longhorn, and Gentoo all at the same time, OpenVZ only lets you run Linux on Linux.
Does it run multiple instances of Linux?
The hypervisor is essentially a light-weight OS, on which the VMs are running. The hypervisor manages the underlying hardware, and provides virtualized access to the hardware, for the VMs.
Nothing like a virtualization comparison that ignores the 800 guerilla that is VMWare. How do the learning curves, performance and security of these products compare with VMWare? Why should someone who is satisfied with VMWare consider other alternatives?
the clock on the wall says 4 til 7
The article (yup, I've speed read TFA) defines Xen as a para-virtualization systems... Completely ignoring that since now years Xen also allows to do hardware-virtualization. Another posted also noted already that Xen's power lies in its ability to run different OSes.
Btw I happen to run my Samba / NFS / CVS / SVN server on a Xen para-virtualized domU. For hardware-virtualization I tried Xen too and the open, free, version lacks good I/O drivers for Windows (slow network and slow disk).
People want to Google on exactly "Which virtualization is right for you" and read infos from a knowledgable sysadmin (managing thousands of servers and virtual servers on a lot of various platforms and, no, it's not me) instead of an article performing micro-benchmarking of hypercalls to compare apples to oranges.
Here are a few talking points based on my experiences with both Xen and VMWare (ESX Server & Workstation).
1. Cost - no contest, xen wins hands down $0 vs $5000/cpu.
2. Performance - xen wins noticably, i can get away with running 8 virtual machines with 1/4 the hardware that VMWare required for 6.
3. Capabilities - VMware versions ESX GSX and up beat Xen in ease of use and flexibility, anything less and Xen wins. Xen does have a quicker live migration capability, but falls short on conencting external hardware to the virtual machine (something that is trivial in VMware).
4. Stability - about even, maybe Xen. I've seen ESX crash once, and have never seen Xen crash.
5. Ease of use - VMWare no question. Theres a learning curve to Xen and setting up new VM images is a pain. (which is disappearing) There are fantastic tools for VMware that will let you manage virtual machine creation and even migration from a physical box. (some of which can be used to feed xen too =))
The bottom line. A Xen setup (using open source version) that can easily run 12 VMs costs about $2,000 on DIY hardware. A VMWare server/software combo to do the same? about $30,000. Assume an additional 40-80 hours of learning to get up to speed with Xen vs VMware.
The comments above cover the open source / free version of Xen. I have no experience with the commercial Xen offerings.
Personally i'm Xen biased due to cost.
Linux has a lot of great VM options. VMware is a great free (cost) option, and KVM has become a great option very quickly. OpenVZ and VServer are interesting light weight OS "jail" virtualizations. They each have pros and cons, depending on your requirements and apps being used.
I'm setting up my "next generation" home linux server, and looking into the virtualization options for that. Probably a bigger factor than performance is the setup and manageability. I have found Xen to be pretty primitive compared to VMWare.. setup is a pain, documentation is spotty, and support is minimal. The one advantage of Xen is that you can (and often must) do everything with it from the command-line. The GUI tools are weak at best.
I am now leaning towards using VMWare server. But, I still need to do some testing with KVM.. articles I have read about it sound very impressive. KVM paravirtualization performance is supposed to be excellent. But, I don't know about management.
Go the FreeBSD way!
Lousy virtualization, Happy users: FreeBSD's jail(2) facility
Source: UKUUG
Tags: ukuug, presentation, freebsd, jails, poul-henning kamp
Slides (2.7 Mb)
Lousy virtualization, Happy users: FreeBSD's jail(2) facility by Poul-Henning Kamp (phk@FreeBSD.org)
bash$
OpenVZ and Virtuozzo rely upon Linux kernel modifications; in other words, no FreeBSD, no Windows.
Notes From Under *nix: blas.phemo.us
" hypervisor-level virtualization technology that allows multiple operating systems to be run with and without para-virtualization "
> I don't know about you but it still makes my eyes hurt!
Really, it's not that complex. The technology monitors all system calls, and makes a judgement call - if it's safe to let it through, it routes it through the EPS conduits. If it's not, it routes it through the GNDN tubes. As long as you don't overload the EPS taps, it's all good.
It's not always about performance; Xen gets each their separate kernel. This means that special adjustments can be made for a virtual machine. Also, with Xen you could easily experiment with an upgraded kernel for the virtual machines, without rebooting the main (host) machine. Finally, I for myself like the fact that you have your 'own' kernel. It feels much more like a real machine. Especially with a bootloader like pygrub, which is employed in RedHat AS and CentOS, the kernel inside the virtual machine can even be upgraded by yum running inside the VM.
Note that I'm not a Xen apologist, I'm not denying a performance hit here.
8 of 13 people found this answer helpful. Did you?
OpenVZ is somewhat like FreeBSD Jails. It provides some separation which makes it easier to manage multiple complex servers. For example, it makes sense to run a web server and mail server in two separate virtual machines, since it keeps the configuration independent.
Xen, is like VmWare or Qemu and provides an independent virtual machine for each system. These systems can be anything at all: Windows, Linux, BSD, whatever.
Performance wise, OpenVZ is bound to win, because it is a different solution to a different problem.
Excuse me, but please get off my Pennisetum Clandestinum, eh!
As long as the performance is not bad, I'll take isolation and ease of use over an edge in performance any day. If performance is not good enough, I'll buy a faster server. If the virtuals start disturbing each other, you won't be able to fix it easily and it might be very expensive on the long run.
I have to admit I don't have a lot of experience with Xen, and even less with OpenVZ. If I was building a server at home I would probably use Xen as it's free. At work I'm happy with VMWare ESX 3. Might be the performance is not on par with Xen (though it can't be far off), but the ease of use and management features make my job so much easier. The ability to move virtuals from one server to another without shutting them down (vmotion), easily view the state and resource usage of each virtual, high availability with clustering (one node goes down the virtuals are automatically started on another host), automatic resource balancing (one server get's overloaded, a virtual is automatically moved to an idle host without shutting it down) ect. make it the only viable choice for anything important that does not have an operator at hand 24/7.
I'm not that impressed with the free VMWare Server. While it works in most things, it has very bad disk IO performance. Especially noticeable if you create new disk files or work with snapshots while running a lot of virtuals. It's ok for development or testing, but that's it.
But which ones of these things can run Windows clients, at least XP? VMWare can, User Mode Linux can't, but what about OpenVZ, Xen, and some of the others? There are times that it's convenient to have a Windows client OS, so I can run TurboTax and other Windows applications, but mostly I'd like a real OS underneath.
Also, do any of these make USB devices visible to the client OS? Or do they all just have to network-mount resources that are actually mounted in the host OS?
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
We're using HyperVM from LxLabs http://www.lxlabs.com/ and it manages both OpenVZ and XEN. You can easily watch the performance penalties of both virtual machines from the same panel and migrate in between. So whenever someone abuses OpenVZ you can migrate it to XEN.
FWIW.
I am a big fan of Virtuozzo and OpenVZ. I just wish vzstat would be included with the free stuff.
I used to have a Virtuozzo server, but after I started noticing poor PHP performance, my hosts migrated to a Xen3 machine and I must say the speed *increase* was quite impressive, and that was running with less physical RAM allocated, and more swap, on the same spec Opteron box.
So maybe OpenVZ has some improvements over the commercial variant (seems backwards) or the article is talking about an old Xen2?
I'm currently moving onto a real hardware colo system, which is more hassle, but gives me more control.
#include <sig.h>
Then the whole article about 'compete with Xen' is bull. The computing world is bigger than GNU/Linux.
... because I actually got that joke.
Oh dear!
--I thought I was wrong once, but I was mistaken.
Let's look at what are the companies in partnership with XEN and with SWSoft (OpenVX copyright owner). HP appears only on one list.
http://www.xensource.com/partners/
http://www.swsoft.com/en/partners
I guess I have to correct you here. Xen trades off performance for an ability to run different kernels, and this has nothing to do with either isolation or security. So, Xen is good when you want to run different kernels (different OSs).
OpenVZ, on the other hand, employs a single kernel model, which makes it suitable for you if you only want to run Linux (different distros are possible, different kernels are not). But in this very field OpenVZ is way better than Xen -- not only in terms of performance, but also scalability, manageability, density, and usability.
Speaking of isolation and security, OpenVZ runs on thousands of ISP/HSP servers, and everyone can buy a VE (Virtual Environment) for about 10-15 bucks a month. There one have a root account and can try to exploit the system in all the possible ways. So far those HSPs are not out of business yet, that practically proves the system is secure and properly isolated. More to say, security comes from the constant care, and we (OpenVZ team) do care for security a lot, see this blog entry for some more details.
-- Kir Kolyshkin, OpenVZ project leader.
Just because a lumberjack doesn't know how to use his tools properly, don't blame the chainsaw because it ran out of oil and seized up
Thnaks for OpenVZ btw! It's a great product, when used correctly
Here's to the crazy ones
Performance is always a consideration when choosing a virtualization strategy, but it's rarely #1. If you want raw performance you're always going to "go native." If you want virtualization, you're always going to go for "good enough" performance that meets your primary objectives for virtualization: management, security, or an isolated need to run a non-native application. Price would be a fourth factor.
For me, I chose virtualization for an isolated need to run a non-native application. Securing the application in a sandbox was second, since it was exposed to the internet, and managing everything on one box came in third. "Free-ness" was gravy. Performance just had to be good enough that end-users didn't notice.
Here's a full summary of my experience:
http://forums.srcds.com/viewtopic/4390
My solution was to use containers, a Solaris feature turned out to be the best (and cheapest) solution to the 4-factor problem.
Now that Solaris is open-source, we'll see if containers shows up on a FOSS OS near you.