Difference between revisions of "Xen installation"

From ERIKA WIKI
Jump to: navigation, search
Line 1: Line 1:
 
== Introduction ==
 
== Introduction ==
 
The section contains the instruction to install Xen hypervisor on platform x86-64.
 
The section contains the instruction to install Xen hypervisor on platform x86-64.
Furthermore, it contains the procedure for running Windows OS under Xen hypervisor.
+
Furthermore, it contains the procedure for running a guest operating system (i.e., Windows OS) under Xen hypervisor.
  
 
== Xen Installation procedure ==
 
== Xen Installation procedure ==
Line 47: Line 47:
 
   $ $XENPATH/configure --enable-systemd
 
   $ $XENPATH/configure --enable-systemd
  
In case of Xen EFI (as for example in <i>Ubuntu 18.04.01</i>), add the option <code>--enable-targets=x86_64-pep</code> as follows:
+
In case of Xen EFI, add the option <code>--enable-targets=x86_64-pep</code> as follows:
 
   $ $XENPATH/configure --enable-systemd --enable-targets=x86_64-pep
 
   $ $XENPATH/configure --enable-systemd --enable-targets=x86_64-pep
  
Line 56: Line 56:
  
 
Install (as root):
 
Install (as root):
   # make install
+
   # sudo make install
  
 
<b>Enable the Xen services</b><br>
 
<b>Enable the Xen services</b><br>
 
Reload dynamic libraries:
 
Reload dynamic libraries:
   # /sbin/ldconfig
+
   # sudo /sbin/ldconfig
  
 
Enable systemd Xen services:
 
Enable systemd Xen services:
   # systemctl enable xen-qemu-dom0-disk-backend.service
+
   # sudo systemctl enable xen-qemu-dom0-disk-backend.service
   # systemctl enable xen-init-dom0.service
+
   # sudo systemctl enable xen-init-dom0.service
   # systemctl enable xenconsoled.service
+
   # sudo systemctl enable xenconsoled.service
   # systemctl enable xenstored.service
+
   # sudo systemctl enable xenstored.service
   # systemctl enable xendomains.service
+
   # sudo systemctl enable xendomains.service
 
Note that in case of error for enabling xendomains service, remove <code>/etc/init.d/xendomains</code>.
 
Note that in case of error for enabling xendomains service, remove <code>/etc/init.d/xendomains</code>.
  
 
<b>Update grub</b><br>
 
<b>Update grub</b><br>
 
Finally, update grub and reboot:
 
Finally, update grub and reboot:
   # udate-grub
+
   # sudo udate-grub
   # reboot
+
   # sudo reboot
  
 
== Example: Creating a Windows HVM (Hardware Virtualized) Guest ==
 
== Example: Creating a Windows HVM (Hardware Virtualized) Guest ==
 
In order to create a Windows HVM (Hardware Virtualized) Guest, performs the following operations:
 
In order to create a Windows HVM (Hardware Virtualized) Guest, performs the following operations:
 
<ul>  
 
<ul>  
<li>Setup the LVM storage: LVM, Logical Volume Manager, allows Linux to manage block devices in a more abstract manner. LVM creates ''logical volumes'' within a ''volume group'' that can share the same physical storage, known as ''physical volume''.
+
<li> Setup the LVM storage
 
</li>
 
</li>
 
<li> Setup Linux Bridge in order to attach guest machines to the external network
 
<li> Setup Linux Bridge in order to attach guest machines to the external network
Line 89: Line 89:
  
 
=== Setup LVM storage ===
 
=== Setup LVM storage ===
 +
LVM, Logical Volume Manager, allows Linux to manage block devices in a more abstract manner. LVM creates ''logical volumes'' within a ''volume group'' that can share the same physical storage, known as ''physical volume''.
 
The LVM setup process can be summarized as allocating a physical volume, creating a volume group on top of this, then creating logical volumes to store data.
 
The LVM setup process can be summarized as allocating a physical volume, creating a volume group on top of this, then creating logical volumes to store data.
  
 
Install LVM:
 
Install LVM:
  apt-get install lvm2
+
  # sudo apt-get install lvm2
  
Create a physical volume associated with the device (e.g., <code>/dev/XenVolumeGroup</code>):
+
Create a physical partition (if there none free) by using a partition manager (e.g., <code>gparted</code>).
  pvcreate /dev/XenVolumeGroup
+
Create a physical volume associated with the physical partition (e.g., <code>/dev/XenVolumeGroup</code>):
 +
  # sudo pvcreate /dev/XenVolumeGroup
  
Create a volume group called <code>vg0</code> using this physical volume:
+
Create a volume group, called <code>vg0</code>, using this physical volume:
  vgcreate vg0 /dev/XenVolumeGroup
+
  # sudo vgcreate vg0 /dev/XenVolumeGroup
  
Create a new logical volume, named <code>windows</code>, of 50Gbytes size on the volume group called vg0:
+
Finally, create a new logical volume, named <code>windows</code>, of 50Gbytes size on the volume group <code>vg0</code>:
  lvcreate -n windows -L 50G vg0
+
  # sudo lvcreate -n windows -L 50G vg0
  
 
=== Setup Linux Bridge for guest networking ===
 
=== Setup Linux Bridge for guest networking ===
 
In order to allow network access to the Xen guests, the Linux bridge package allows to create a virtual switch within Dom0. The switch will take packets from the virtual machines and forward them on to the physical network.
 
In order to allow network access to the Xen guests, the Linux bridge package allows to create a virtual switch within Dom0. The switch will take packets from the virtual machines and forward them on to the physical network.
  
In order to install the Linux bridge package and its core component, launche the following command:
+
In order to install the Linux bridge package and its core component, launch the following command:
 
   % sudo apt-get install bridge-utils
 
   % sudo apt-get install bridge-utils
  
Edit '/etc/network/interfaces' file by adding:
+
In case of Linux bridge configured by DHCP, edit <code>/etc/network/interfaces</code> file as follows:
# dhcp
 
 
   auto xenbr0
 
   auto xenbr0
 
   iface xenbr0 inet dhcp
 
   iface xenbr0 inet dhcp
 
     bridge_ports <your-network-interface>
 
     bridge_ports <your-network-interface>
 +
where <code> <your-network-interface></code> is the physical interface (e.g., <code>eth0</code>).
  
# static bridging
+
In case of static Linux bridge, edit <code>/etc/network/interfaces</code> file as follows:
 
   auto xenbr0
 
   auto xenbr0
 
   iface xenbr0 inet static
 
   iface xenbr0 inet static
 
     bridge_ports <your-network-interface>
 
     bridge_ports <your-network-interface>
     address <add>
+
     address <bridge-address>
 
     netmask 255.255.255.0
 
     netmask 255.255.255.0
     gateway <gw>
+
     gateway <gtw-address>
     broadcast <bcast address>
+
     broadcast <bcast-address>
 +
 
 +
where <code> <your-network-interface></code> is the physical interface (e.g., <code>eth0</code>) and
 +
<code><bridge-address></code>, <code><bridge-address></code> and <code><bridge-address></code> are respectively the address assigned to the Linux bridge, the gateway address and the broadcast address.
  
 
Then, restart networking:
 
Then, restart networking:
 
   % sudo service networking restart
 
   % sudo service networking restart
  
Showing bridge setup:
+
In case of correct setup, the command <code>brctl</code> will show the bridge setup:
  % brctl show
+
  % brctl show
 
+
 
    bridge name    bridge id              STP enabled    interfaces
+
  bridge name    bridge id              STP enabled    interfaces
    xenbr0 8000.006065444af1 no      <your-network-interface>
+
  xenbr0 8000.006065444af1 no      <your-network-interface>
  
 
=== Install Windows OS on the Xen HVM Guest ===
 
=== Install Windows OS on the Xen HVM Guest ===

Revision as of 09:17, 15 May 2019

Introduction

The section contains the instruction to install Xen hypervisor on platform x86-64. Furthermore, it contains the procedure for running a guest operating system (i.e., Windows OS) under Xen hypervisor.

Xen Installation procedure

The following installation procedure aims at installing Xen RELEASE-4.11.0 from source. It has been performed on the platform x86-64 with one of the following operating system:

  • Ubuntu 16.04
  • Ubuntu 18.04.1 LTS

Build Dependencies
Install the following packages:

 # apt update && apt dist-upgrade #update/upgrade the kernel
 # apt install build-essential
 # apt install bcc bin86 gawk bridge-utils iproute2 
 # apt install libcurl4 libcurl4-openssl-dev bzip2 module-init-tools transfig tgif
 # apt install texinfo texlive-latex-base texlive-latex-recommended texlive-fonts-extra texlive-fonts-recommended
 # apt install pciutils-dev mercurial
 # apt install make gcc libc6-dev zlib1g-dev python python-dev python-twisted 
 # apt install libncurses5-dev patch libsdl-dev libjpeg-dev
 # apt install libvncserver-dev
 # apt install iasl libbz2-dev e2fslibs-dev git-core uuid-dev 
 # apt install ocaml ocaml-findlib libx11-dev bison flex xz-utils libyajl-dev
 # apt install gettext libpixman-1-dev libaio-dev markdown pandoc
 # apt install libc6-dev-i386
 # apt install lzma lzma-dev liblzma-dev #for rombios
 # apt install libsystemd-dev xorriso

Retrieve the GRUB version
The Xen installation strictly depends on the installed Grub version: grub-pc or grub-efi. In order to retrieve the grub version, launch the following command:

 $ dpkg --get-selections | grep grub

Retrieve Xen source
Clone the Xen repository and switch to the chosen version (i.e., RELEASE 4.11):

 $ git clone https://github.com/xen-project/xen.git
 $ cd xen
 $ git checkout RELEASE-4.11.0 -b RELEASE-4.11.0

In the following part of the tutorial, we refer to the Xen repository path as $XENPATH.

Configure
Configure:

 $ $XENPATH/configure --enable-systemd

In case of Xen EFI, add the option --enable-targets=x86_64-pep as follows:

 $ $XENPATH/configure --enable-systemd --enable-targets=x86_64-pep

Build and install
Build all components (hypervisor, tools, docs, stubdomains, etc):

 $ cd $XENPATH
 $ make dist

Install (as root):

 # sudo make install

Enable the Xen services
Reload dynamic libraries:

 # sudo /sbin/ldconfig

Enable systemd Xen services:

 # sudo systemctl enable xen-qemu-dom0-disk-backend.service
 # sudo systemctl enable xen-init-dom0.service
 # sudo systemctl enable xenconsoled.service
 # sudo systemctl enable xenstored.service
 # sudo systemctl enable xendomains.service

Note that in case of error for enabling xendomains service, remove /etc/init.d/xendomains.

Update grub
Finally, update grub and reboot:

 # sudo udate-grub
 # sudo reboot

Example: Creating a Windows HVM (Hardware Virtualized) Guest

In order to create a Windows HVM (Hardware Virtualized) Guest, performs the following operations:

  • Setup the LVM storage
  • Setup Linux Bridge in order to attach guest machines to the external network
  • Install Windows OS on the Xen HVM Guest
  • Run Windows OS on the Xen HVM Guest

Setup LVM storage

LVM, Logical Volume Manager, allows Linux to manage block devices in a more abstract manner. LVM creates logical volumes within a volume group that can share the same physical storage, known as physical volume. The LVM setup process can be summarized as allocating a physical volume, creating a volume group on top of this, then creating logical volumes to store data.

Install LVM:

 # sudo apt-get install lvm2

Create a physical partition (if there none free) by using a partition manager (e.g., gparted). Create a physical volume associated with the physical partition (e.g., /dev/XenVolumeGroup):

 # sudo pvcreate /dev/XenVolumeGroup

Create a volume group, called vg0, using this physical volume:

 # sudo vgcreate vg0 /dev/XenVolumeGroup

Finally, create a new logical volume, named windows, of 50Gbytes size on the volume group vg0:

 # sudo lvcreate -n windows -L 50G vg0

Setup Linux Bridge for guest networking

In order to allow network access to the Xen guests, the Linux bridge package allows to create a virtual switch within Dom0. The switch will take packets from the virtual machines and forward them on to the physical network.

In order to install the Linux bridge package and its core component, launch the following command:

  % sudo apt-get install bridge-utils

In case of Linux bridge configured by DHCP, edit /etc/network/interfaces file as follows:

 auto xenbr0
 iface xenbr0 inet dhcp
    bridge_ports <your-network-interface>

where <your-network-interface> is the physical interface (e.g., eth0).

In case of static Linux bridge, edit /etc/network/interfaces file as follows:

 auto xenbr0
 iface xenbr0 inet static
   bridge_ports <your-network-interface>
   address <bridge-address>
   netmask 255.255.255.0
   gateway <gtw-address>
   broadcast <bcast-address>

where <your-network-interface> is the physical interface (e.g., eth0) and <bridge-address>, <bridge-address> and <bridge-address> are respectively the address assigned to the Linux bridge, the gateway address and the broadcast address.

Then, restart networking:

  % sudo service networking restart

In case of correct setup, the command brctl will show the bridge setup:

 % brctl show
 
 bridge name     bridge id               STP enabled     interfaces
 xenbr0		8000.006065444af1	no      <your-network-interface>

Install Windows OS on the Xen HVM Guest

By assuming the Windows iso is located in /root/windows.iso, it follows an example of configuration file, referred to as windows.cfg to enable the installation of Windows on the logical volume.

 name="win"
 builder="hvm"
 
 memory=4096
 vcpus=2 #2cpus
 
 #disk option
 disk=['file:/dev/XenVolumeGroup/windows,hda,w', 'file://root/windows.iso,hdb:cdrom,r']
 boot="dc"
 
 #networking
 vif=['type=ioemu, bridge=xenbr0']
 
 #vnc or sdl
 vnc=1
 sdl=0
 
 stdvga=0
 usb=1
 usbdevice="tablet"
 ide0="noprobe"
 serial="pty"
 
 on_poweroff="destroy"
 on_reboot="preserve"
 on_crash="preserve"

Launch the following command to start the guest:

 $ xl create windows.cfg

Then, the VNC display should be available on port 5900 of your dom0 IP, for instance using vncviewer:

  $ vncviewer <dom0-ip-address>:5900

Then, proceed with Windows' installation. Once you have installed Windows by formatting the disk and by following the prompts the domain will restart. However, in order to prevent the booting from DVD, destroy the domain:

  $ xl destroy win

Run Windows OS on the Xen HVM Guest

After installing the Windows on the logical volume, change the boot line in the config file (i.e., windows.cfg)

  boot="c"

Then start the domain:

  $ xl create windows.cfg

and reconnect with VNC to have access to the Windows GUI.