Difference between revisions of "Dom0"

From Xen
(Merge stuff from Dom0_Kernels_for_Xen)
(initial sentence split. Added overview link (beginners will view this page))
 
(3 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Dom0, or domain zero to expand the abbreviation, is the first [[domain]] started by the Xen [[hypervisor]] on boot. The Xen hypervisor is not usable without Domain-0 ("dom0").
+
[[Dom0]] is the initial [[domain]] started by the Xen [[hypervisor]] on boot. Dom0 is an abbrevation of "Domain 0" (sometimes written as "domain zero" or the "host domain"). Dom0 is a privileged domain that starts first and manages the [[DomU]] unprivileged domains.
   
The dom0 is essentially the "host" operating system (or a "service console", if you prefer). As a result, it runs the Xen management toolstack, and has special privileges, like being able to access the hardware directly.
+
The Xen [[hypervisor]] is not usable without Dom0. This is essentially the "host" operating system (or a "service console", if you prefer). As a result, Dom0 runs the Xen management toolstack, and has special privileges, like being able to access the hardware directly.
   
It also has drivers for hardware, and it provides Xen virtual disks and network access for other guests aka domUs (unprivileged domains). For hardware that is made available to other domains, like network interfaces and disks, it will run the [[BackendDriver]], which multiplexes and forwards to the hardware requests from the [[FrontendDriver]] in each [[DomU]].
+
Dom0 has drivers for hardware, and it provides Xen virtual disks and network access for guests each referred to as a domU (unprivileged domains). For hardware that is made available to other domains, like network interfaces and disks, it will run the [[BackendDriver]], which multiplexes and forwards to the hardware requests from the [[FrontendDriver]] in each [[DomU]].
   
Unless [[DriverDomain]]'s are being used or the hardware is passed through to the domU, the dom0 is responsible for running all of the device drivers for the hardware.
+
Unless [[DriverDomain]]'s are being used or the hardware is passed through to the [[domU]], the dom0 is responsible for running all of the device drivers for the hardware.
   
 
== Also See ==
 
== Also See ==
  +
  +
* [[Xen Project Software Overview]]
 
* [[Dom0 Kernels for Xen]] : Supported Kernels for Dom0
 
* [[Dom0 Kernels for Xen]] : Supported Kernels for Dom0
   
Line 14: Line 16:
 
* NetBSD -- http://www.netbsd.org/ports/xen/howto.html#netbsd-dom0
 
* NetBSD -- http://www.netbsd.org/ports/xen/howto.html#netbsd-dom0
 
* [[OpenSolaris]] -- http://www.opensolaris.org/os/community/xen/docs/SetupDom0.htm
 
* [[OpenSolaris]] -- http://www.opensolaris.org/os/community/xen/docs/SetupDom0.htm
  +
  +
[[Category:Xen]]
  +
[[Category:Users]]
  +
[[Category:Beginners]]
  +
[[Category:Overview]]

Latest revision as of 11:36, 29 March 2015

Dom0 is the initial domain started by the Xen hypervisor on boot. Dom0 is an abbrevation of "Domain 0" (sometimes written as "domain zero" or the "host domain"). Dom0 is a privileged domain that starts first and manages the DomU unprivileged domains.

The Xen hypervisor is not usable without Dom0. This is essentially the "host" operating system (or a "service console", if you prefer). As a result, Dom0 runs the Xen management toolstack, and has special privileges, like being able to access the hardware directly.

Dom0 has drivers for hardware, and it provides Xen virtual disks and network access for guests each referred to as a domU (unprivileged domains). For hardware that is made available to other domains, like network interfaces and disks, it will run the BackendDriver, which multiplexes and forwards to the hardware requests from the FrontendDriver in each DomU.

Unless DriverDomain's are being used or the hardware is passed through to the domU, the dom0 is responsible for running all of the device drivers for the hardware.

Also See

Most commonly dom0 runs some variant of Linux, but Xen dom0 implementations also exist for OpenSolaris and NetBSD. Modified versions of Linux, NetBSD and Solaris can be used as the dom0. See OS vendor documentation for specific steps. Current official documentation may be found at the following sites: