Attention, Attention, Attention. The Xen Summit Program Committee for the Boston event in June (23 – 24) is busy reviewing submitted topics and is waiting for your proposal. We are actively putting together the agenda and would like nothing more than to have you as a speaker. This is your chance to promote yourself and your work to the Xen.org community. To assist us, we are asking all interested speakers to submit their topics early this year so we can create the best possible event without having any last minute submissions which may get missed as many Xen Program Committee members will be taking vacation early this summer. Please submit your topics to email@example.com and I will ensure the Program Committee receives it for a timely review.
I have added a few new Blogroll links to other people who have active blogs on the Xen hypervisor. Please take some time to visit their blogs for interesting information:
- Ian C Blenke – http://ian.blenke.com/xen/
- Kris Buytaert – http://www.krisbuytaert.be/blog/taxonomy/term/470
- Muli Ben-Yehuda – http://mulix.livejournal.com/
- Raska’s Blog – http://www.raskas.be/blog/category/linux-sysadmin/xen/
When I first started working in the Xen community, I purchased the David Chisnall book about Xen to learn more. I received a link from the publisher to showcase a chapter from the book. Click here to read Chapter 6, Understanding Device Drivers. For more information on this book you can visit the publishers site here.
Quote from Simon Crosby on this book:
â€œThe Xen hypervisor has become an incredibly strategic resource for the industry, as the focal point of innovation in cross-platform virtualization technology. Davidâ€™s book will play a key role in helping the Xen community and ecosystem to grow.â€
David also has a recent posting on the HURD kernel worth reading for those with an interest in OS history.
(Note: I will be promoting other Xen books over time to ensure that all authors writing Xen books get publicity within the community)
It’s a question many will ask at some point. You’ve got Xen set up, used a graphical tool to configure some domUs (or downloaded some pre-built images, or followed a howto). But now you want to know where your virtual machines are actually stored. It’s a good question – and it has a slightly complicated answer.
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:
- Isolation of Shared Network Resources in XenoServers (Nov 2002)
- Controlling the XenoServer Open Platform (Nov 2002)
- Xenoservers: Accountable Execution of Untrusted Code
- The XenoService â€“ a Distributed Defeat for Distributed Denial of Service
- Safe Hardware Access with the Xen Virtual Machine Monitor
- Denali Project at University of Washington
- Paper: Denali: Lightweight Virtual Machines for Distributed and Networked Application (denali-lightweight-virtual-machines.pdf)
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.