Xen Project Hypervisor: Difference between revisions

(10 intermediate revisions by 2 users not shown)

Line 16:

After a successful reboot, you should now be using a Xen ~~EFI~~ kernel, and Xen's usual commands, such as <code>xl</code>, will begin working. Right after a fresh boot, there's usually only a single domain (virtual machine) running: the Domain 0.

After a successful reboot, you should now be using a Xen kernel, and Xen's usual commands, such as <code>xl</code>, will begin working. Right after a fresh boot, there's usually only a single domain (virtual machine) running: the Domain 0.

=== About the Domain 0 ===

Line 69:

You can then start the domain using the following command:

~~{{Commands|~~# xl create /path/to/example-hvm.cfg -Fc}}

# xl create /path/to/example-hvm.cfg -Fc

</syntaxhighlight>

If you are interested in managing Xen domains declaratively, please take a look at pull request {{pull|363388}} and everything else tagged with the ~~`declarative libxenlight` 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_version='qemu_xen'~~

~~device_model_override='/run/current-system/sw/bin/qemu-system-i386'~~

~~</nowiki>~~

}}

== See also ==

@@ Line 16: / Line 16: @@
 {{Evaluate|boot}}
-After a successful reboot, you should now be using a Xen EFI kernel, and Xen's usual commands, such as <code>xl</code>, will begin working. Right after a fresh boot, there's usually only a single domain (virtual machine) running: the Domain 0.
+After a successful reboot, you should now be using a Xen kernel, and Xen's usual commands, such as <code>xl</code>, will begin working. Right after a fresh boot, there's usually only a single domain (virtual machine) running: the Domain 0.
 === About the Domain 0 ===
@@ Line 69: / Line 69: @@
 You can then start the domain using the following command:
-{{Commands|# xl create /path/to/example-hvm.cfg -Fc}}
+<syntaxhighlight lang=console>
+# xl create /path/to/example-hvm.cfg -Fc
+</syntaxhighlight>
-If you are interested in managing Xen domains declaratively, please take a look at pull request {{pull|363388}} and everything else tagged with the `declarative libxenlight` 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_version='qemu_xen'
-device_model_override='/run/current-system/sw/bin/qemu-system-i386'
-</nowiki>
-}}
 == See also ==