Join the Xen Project Advisory Board

The Xen Project Advisory Board is comprised of companies who are committed to the market and technical success of the Xen Project.  Member companies provide financial support, technical contributions, and set high-level policy decisions.

The Xen Project Advisory Board's responsibilities include:

  • Financial Oversight, such as budget management and investment decisions on infrastructure and project operations.
  • Membership requirements, including annual membership fees.
  • Steer the project to advance its market and technical success by raising awareness and garnering broader industry support for Xen through individual and collaborative efforts.
  • Global policy decisions, including trademarks, compliance requirements, and test cases and infrastructure.

The Xen Project Advisory Board is complementary to the role of committers and maintainers within the Xen Project, with both working closely together to ensure the overall priorities of the project are aligned.  Committers and maintainers are responsible for technical development of the project, and are the final decision makers on code contributions to the Xen Project.  

Improve your engineering ROI

The Xen Project is in the process of creating a new common test infrastructure.  New test cases for specific hardware and software combinations will lead to higher quality project releases.  In addition, a planned focus on a security and hardening framework will enhance the release readiness of the Xen Project.

The Xen Project Advisory Board will be responsible for defining test cases and prioritizing release requirements, in cooperation with Xen Project maintainers.  Members will see increased engineering ROI thanks to increased focus on the test cases the Xen Project Advisory Board members prioritize.

Insight and input into Xen Project planning

Xen Project Advisory Board members can propose and vote upon changes and additions to Xen Project test and validation infrastructure.  Members will also vote on requests to allocate financial resources to Xen Project Sub-Projects.

In addition, Xen Project Advisory Board members will gain valuable strategic insight into project plans and future scope.  By virtue of being an active Xen Project Advisory Board participant, members will have regular opportunities for discussions with technical leaders within the Xen Project.  Working in conjunction with technical leaders, they will have the opportunity to share technical and marketing priorities, and endorse new strategies for the project.

Xen Project Advisory Board members will gain valuable insight into the multi-year strategic direction of the project, and help protect the durability of their investments in Xen Project.

Increase your visibility

Xen Project Advisory Board members have the option to participate in press releases, include logos on banners, websites, and giveaways at Xen events, and influence the Xen Project marketing strategy.

Support the ongoing neutrality of the Xen Project

Xen Project Advisory Board membership dues fund non-technical project support.  Members are collectively reponsible for defining policies, including trademark usage and approvals, compliance and certification of Xen derivatives, and branding and style guidelines.  In addition, membership dues  fund project infrastructure, such as hosting and test environments.

The Xen Project Advisory Board process will help ensure non-technical decisions are collectively determined by members as a whole.  In this way, the Advisory Board contributes a sustainable, self-directed source of funding for work that will help drive the marketplace and technical success of the Xen Project.

Joining the Xen Project Advisory Board

To learn more about joining the Xen Project Advisory Board, organizations must sign the Xen Project Advisory Board Membership Application and join the Linux Foundation as a member.  To get started, please fill out this form and someone will contact you within two days.


Projects, Products and Services for the Xen Project Hypervisor

The pages in this section are community and vendor maintained. Only vendors who submit listings have been added to the pages in this section.  As a result, some pages may not be complete if the vendor responsible chose not to complete the form. If you are an open source project, vendor or individual and want to be added to one of the pages, please feel free to add your information to the listings in this directory.

Click here to enter the Ecosystem Directory.

Contact Us

For development questions, please begin by asking on the mailing lists or IRC.  These are generally the fastest ways to get an answer.

For questions related to using the Xen Project, please ask on one of our user lists or in or Q&A system.

Learn more about joining the Xen Project Advisory Board here.

For all other questions, please fill out this form and someone will get back to you within two business days.




Late 1990s

The Xen hypervisor was first created by Keir Fraser and Ian Pratt as part of the Xenoserver research project at Cambridge University in the late 1990s. A hypervisor "forms the core of each Xenoserver node, providing the resource management, accounting and auditing that we require." The earliest web page dedicated to the Xen hypervisor is still available on Cambridge web servers.  The early Xen history can easily be traced through a variety of academic papers from Cambridge University. Controlling the XenoServer Open Platform is an excellent place to begin in understanding the origins of the Xen hypervisor and the XenoServer project. Other relevant research papers can be found at:

Over the years, the Xen community has hosted several Xen Summit events where the global development community meets to discuss all things Xen. Many presentations and videos of those events are available here.


The Xen hypervisor was open sourced to allow a global community of developers to contribute and improve the product.


The first public release of Xen is announced at the USENIX Operating Systems Design and Implementation conference in the fall.  We regard this as the "birthday" of Xen.


Xen 1.0 was officially released followed a short time later by Xen 2.0. At the same time, Ian Pratt and several other technology leaders founded XenSource, Inc. to convert the Xen hypervisor from a research tool into a competitive product for enterprise computing. As part of the corporate strategy, the Xen hypervisor remained an open source solution.


Widespread adoption of the Xen hypervisor took place when Red Hat, Novell, and Sun all added the Xen hypervisor as their virtualization solution of choice. The development community also accelereted the capabilities of Xen with the Xen 3.0 release.


Microsoft and VMWare adopted the concept of Paravirtualization, first introduced by the Xen community.


Citrix Systems, Inc. acquired XenServer in August for $500 million.
“This announcement represents a key milestone for the Xen project,” said Ian Pratt, leader of the Xen project and co-founder of XenSource. “Citrix is committed to our community and the principles of transparency and neutrality that allow us to work together on the reference standard for virtualization, promoting the rapid, ubiquitous adoption of virtualization.”


The Xen ARM project is created by Samsung Electronics.


The Xen community announced a new initative for Cloud Computing, Xen Cloud Platform.


The Xen community releases Xen 4.0.  In early 2010, a community contest was held to create the Xen mascot. The official mascot was launched in June 2010.


Linux 2.6.37, is the first upstream Linux kernel that canboot on Xen as Dom0 out-of-the-box.

The Xen community delivered the first version of the Xen Cloud Platform.

Linux 3.x, contains full support for Xen Dom0 and DomU. Major Linux distributions announce that they will re-introduce Xen into their distributions.

Project Kronos is created to deliver XCP supporting Debian and Ubuntu as Dom0, as well is being distributed via Linux distributions.

First Xen prototype for XenARM using Cortex A15 is announced.


The Xen Cloud Platform packages for Linux are released.


The Xen ARM port becomes functional.

Xen becomes part of the Linux Foundation as a Linux Foundation Collaborative Project.  The community website is transitioned from to a more modern website at, and the new trademark "Xen Project" is issued to the Linux Foundation.

The first truly user-centric event is held, called the Xen Project User Summit.


The number of Advisory Board members expands.

Mirage OS 2.0 is released.


Sed vitae nulla sed lectus bibendum feugiat vitae non lorem. Pellentesque vestibulum nisi ut lorem laoreet tincidunt. Sed quis scelerisque orci. Fusce sit amet nulla in quam aliquet blandit vitae sed risus.

Integer sagittis magna ut urna eleifend posuere. In hac habitasse platea dictumst. Quisque sed lorem nec velit blandit accumsan sed nec massa. Duis placerat pretium tempus. Sed sed lacus a tortor imperdiet iaculis. Donec molestie, felis eu tristique blandit, nunc ante sollicitudin turpis, id sagittis lectus enim vel mi. Fusce quis erat ut massa posuere mollis id vel turpis.

Suspendisse lobortis consectetur libero eu molestie. Nulla arcu tortor, tincidunt et ultricies ut, elementum sit amet magna. Duis ullamcorper, turpis at aliquet feugiat, ipsum arcu consectetur nunc, id suscipit nisl mi vel massa. Fusce cursus ornare odio sed posuere. Etiam semper sagittis mi, et pretium neque mollis sed. Suspendisse a libero elit, convallis lacinia nibh. Duis nunc elit, faucibus quis laoreet ac, euismod vel diam. Suspendisse ac aliquet sem. Nunc cursus dictum auctor. Aenean consectetur, leo at euismod placerat, lorem diam pharetra sapien, ut sagittis libero eros sit amet ante. Phasellus rutrum erat sed sem scelerisque sodales. Mauris facilisis molestie ullamcorper. Nulla porttitor tempus elit sit amet luctus. Cras et varius nisi. Vivamus ac elit sapien.