Raisin: Difference between revisions
Lars.kurth (talk | contribs) |
No edit summary |
||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 20: | Line 20: | ||
=== 2. Install Selected OS === |
=== 2. Install Selected OS === |
||
We require a specific minimal functionality from your base Linux distribution to make it as easy as possible. We recommend using a minimal install of your chosen distro to get started. You may need to get git and a few other tools using the distros application managers, if the software does not come with the distro by default. |
We require a specific minimal functionality from your base Linux distribution to make it as easy as possible. We recommend using a minimal install of your chosen distro to get started. You may need to get git and a few other tools using the distros application managers, if the software does not come with the distro by default. All other dependencies are automatically retrieved or pulled from the relevant git repositories and then built. |
||
=== 3. Download Raisin === |
=== 3. Download Raisin === |
||
| Line 30: | Line 30: | ||
=== 4. Configure === |
=== 4. Configure === |
||
cp defconfig config |
|||
| ⚫ | |||
| ⚫ | We recommend that you review the configuration file called '''[http://xenbits.xen.org/gitweb/?p=raisin.git;a=blob;f=defconfig;h=47969f46331c8802c3b1203f6b37f0b5bf93915c;hb=HEAD raisin/defconfig]''', copy it to config, then make changes as necessary. Note that the configuration contains sensible defaults and will work. |
||
=== 5. Start the build and install === |
=== 5. Start the build and install === |
||
| Line 37: | Line 39: | ||
raise -y build |
raise -y build |
||
| ⚫ | It takes a few minutes, we recommend reading the [http://xenbits.xen.org/gitweb/?p=raisin.git;a=blob_plain;f=README;hb=HEAD README] file while it is building. Note that you will be asked for the sudo password to install dependencies. If you install them beforehand, manually or executing ''raise install-builddep'', no sudo password will be necessary. |
||
Note that you will asked for the sudo password. |
|||
| ⚫ | |||
== Resources == |
== Resources == |
||
Latest revision as of 14:47, 19 June 2015
Build, deployment and test tool for the Xen Project hypervisor.
Overview
The purpose of Raisin is to retrieve and build from source everything needed for a good Xen installation. Today that includes Xen, QEMU, Grub, SeaBios, OVMF and Libvirt. It can be used to quickly setup a Xen development environment. Optionally it can also install and configure the system for you.
Raisin is meant to be easy to read so that it can be used as a guideline on how to build and configure the system.
Quick Start
1. Select a Linux Distribution
Raisin has been tested on Debian Wheezy, Ubuntu 14.04 LTS, Fedora 21 and CentOS 6 & 7. It is likely that it will work with other distros, but we have not tested it at this stage. If you tried it, and it works, please add the distro to the list above.
2. Install Selected OS
We require a specific minimal functionality from your base Linux distribution to make it as easy as possible. We recommend using a minimal install of your chosen distro to get started. You may need to get git and a few other tools using the distros application managers, if the software does not come with the distro by default. All other dependencies are automatically retrieved or pulled from the relevant git repositories and then built.
3. Download Raisin
git clone git://xenbits.xenproject.org/raisin.git
The Raisin repo contains a script that installs builds Xen with all dependencies, configuration files and some tests.
4. Configure
cp defconfig config
We recommend that you review the configuration file called raisin/defconfig, copy it to config, then make changes as necessary. Note that the configuration contains sensible defaults and will work.
5. Start the build and install
cd raisin raise -y build
It takes a few minutes, we recommend reading the README file while it is building. Note that you will be asked for the sudo password to install dependencies. If you install them beforehand, manually or executing raise install-builddep, no sudo password will be necessary.
