Dom0 Disaggregation: Difference between revisions
ToddDeshane (talk | contribs) (add more references) |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
==Dom0 |
==Dom0 Disaggregation== |
||
The [[Dom0]] or control domain has traditionally been a monolithic privileged virtual machine. However, the original intention was for Dom0 to be carefully broken into several privileged service domains - termed Dom0 disaggregation. Qubes OS, Citrix XenClient, and Xoar have made the case for more disaggregation of Dom0 for purposes of better security, reliablity, isolation, and auditability. |
The [[Dom0]] or control domain has traditionally been a monolithic privileged virtual machine. However, the original intention was for Dom0 to be carefully broken into several privileged service domains - termed Dom0 disaggregation. Qubes OS, OpenXT, Citrix XenClient, and Xoar have made the case for more disaggregation of Dom0 for purposes of better security, reliablity, isolation, and auditability. |
||
[[File:Xoar_architecture.jpg|800px]] |
[[File:Xoar_architecture.jpg|800px]] |
||
==In Practice== |
|||
The OpenXT project, derived from the original Citrix product XenClient XT, offers a disaggregated networking stack and isolated network driver domains. |
|||
Qubes OS is similarly pursuing a disaggregated architecture for a desktop system. |
|||
The Citrix XenServer organization has made steps towards disaggregation, with the Windsor architecture project. |
|||
"Although domain 0 disaggregation is not new it is seldom used in practise and much of its use is focussed on providing enhanced security. Citrix XenServer will be moving towards a disaggregated domain 0 in order to provide better security, scalability, performance, reliability, supportability and flexibility." |
|||
Project “Windsor”: Domain 0 Disaggregation for XenServerXCP: |
|||
* http://www.xen.org/xensummit/xs12na_talks/T2.html |
|||
A more recent update indicates that the Windsor project is now viewed more as technology development than productization: |
|||
* http://xenserver.org/discuss-virtualization/virtualization-blog/entry/whatever-happened-to-xenserver-s-windsor-architecture.html |
|||
==References== |
==References== |
||
* http://openxt.org |
|||
* http://qubes-os.org/Home.html |
* http://qubes-os.org/Home.html |
||
* http://www.cs.ubc.ca/~andy/papers/xoar-sosp-final.pdf |
* http://www.cs.ubc.ca/~andy/papers/xoar-sosp-final.pdf |
||
Latest revision as of 18:58, 17 August 2016
Dom0 Disaggregation
The Dom0 or control domain has traditionally been a monolithic privileged virtual machine. However, the original intention was for Dom0 to be carefully broken into several privileged service domains - termed Dom0 disaggregation. Qubes OS, OpenXT, Citrix XenClient, and Xoar have made the case for more disaggregation of Dom0 for purposes of better security, reliablity, isolation, and auditability.
In Practice
The OpenXT project, derived from the original Citrix product XenClient XT, offers a disaggregated networking stack and isolated network driver domains.
Qubes OS is similarly pursuing a disaggregated architecture for a desktop system.
The Citrix XenServer organization has made steps towards disaggregation, with the Windsor architecture project.
"Although domain 0 disaggregation is not new it is seldom used in practise and much of its use is focussed on providing enhanced security. Citrix XenServer will be moving towards a disaggregated domain 0 in order to provide better security, scalability, performance, reliability, supportability and flexibility."
Project “Windsor”: Domain 0 Disaggregation for XenServerXCP:
A more recent update indicates that the Windsor project is now viewed more as technology development than productization:
