Xen Project Hypervisor: Difference between revisions

Vater (talk | contribs)
mNo edit summary
Removed fixed issue workaround
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[File:Xen-project-logo.png|thumb|The Xen Project Logo]]
[[File:Xen-project-logo.png|thumb|The Xen Project Logo]]
The '''[https://xenproject.org/ {{PAGENAME}}]''' ([[wikipedia:en:Xen]]) is an open-source type-1 virtual machine manager, which allows multiple virtual machines, known as domains, to run concurrently with the host on the physical machine. This is unlike a typical type-2 hypervisor, such as [[QEMU]], where the virtual machines run as applications on top of the host. NixOS runs as the privileged <b>Domain 0</b>, and can paravirtualise or fully virtualise Unprivileged Domains (<code>domUs</code>).
The <strong>[https://xenproject.org/ Xen Project Hypervisor]</strong> is an open-source type-1 virtual machine manager, which allows multiple virtual machines, known as domains, to run concurrently with the host on the physical machine. This is unlike a typical type-2 hypervisor, such as [[QEMU]], where the virtual machines run as applications on top of the host. NixOS runs as the privileged <b>Domain 0</b>, and can paravirtualise or fully virtualise Unprivileged Domains (<code>domUs</code>).


Xen is well-known for its [https://xenbits.xenproject.org/xsa impeccable security record], and is the go-to solution for hyper-scale cloud infrastructures.
Xen is well-known for its [https://xenbits.xenproject.org/xsa impeccable security record], and is the go-to solution for hyper-scale cloud infrastructures.
Line 72: Line 72:


If you are interested in managing Xen domains declaratively, please take a look at pull request {{pull|363388}} and everything else tagged with the <code>declarative libxenlight</code> title.
If you are interested in managing Xen domains declaratively, please take a look at pull request {{pull|363388}} and everything else tagged with the <code>declarative libxenlight</code> title.
=== Troubleshooting ===
==== <code>error: device model qemu-dm is not executable: No such file or directory</code> ====
This error follows a <code>qemu-xen is unavailable, using qemu-xen-traditional instead</code> message. This is an upstream bug in Xen, and can be fixed by pull request {{pull|365890}}, or by overriding the QEMU path in your domain configuration:
{{file|example-hvm.cfg|cfg|
<nowiki>
device_model_override='/run/current-system/sw/bin/qemu-system-i386'
</nowiki>
}}


== See also ==
== See also ==