Difference between revisions of "DomU"

From Xen
m (Updated to use xl, not xend.)
Line 6: Line 6:
   
 
__NOTOC__
 
__NOTOC__
A DomU is the counterpart to [[Dom0]]; it is an unprivileged [[domain]] with (by default) no access to the hardware. It must run a [[FrontendDriver]] for multiplexed hardware it wishes to share with other domains. A DomU is started by xend in Dom0, which the user accesses with the xm command-line tool. The kernel for a DomU comes from Dom0's filesystem, not from the filesystem exported to the DomU.
+
A DomU is the counterpart to [[Dom0]]; it is an unprivileged [[domain]] with (by default) no access to the hardware. It must run a [[FrontendDriver]] for multiplexed hardware it wishes to share with other domains. A DomU is started by running
  +
<pre>
  +
xl create
  +
</pre>
  +
in Dom0. The kernel for a DomU comes from Dom0's filesystem, not from the filesystem exported to the DomU.
   
 
== Also see ==
 
== Also see ==

Revision as of 13:58, 30 July 2012


A DomU is the counterpart to Dom0; it is an unprivileged domain with (by default) no access to the hardware. It must run a FrontendDriver for multiplexed hardware it wishes to share with other domains. A DomU is started by running

xl create

in Dom0. The kernel for a DomU comes from Dom0's filesystem, not from the filesystem exported to the DomU.

Also see