Dom0 Disaggregation: Difference between revisions
From Xen
Jump to navigationJump to search
ToddDeshane (talk | contribs) (add initial page) |
ToddDeshane (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
==Dom0 Dissaggregation== |
==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 |
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. |
||
[[File:Xoar_architecture.jpg|800px]] |
[[File:Xoar_architecture.jpg|800px]] |
||
Revision as of 20:04, 24 January 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.
