Difference between revisions of "DomU"

From Xen
m (Updated to use xl, not xend.)
m
 
Line 8: Line 8:
 
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
 
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>
 
<pre>
xl create
+
xl create &lt;xen-config-filename&gt;
 
</pre>
 
</pre>
 
in Dom0. The kernel for a DomU comes from Dom0's filesystem, not from the filesystem exported to the DomU.
 
in Dom0. The kernel for a DomU comes from Dom0's filesystem, not from the filesystem exported to the DomU.

Latest revision as of 14:35, 10 September 2013


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 <xen-config-filename>

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

Also see