DomU: Difference between revisions
From Xen
Jump to navigationJump to search
(Created page with "<!-- MoinMoin name: DomU --> <!-- Comment: --> <!-- WikiMedia name: DomU --> <!-- Page revision: 00000003 --> <!-- Original date: Sat Aug 11 20:13:11 2007 (11868631910…") |
mNo edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| 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 |
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 <xen-config-filename> |
|||
</pre> |
|||
in Dom0. The kernel for a DomU comes from Dom0's filesystem, not from the filesystem exported to the DomU. |
|||
== |
== Also see == |
||
* [[DomU Support for Xen]] : List of supported operation systems |
* [[DomU Support for Xen]] : List of supported operation systems |
||
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
- DomU Support for Xen : List of supported operation systems
