Difference between revisions of "Xen Dom0"

From Alpine Linux
Jump to: navigation, search
(add See also)
(18 intermediate revisions by 12 users not shown)
Line 1: Line 1:
So before anything else verify that you can '''reliably''' log into your Alpine box through [[Setting_up_a_ssh-server|SSH]], because with some video chipset (intel in my case) xen will blank your screen so you will have to use SSH.
+
This guide will show you how to have your 'sys' install of Alpine run as a Xen Dom0. You can start either from an existing standard install or install a new copy of Alpine with the Alpine Xen ISO.
  
Then upgrade your setup to [[Upgrading_to_Edge|Edge/testing]] (as of the date of writing, Xen is only available in Edge). Install Xen:
+
== Install Xen ==
 +
=== New installation ===
 +
==== Writing the medium ====
 +
{{Warning|This will erase '''everything''' on the drive you point it at. Check and double check that <code>/dev/sdx</code> is the correct USB device you want to write to, using the commands <code>lsblk</code> and <code>blkid</code>.}}
 +
First download Alpine's [https://www.alpinelinux.org/downloads/ Xen install ISO], and either [[Burning ISOs|burn the ISO to a CD/DVD]] or write it to a USB storage device with the following command, where <code>3.12.0</code> should be replaced with the release number of your downloaded ISO and <code>/dev/sdx</code> should be replaced with the drive letter of your USB:
 +
<pre>dd if=alpine-xen-3.12.0-x86_64.iso of=/dev/sdx</pre>
  
{{Cmd|apk add xen}}
+
==== Installation ====
 +
Now boot from your CD or USB, and type 'root' when prompted for a username. After you have logged in run <code>setup-xen-dom0</code>, then continue with a standard [[Install to disk|Alpine installation]] until you get to the prompt asking to choose your network card.
 +
What you'll want to do is select what is to be your internet-facing interface, and when asked to bridge it type 'yes'. Then you can configure the networking settings of your bridge device, <code>br0</code>, as you would have configured your internet-facing interface.
 +
{{Note|You cannot bridge a WiFi interface in the automatic installation script due to incompatible protocols. Make sure you pick an ethernet interface for this.}}
 +
Now continue with your installation to disk until you reach the 'reboot' prompt. There are a few more things to do before you can boot without errors:
 +
<pre>
 +
# xen-hypervisor isn't installed by default with Xen so we must install it manually
 +
apk add xen-hypervisor
 +
apk add bridge
 +
</pre>
 +
 
 +
Now you can safely reboot after removing your install medium, making sure to pick the <code>Alpine Linux v3.12, with Xen 4.13.1 and Linux lts</code> boot option in your GRUB menu, with 3.12 and 4.13.1 replaced with your Linux and Xen version numbers, respectively.
 +
 
 +
After this, [[Enable Community Repository|enable the Alpine community repository]] and install the firmware to be used for Xen's virtual machines:
 +
<pre>
 +
apk add seabios ovmf
 +
</pre>
 +
 
 +
Now you are ready to configure GRUB.
  
