Difference between revisions of "Compiling Xen From Source on NetBSD"

From Xen
(Dependencies)
 
(17 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
==Introduction==
 
==Introduction==
  
The purpose of this document is to guide users through the process of installing Xen from source (either from the tarball releases or from a source code repository).
+
The purpose of this document is to guide users through the process of installing Xen Project software from source (either from the tarball releases or from a source code repository).
  
This document was written targeting the Xen 4.2 release, which is the first release to build natively on NetBSD without any specific patches.
+
This document was written targeting the Xen Project 4.2 release, which is the first release to build natively on NetBSD without any specific patches.
  
 
An assumption is made of some familiarity with the general concept of building software and with using your distributions package manager to install relevant build tools etc.
 
An assumption is made of some familiarity with the general concept of building software and with using your distributions package manager to install relevant build tools etc.
Line 9: Line 9:
 
==Dependencies==
 
==Dependencies==
  
The first step is to install the dependencies needed by Xen, they can all be found in pkgsrc. Here is the list of packages that should be installed for 4.2:
+
The first step is to install the dependencies needed by the Xen Project software, they can all be found in pkgsrc. Here is the list of packages that should be installed for 4.2:
  
<pre>
+
devel/mercurial
devel/mercurial
+
devel/scmgit
devel/scmgit
+
devel/gmake
devel/gmake
+
lang/python27
lang/python27
+
devel/py27-curses
devel/py-curses
+
devel/dev86
devel/dev86
+
devel/glib2
devel/glib2
+
devel/yajl
devel/yajl
+
 
</pre>
+
If you followed the [http://www.netbsd.org/docs/pkgsrc/using.html#building-packages-from-source pkgsrc instructions for building from source], and didn't install anything aside from the minimal selection of sets, the <code>comp</code> and the <code>text</code> sets, you also have to install:
 +
 
 +
shell/bash
 +
devel/pkg-config
 +
 
 +
==Cloning==
 +
 
 +
To clone the repository with git, use:
  
If you followed the [http://www.netbsd.org/docs/pkgsrc/using.html#building-packages-from-source|pkgsrc instructions for building from source], and didn't install anything aside from the minimal selection of sets, the <code>comp</code> and the <code>text</code> sets, you also have to install:
+
git clone -b <BRANCH> git://xenbits.xen.org/xen
  
<pre>
+
Note: you can find a list of the available branches and how to obtain them [[Xen_Repositories|here]].
shell/bash
 
</pre>
 
  
 
==Configuration==
 
==Configuration==
  
From Xen 4.2 onwards Xen uses the commonly used ''autoconf'' tool to provide compile time configurability of the toolstack. This allows some control of what features are built into Xen, as well as compile time sanity checking. Since pkgsrc installs packages in /usr/pkg, we will need to instruct configure to search for the required libraries there:
+
From Xen Project 4.2 onwards Xen uses the commonly used ''autoconf'' tool to provide compile time configurability of the toolstack. This allows some control of what features are built into Xen Project, as well as compile time sanity checking. Since pkgsrc installs packages in /usr/pkg, we will need to instruct configure to search for the required libraries there:
  
<pre>
+
$ ./configure PYTHON=/usr/pkg/bin/python2.7 APPEND_INCLUDES=/usr/pkg/include APPEND_LIB=/usr/pkg/lib --prefix=/usr/xen42
$ ./configure PYTHON=/usr/pkg/bin/python2.7 APPEND_INCLUDES=/usr/pkg/include APPEND_LIB=/usr/pkg/lib --prefix=/usr/xen42
 
</pre>
 
  
 
Please note that "prefix" has been set to /usr/xen42, you can change this to install it in /usr/pkg or whatever directory that suits your needs.
 
Please note that "prefix" has been set to /usr/xen42, you can change this to install it in /usr/pkg or whatever directory that suits your needs.
Line 42: Line 45:
 
Now that the configuration has finished, let's start the building. Stubdomains are not available on NetBSD, so we will skip the build of those:
 
Now that the configuration has finished, let's start the building. Stubdomains are not available on NetBSD, so we will skip the build of those:
  
<pre>
+
$ gmake PYTHON=/usr/pkg/bin/python2.7 xen
$ gmake PYTHON=/usr/pkg/bin/python2.7 xen
+
$ gmake LD_LIBRARY_PATH=/usr/pkg/lib tools
$ gmake LD_LIBRARY_PATH=/usr/pkg/lib tools
 
</pre>
 
  
{{Info|The Xen build system supports running several jobs at the same time, so it's recomendable to use the -jX option to speed up the build process if you have a SMP machine.}}
+
{{Info|The Xen Project build system supports running several jobs at the same time, so it's recommendable to use the -jX option to speed up the build process if you have a SMP machine.}}
  
 
==Install==
 
==Install==
  
First, we will copy the Xen kernel to /:
+
First, we will copy the Xen Project kernel to /:
  
<pre>
+
# cp xen/xen.gz /xen.gz
# cp xen/xen.gz /xen.gz
 
</pre>
 
  
 
Now we need to fetch a Dom0 kernel for the NetBSD version we are running, Dom0 kernels can be found at:
 
Now we need to fetch a Dom0 kernel for the NetBSD version we are running, Dom0 kernels can be found at:
Line 63: Line 62:
 
</pre>
 
</pre>
  
Download it to /, unpack and rename it to netbsd.xen. The next step is to modify the bootloader to correctly boot the Xen kernel and NetBSD. The following line should be added to /boot.cfg:
+
{{info|Note: For PAE-enabled xen.gz ELFs, there are also PAE kernels in the binary/kernel directory of your <version>/<architecture> setup on the netbsd ftp.}}
 +
 
 +
Download it to /, unpack and rename it to netbsd.xen. The next step is to modify the bootloader to correctly boot the Xen Project kernel and NetBSD. The following line should be added to /boot.cfg:
  
<pre>
+
menu=NetBSD Xen:load /netbsd.xen console=pc;multiboot /xen.gz dom0_mem=512M
menu=NetBSD Xen:load /netbsd.xen console=com0;multiboot /xen.gz dom0_mem=512M
 
</pre>
 
  
 
For a serial console boot use the following:
 
For a serial console boot use the following:
  
<pre>
+
menu=NetBSD Xen com0:load /netbsd.xen console=com0;multiboot /xen.gz dom0_mem=512M console=com1 com1=115200,8n1
menu=NetBSD Xen com0:load /netbsd.xen console=com0;multiboot /xen.gz dom0_mem=512M console=com1 com1=115200,8n1
 
</pre>
 
  
Also, set the dom0_mem parameter to an appropriate value for your use case. More info about the Xen kernel boot parameters can be found at [[Xen Command Line and Boot Options]].
+
Also, set the dom0_mem parameter to an appropriate value for your use case. More info about the Xen Project kernel boot parameters can be found at [[Xen Command Line and Boot Options]].
  
 
Finally, we should install the tools that we compiled previously:
 
Finally, we should install the tools that we compiled previously:
  
<pre>
+
# gmake install-tools
# gmake install-tools
 
</pre>
 
  
 
Now we can reboot into the newly installed Xen system:
 
Now we can reboot into the newly installed Xen system:
  
<pre>
+
# shutdown -r now
# shutdown -r now
 
</pre>
 
  
 
==Basic usage==
 
==Basic usage==
  
If you have installed Xen in a location different than /usr/pkg you will need to add it to your LD_LIBRARY_PATH, PATH and PYTHONPATH:
+
If you have installed the hypervisor in a location different than /usr/pkg you will need to add it to your LD_LIBRARY_PATH, PATH and PYTHONPATH:
 +
 
 +
# export LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:/usr/xen42/lib"
 +
# export PATH="${PATH}:/usr/xen42/sbin:/usr/xen42/bin"
 +
# export PYTHONPATH="/usr/xen42/lib/python2.7/site-packages"
 +
 
 +
{{warning|If the directory <code>/var/lib/xenstored</code> is missing, both the xencommons script and the tools will hang indefinitely. Please check that this directory exists before proceeding further.}}
 +
 
 +
To begin using the hypervisor, xencommons has to be started:
  
<pre>
+
# /usr/xen42/etc/rc.d/xencommons onestart
# export LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:/usr/xen42/lib"
 
# export PATH="${PATH}:/usr/xen42/sbin:/usr/xen42/bin"
 
# export PYTHONPATH="/usr/xen42/lib/python2.7/site-packages"
 
</pre>
 
  
To begin using Xen, xencommons has to be started:
+
If you built the hypervisor onto another system, runtime dependencies are required:
  
<pre>
+
devel/yajl
# /usr/xen42/etc/rc.d/xencommons onestart
 
</pre>
 
  
 
Check that xl is working:
 
Check that xl is working:
  
<pre>
+
# xl list
# xl list
 
</pre>
 
  
[[Category:Users]] [[Category:Host Install]] [[Category:NetBSD]]
+
[[Category:Users]] [[Category:Host Install]] [[Category:NetBSD]] [[Category:Fundamentals]]

Latest revision as of 00:16, 18 April 2014

Introduction

The purpose of this document is to guide users through the process of installing Xen Project software from source (either from the tarball releases or from a source code repository).

This document was written targeting the Xen Project 4.2 release, which is the first release to build natively on NetBSD without any specific patches.

An assumption is made of some familiarity with the general concept of building software and with using your distributions package manager to install relevant build tools etc.

Dependencies

The first step is to install the dependencies needed by the Xen Project software, they can all be found in pkgsrc. Here is the list of packages that should be installed for 4.2:

devel/mercurial
devel/scmgit
devel/gmake
lang/python27
devel/py27-curses
devel/dev86
devel/glib2
devel/yajl

If you followed the pkgsrc instructions for building from source, and didn't install anything aside from the minimal selection of sets, the comp and the text sets, you also have to install:

shell/bash
devel/pkg-config

Cloning

To clone the repository with git, use:

git clone -b <BRANCH> git://xenbits.xen.org/xen

Note: you can find a list of the available branches and how to obtain them here.

Configuration

From Xen Project 4.2 onwards Xen uses the commonly used autoconf tool to provide compile time configurability of the toolstack. This allows some control of what features are built into Xen Project, as well as compile time sanity checking. Since pkgsrc installs packages in /usr/pkg, we will need to instruct configure to search for the required libraries there:

$ ./configure PYTHON=/usr/pkg/bin/python2.7 APPEND_INCLUDES=/usr/pkg/include APPEND_LIB=/usr/pkg/lib --prefix=/usr/xen42

Please note that "prefix" has been set to /usr/xen42, you can change this to install it in /usr/pkg or whatever directory that suits your needs.

Building

Now that the configuration has finished, let's start the building. Stubdomains are not available on NetBSD, so we will skip the build of those:

$ gmake PYTHON=/usr/pkg/bin/python2.7 xen
$ gmake LD_LIBRARY_PATH=/usr/pkg/lib tools
Icon Info.png The Xen Project build system supports running several jobs at the same time, so it's recommendable to use the -jX option to speed up the build process if you have a SMP machine.


Install

First, we will copy the Xen Project kernel to /:

# cp xen/xen.gz /xen.gz

Now we need to fetch a Dom0 kernel for the NetBSD version we are running, Dom0 kernels can be found at:

ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-<version>/<arch>/binary/kernel/netbsd-XEN3_DOM0.gz
Icon Info.png Note: For PAE-enabled xen.gz ELFs, there are also PAE kernels in the binary/kernel directory of your <version>/<architecture> setup on the netbsd ftp.


Download it to /, unpack and rename it to netbsd.xen. The next step is to modify the bootloader to correctly boot the Xen Project kernel and NetBSD. The following line should be added to /boot.cfg:

menu=NetBSD Xen:load /netbsd.xen console=pc;multiboot /xen.gz dom0_mem=512M

For a serial console boot use the following:

menu=NetBSD Xen com0:load /netbsd.xen console=com0;multiboot /xen.gz dom0_mem=512M console=com1 com1=115200,8n1

Also, set the dom0_mem parameter to an appropriate value for your use case. More info about the Xen Project kernel boot parameters can be found at Xen Command Line and Boot Options.

Finally, we should install the tools that we compiled previously:

# gmake install-tools

Now we can reboot into the newly installed Xen system:

# shutdown -r now

Basic usage

If you have installed the hypervisor in a location different than /usr/pkg you will need to add it to your LD_LIBRARY_PATH, PATH and PYTHONPATH:

# export LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:/usr/xen42/lib"
# export PATH="${PATH}:/usr/xen42/sbin:/usr/xen42/bin"
# export PYTHONPATH="/usr/xen42/lib/python2.7/site-packages"
Icon Ambox.png If the directory /var/lib/xenstored is missing, both the xencommons script and the tools will hang indefinitely. Please check that this directory exists before proceeding further.


To begin using the hypervisor, xencommons has to be started:

# /usr/xen42/etc/rc.d/xencommons onestart

If you built the hypervisor onto another system, runtime dependencies are required:

devel/yajl

Check that xl is working:

# xl list