The final installment of the History of Xen – Architecture involves the ultimate question, where does the name “Xen” come from? It is clear that Xen comes from the XenoServer project at Cambridge which is the research that the Xen hypervisor emerged from. The name “Xeno” for the XenoServer project is specifically mentioned in the Controlling the XenoServer Open Platform (Nov 2002) as footnote1:
The name derives from the Greek word “”o&” (xenos), which means
foreign or unknown, much like the tasks that XenoServers accept and safely
So, the name Xen comes from XenoServer with a Greek origin; but who was the first person to claim the name “Xen”? If anyone knows or wants to make the claim, here is your chance.
In reading the two documents posted in Part 2, I discovered even more interesting work that was done previously. I think we are now getting close to the earliest research from which the open source Xen project was created. For your reading pleasure:
If you are limited in time, I highly recommend the Safe Hardware Access with the Xen Virtual Machine Monitor paper as it does an excellent job of detailing of a device driver is run in isolation for the Xen hypervisor system.
As stated earlier in my first History of Xen – Architecture post, I am on the active trail of the history of Xen and will continue to publish documents and information to help give the community a complete history of the project from idea to development to open source solution. I have two more interesting documents from the University of Cambridge that were created before the Xen and the Art of Virtualization paper was published. Enjoy.
The Xenoserver Computing Infrastructure : Technical Report #552
Xen 2002 : Technical Report #553
As I continue to learn more about Xen, I find it interesting to read old documents that show the transformation of Xen from a research project at Cambridge University to the current leading open source hypervisor technology. A great link form Cambridge University is available with a collection of documents and presentations. I would like to highlight two documents that I found worth reading: