Xen is a free software virtual machine monitor for IA-32, x86-64, IA-64 and PowerPC 970 architectures. It allows several guest operating systems to be executed on the same computer hardware at the same time.A Xen system is structured with the Xen hypervisor as the lowest and most privileged layer . Above this layer are one or more guest operating systems, which the hypervisor schedules across the physical CPUs. The first guest operating system, called in Xen terminology domain 0 (dom0), is booted automatically when the hypervisor boots and given special management privileges and direct access to the physical hardware. The system administrator logs into dom0 in order to start any further guest operating systems, called domain U (domU) in Xen terminology. Modified versions of Linux, NetBSD and Solaris can be used as the dom0. Several modified Unix-like operating systems may be employed as guest operating systems (domU); on certain hardware, as of Xen version 3.0, unmodified versions of Microsoft Windows and other proprietary operating systems can also be used as guests if the CPU supports VT technology. Xen originated as a research project at the University of Cambridge, led by Ian Pratt, senior lecturer at Cambridge and founder of XenSource, Inc. This company now supports the development of the open source project and also sells enterprise versions of the software. The first public release of Xen was made available in 2003. XenSource, Inc was acquired by Citrix Systems in October 2007. XenSource's products have subsequently been renamed under the Citrix brand: XenExpress was renamed XenServer Express Edition and XenServer OEM Edition (embedded hypervisor); XenServer was renamed XenServer Standard Edition; XenEnterprise was renamed XenServer Enterprise Edition.On 2007-10-22, Citrix Systems completed its acquisition of XenSource, and the Xen project moved to http://www.xen.org. This move had been under way for some time, and afforded the project an opportunity to make public the existence of the Xen Project Advisory Board (Xen AB), which currently has members from Citrix, IBM, Intel, Hewlett-Packard, Novell, Red Hat and Sun Microsystems. The Xen AB is chartered with oversight of the project's code management procedures, and with development of a new trademark policy for the Xen mark, which Citrix intends to freely license to all vendors and projects that implement the Xen hypervisor; the requirements for licensing will be solely the responsibility of the Xen AB. [edit]
Xen is a free software virtual machine monitor for IA-32, x86-64, IA-64 and PowerPC 970 ar...
| OStatic Users | 2 |
| Stories | 7 |
| Questions | 1 |
Share a valuable story about this application with the OStatic Community.
I played around with OpenVZ as well as Xen, to decide which one I would use for a virtualization project for my company. I ended up choosing Xen as the clear winner. There are some benchmarks out on the web which show OpenVZ has a very slight performance benefit over Xen. However, the performance benefit appears to be negligible in most circumstances, and I found Xen much more user friendly. Xen is much more manageable, and makes it easy to save a copy of a virtual machine. It also provides mechanisms for moving a virtual machine to another host running Xen in realtime, with the virtual machine taking a "hit" for only a few milliseconds. I did not test this functionality, but just illustrates how more mature the Xen project is over OpenVZ.
Having said that, OpenVZ does provide some things Xen does not provide. It allows "over subsubscribing" system resources such as memory, and allows more finely tuned tweaking than Xen provides. Also, if you are familiar with Zones in Solaris, you'll feel more at home with OpenVZ than with Xen.