summaryrefslogtreecommitdiff
path: root/kernels/xen/xen.install
diff options
context:
space:
mode:
authorAndré Fabian Silva Delgado <emulatorman@parabola.nu>2015-04-10 06:00:25 -0300
committerAndré Fabian Silva Delgado <emulatorman@parabola.nu>2015-04-10 06:00:25 -0300
commitf47c84c7843829edd571e1e0c511c8bd60c65973 (patch)
treee528dd883257fc056628e6b6893d0443531ff95d /kernels/xen/xen.install
parent1cba3813bf3ffc2988b0b343fc2f38863f54aef4 (diff)
xen-4.5.0-1.parabola1: updating version
Diffstat (limited to 'kernels/xen/xen.install')
-rw-r--r--kernels/xen/xen.install45
1 files changed, 30 insertions, 15 deletions
diff --git a/kernels/xen/xen.install b/kernels/xen/xen.install
index d25d3a93d..173e6437f 100644
--- a/kernels/xen/xen.install
+++ b/kernels/xen/xen.install
@@ -4,17 +4,27 @@ install_msg() {
In order to complete the installation, and enable Xen,
at the very least you must:
-1. Edit your GRUB2 config files as specified at
- https://wiki.parabolagnulinux.org/index.php/Xen#Bootloader_Configuration
-2. Issue the following commands to allow you to create and start VMs:
- systemctl enable xenstored.service
+1. If using GRUB2, edit your GRUB2 config files as specified at
+ https://wiki.parabola.nu/index.php/Xen#Bootloader_Configuration
+
+ Support for the grub-mkconfig command was added, and will auto-discover
+ the deployed xen hypervisor and linux kernel
+2. If booting via efi, copy the example /etc/xen/efi-xen.cfg to /boot/xen.cfg
+ and edit the contents to match the settings you need.
+3. Issue the following commands to allow you to create and start VMs:
+
+ systemctl enable xen-qemu-dom0-disk-backend.service
+ systemctl enable xen-init-dom0.service
systemctl enable xenconsoled.service
-3. If you want some domains to automatically start up/shutdown, run the following:
+
+ Other optional services are:
+ systemctl enable xen-watchdog.service
+
+4. If you want some domains to automatically start up/shutdown, run the following:
systemctl enable xendomains.service
-4. xen 4.4 no longer includes the xend daemon or the xm binary
For more information refer to the Wiki:
- https://wiki.parabolagnulinux.org/index.php/Xen
+ https://wiki.parabola.nu/index.php/Xen
__EOF__
@@ -25,15 +35,16 @@ upgrade_msg() {
Note: If you are upgrading from one of the previous 4.2 xen builds, and are having issues
with graphics card passthrough, the default device model used has changed and the
- newer model can sometimes have issues. To resolve, add (or change ) the following
- line into your domain config file:
+ newer model can sometimes have issues. To work around these issue, support for the
+ old style qemu-xen-traditional device model has been enabled. To use, add (or change)
+ the following line into the configuration file for the domain you want to use
+ passthrough with:
device_model_version = "qemu-xen-traditional"
- Also remember to rebuild your grub configuration if upgrading from a non-xen 4.4.1
- install.
+ Also remember to rebuild your grub configuration if upgrading from a non-xen 4.5.0
+ install.
- xen 4.4 no longer includes the xend daemon or the xm toolset by default, however
- this build does enable it.
+ The xend daemon and the xm toolset have now been removed with the xen 4.5 release.
This install is now using a new version of the 09_xen file, used when generating
a new grub.cfg file. The new version inherits the default linux-libre kernel command
@@ -54,12 +65,16 @@ post_upgrade() {
pre_remove() {
systemctl stop xendomains.service
+ systemctl stop xen-watchdog.service
systemctl stop xenconsoled.service
- systemctl stop xenstored.service
+ systemctl stop xen-init-dom0.service
+ systemctl stop xen-qemu-dom0-disk-backend.service
systemctl disable xendomains.service
+ systemctl disable xen-watchdog.service
systemctl disable xenconsoled.service
- systemctl disable xenstored.service
+ systemctl disable xen-init-dom0.service
+ systemctl disable xen-qemu-dom0-disk-backend.service
}
post_remove() {