Modify your extlinux.cfg (credits: http://lists.alpinelinux.org/alpine-devel/1406.html)
+
=== Existing installation ===
since video card is not working for now, we will use a serial console:
+
First you must [[Enable Community Repository|enable the Alpine community repository]], then install Xen and the seabios (BIOS) and ovmf (UEFI) firmwares for its virtual machines.
  
 
<pre>
 
<pre>
SERIAL 0 115200
+
# apk add xen xen-hypervisor seabios ovmf
DEFAULT menu.c32
+
</pre>
PROMPT 0
+
 
MENU TITLE Alpine/Linux Boot Menu
+
This will install Xen Hypervisor, xl cli command and all the required packages. The next step is to modify your GRUB configuration to properly boot Xen.
MENU HIDDEN
 
MENU AUTOBOOT Alpine will be booted automatically in # seconds.
 
TIMEOUT 50
 
  
LABEL 0
+
The next step is to load the necessary kernel modules for Xen, we will add them to /etc/modules, so they will be loaded automatically on boot:
  MENU LABEL XEN
+
<pre>echo "xen-netback" >> /etc/modules
  KERNEL mboot.c32
+
echo "xen-blkback" >> /etc/modules
  APPEND /boot/xen-4.gz iommu=1 dom0_mem=1024M dom0_max_vcpus=2 dom0_vcpus_pin  loglvl=all guest_loglvl=all com1=115200,8n1 console=com1  --- /boot/grsec root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=ext4 console=hvc0 earlyprintk=xen nomodeset --- /boot/grsec.gz
+
echo "tun" >> /etc/modules</pre>
 +
Then lastly we add the Xen daemons to the default runlevel.
 +
<pre>rc-update add xenconsoled
 +
rc-update add xendomains
 +
rc-update add xenqemu
 +
rc-update add xenstored</pre>
 +
Now reboot.
  
LABEL 1
+
== GRUB configuration ==
  MENU LABEL Linux
+
Once running a Xen kernel we will need to edit its command-line options and enable the setting of a default GRUB entry by inserting this at the bottom of <code>/etc/default/grub</code>:
  KERNEL grsec
+
{{Cat|/etc/default/grub|<nowiki># We need to set the amount of RAM we allocate to our Dom0 Alpine install so that
  APPEND initrd=grsec.gz root=UUID=f40e340b-ea49-445b-81c0-4d7104b56662 modules=ext4
+
# our future virtual machines are left with enough memory.
 +
GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M"
  
 +
GRUB_DEFAULT="saved"
 +
GRUB_SAVEDEFAULT="true"</nowiki>}}
 +
You can replace 1024M with the amount of memory you want to allocate to your Dom0 operating system.
 +
After this you need to run the following:
 +
<pre>grub-mkconfig -o /boot/grub/grub.cfg
 +
grub-set-default "$(grep ^menuentry /boot/grub/grub.cfg | grep Xen | cut -d \' -f 2 | head -1)"
 
</pre>
 
</pre>
Of course adapt this accordingly to your setup (UUID, modules, etc).
+
What this does is set your default entry in GRUB to the first entry containing 'Xen'. Run this every time you upgrade Alpine or Xen.
 +
 
 +
== Loop Devices ==
 +
If you plan to use more than 8 DomU's, you may need to increase the amount of loop-devices in your Dom0.
  
Let's start Xen services:
+
In Alpine Linux, you will need to add the ''max_loop'' option to the ''loop'' module, then add the loop module to your initramfs.
{{Cmd|
 
apk add xen
 
apk add udev
 
rc-service udev start ; rc-service udev-postmount start
 
rc-service xencommons start
 
}}
 
xl should work. If you want "xm" command
 
{{Cmd|rc-service xend start}}
 
  
So let's install services at boot time :
+
Start by populating <code>/etc/modprobe.d/loop.conf</code> with the module options:
{{Cmd|
 
rc-update add udev sysinit
 
rc-update add udev-postmount default
 
rc-update add xencommons
 
rc-update add xend
 
}}
 
  
since we use a serial line, let'a add a serial console prompt, modify your /etc/inittab accordinly:
 
 
<pre>
 
<pre>
# Put a getty on the serial port
+
# touch /etc/modprobe.d/loop.conf
#ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100
+
# echo "options loop max_loop=32" > /etc/modprobe.d/loop.conf
hvc0::respawn:/sbin/getty -L hvc0 115200 vt100
 
 
</pre>
 
</pre>
hvc0 is Xen console output, where we have already redirected the kernel messages.
 
To switch to Xen console, type three time "Ctrl+a"
 
  
Now you can configure your guest, but before don't forget to load Xen kernel module:
+
Now reflect the module options in the initramfs:
{{Cmd|modprobe xen-gntdev
 
modprobe xen-gntalloc
 
modprobe tun
 
echo "xen-gntdev" >> /etc/modules
 
echo "xen-gntalloc" >> /etc/modules
 
echo "tun" >> /etc/modules
 
}}
 
Yes, tun is not a Xen module but is needed to create tap interface in Dom0.
 
Before creating your VM don't forget to create xenbr0 bridge, otherwise Xen will change eth0 into peth0 and eth0 will become a bridge (!):
 
{{Cmd|
 
brctl addbr xenbr0
 
ifconfig xenbr0 up
 
}}
 
So now if you want to plug your "real" network card in your bridge: (192.168.1.10 is eth0 ip)
 
{{Cmd|
 
ifconfig eth0 0.0.0.0
 
brctl addif xenbr0 eth0
 
ifconfig xenbr0 192.168.1.10
 
}}
 
  
 
+
<pre>
on going debug:
+
# mkinitfs
vi /etc/rc.conf
+
# reboot
rc_sys="xen0"
+
</pre>
why ?
 
  
 
== See also ==
 
== See also ==
 
* [[Xen Dom0 on USB or SD]]
 
* [[Xen Dom0 on USB or SD]]
 
+
* [https://wiki.gentoo.org/wiki/Xen#Host_configuration_.28domain-0.29|Xen page on Gentoo wiki]
 
[[Category:Virtualization]]
 
[[Category:Virtualization]]

Revision as of 08:18, 27 August 2020

This guide will show you how to have your 'sys' install of Alpine run as a Xen Dom0. You can start either from an existing standard install or install a new copy of Alpine with the Alpine Xen ISO.

Install Xen

New installation

Writing the medium

Tango-dialog-warning.png
Warning: This will erase everything on the drive you point it at. Check and double check that /dev/sdx is the correct USB device you want to write to, using the commands lsblk and blkid.


First download Alpine's Xen install ISO, and either burn the ISO to a CD/DVD or write it to a USB storage device with the following command, where 3.12.0 should be replaced with the release number of your downloaded ISO and /dev/sdx should be replaced with the drive letter of your USB:

dd if=alpine-xen-3.12.0-x86_64.iso of=/dev/sdx

Installation

Now boot from your CD or USB, and type 'root' when prompted for a username. After you have logged in run setup-xen-dom0, then continue with a standard Alpine installation until you get to the prompt asking to choose your network card. What you'll want to do is select what is to be your internet-facing interface, and when asked to bridge it type 'yes'. Then you can configure the networking settings of your bridge device, br0, as you would have configured your internet-facing interface.

Note: You cannot bridge a WiFi interface in the automatic installation script due to incompatible protocols. Make sure you pick an ethernet interface for this.

Now continue with your installation to disk until you reach the 'reboot' prompt. There are a few more things to do before you can boot without errors:

# xen-hypervisor isn't installed by default with Xen so we must install it manually
apk add xen-hypervisor
apk add bridge

Now you can safely reboot after removing your install medium, making sure to pick the Alpine Linux v3.12, with Xen 4.13.1 and Linux lts boot option in your GRUB menu, with 3.12 and 4.13.1 replaced with your Linux and Xen version numbers, respectively.

After this, enable the Alpine community repository and install the firmware to be used for Xen's virtual machines:

apk add seabios ovmf

Now you are ready to configure GRUB.

Existing installation

First you must enable the Alpine community repository, then install Xen and the seabios (BIOS) and ovmf (UEFI) firmwares for its virtual machines.

# apk add xen xen-hypervisor seabios ovmf

This will install Xen Hypervisor, xl cli command and all the required packages. The next step is to modify your GRUB configuration to properly boot Xen.

The next step is to load the necessary kernel modules for Xen, we will add them to /etc/modules, so they will be loaded automatically on boot:

echo "xen-netback" >> /etc/modules
echo "xen-blkback" >> /etc/modules
echo "tun" >> /etc/modules

Then lastly we add the Xen daemons to the default runlevel.

rc-update add xenconsoled
rc-update add xendomains
rc-update add xenqemu
rc-update add xenstored

Now reboot.

GRUB configuration

Once running a Xen kernel we will need to edit its command-line options and enable the setting of a default GRUB entry by inserting this at the bottom of /etc/default/grub:

Contents of /etc/default/grub

# We need to set the amount of RAM we allocate to our Dom0 Alpine install so that # our future virtual machines are left with enough memory. GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M" GRUB_DEFAULT="saved" GRUB_SAVEDEFAULT="true"

You can replace 1024M with the amount of memory you want to allocate to your Dom0 operating system. After this you need to run the following:

grub-mkconfig -o /boot/grub/grub.cfg
grub-set-default "$(grep ^menuentry /boot/grub/grub.cfg | grep Xen | cut -d \' -f 2 | head -1)"

What this does is set your default entry in GRUB to the first entry containing 'Xen'. Run this every time you upgrade Alpine or Xen.

Loop Devices

If you plan to use more than 8 DomU's, you may need to increase the amount of loop-devices in your Dom0.

In Alpine Linux, you will need to add the max_loop option to the loop module, then add the loop module to your initramfs.

Start by populating /etc/modprobe.d/loop.conf with the module options:

# touch /etc/modprobe.d/loop.conf
# echo "options loop max_loop=32" > /etc/modprobe.d/loop.conf

Now reflect the module options in the initramfs:

# mkinitfs
# reboot

See also