Dom0 Disaggregation: Difference between revisions
From Xen
Jump to navigationJump to search
Lars.kurth (talk | contribs) m (Added categories) |
ToddDeshane (talk | contribs) (add references) |
||
| Line 2: | Line 2: | ||
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, Citrix XenClient, and Xoar have made the case for more disaggregation of Dom0 for purposes of better security, reliablity, isolation, and auditability. |
||
==References== |
|||
* http://qubes-os.org/Home.html |
|||
* http://www.cs.ubc.ca/~andy/papers/xoar-sosp-final.pdf |
|||
[[File:Xoar_architecture.jpg|800px]] |
[[File:Xoar_architecture.jpg|800px]] |
||
Revision as of 16:43, 6 April 2012
Dom0 Dissaggregation
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.
References
