User Tools

Site Tools


civilinfrastructureplatform:testingkernelcivmsetup

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
civilinfrastructureplatform:testingkernelcivmsetup [2017/02/05 04:23]
sesa126914
civilinfrastructureplatform:testingkernelcivmsetup [2017/02/19 01:33] (current)
Agustin Benito Bethencourt content moved
Line 1: Line 1:
-====== KernelCI Virtual Machine Setup & Configuration ====== +Deprecated pagePlease check [[ciptestingboardatdesksingledevsetup|Board at desk single dev set up]] and configuration.
- +
-===== “Board @ Desk - Single Developer” testing setup ===== +
- +
-The current setup requires (2) Virtual Machines; one for KernelCI and the other for LAVA v2The LAVA v2 VM Setup and Configuration can be found here: +
- +
-[[https://​wiki.linuxfoundation.org/​doku.php?​id=civilinfrastructureplatform/​testinglavav2vmsetup]] +
- +
-==== Setting up KernelCI VM ==== +
- +
-1. Install Vagrant +
- +
-''​[user@host ~] $ **sudo apt-get install vagrant**''​ +
- +
-2. Install Oracle Virtualbox +
- +
-''​[user@host ~] $ **sudo apt-get install virtualbox**''​ +
- +
-      * OR, if you downloaded Virtualbox from the Oracle website  +
-      * //Note: This assumes you are running Ubuntu Xenial(16.04) 64-bit// +
- +
-      * ''​[user@host ~] $ **cd Downloads**''​ +
- +
-''​[user@host Downloads] $ **sudo dpkg -i virtualbox-5.1_5.1.8-111374-Ubuntu-xenial_amd64.deb**''​ +
- +
-3. Get the CIP KernelCI Project +
- +
-''​[user@host ~/git] $ **git clone [[https://​gitlab.com/​cip-project/​testing.git]]**''​ +
- +
-4. Change to the testing directory +
- +
-''​[user@host ~/git] $ **cd testing**''​ +
- +
- +
-5. Launch the KernelCI Virtual Machine +
- +
-''​[user@host ~/​git/​testing] $ **vagrant ​up**''​ +
- +
-//Note: Please ignore any warnings such as "​GetPassWarning:​ Can not control echo on the terminal."​ or "​Warning:​ Password input may be echoed."​ - These do not affect the operation of the KernelCI VM.// +
- +
- +
-6. Connect to the KernelCI VM through ssh using vagrant +
- +
-''​[user@host ~$ **vagrant ssh**''​ +
- +
- +
-==== Get CIP Kernel using git ==== +
- +
-7. Change to the git-repos directory +
- +
-''​vagrant@guest:​~$ **cd git-repos**''​ +
- +
-8. Clone the CIP Linux Kernel +
- +
-''​vagrant@guest:​~/​git-repos$ **git clone [[https://​gitlab.com/​cip-project/​linux-cip.git]]**''​ +
- +
-9. Find the branch of the kernel version you want (i.e. 4.4.27) +
- +
-''​vagrant@guest:​~/​git-repos$ **cd linux-stable**''​ +
- +
-''​vagrant@guest:​~/​git-repos/​linux-stable$ **git tag -l | grep 4.4.y**''​ +
- +
-10. Create a new branch using that tag. +
- +
-''​vagrant@guest:​~/​git-repos/​linux-stable$ **git checkout -b cip_v4.4.27 v4.4.27**''​ +
- +
- +
-==== Compile CIP Kernel ==== +
- +
-11. Set the environment variables +
- +
-''​vagrant@guest:​~/​git-repos/​linux-stable$ **export TREE_NAME=cip-test**''​ +
- +
-''​vagrant@guest:​~/​git-repos/​linux-stable$ **export ARCH=arm**''​ +
- +
-''​vagrant@guest:​~/​git-repos/​linux$ **export CROSS_COMPILE=arm-linux-gnueabi-**''​ +
- +
-//Note: Don't forget the dash (-) at the end of the ''​CROSS_COMPILE''​ line!// +
- +
-12. Execute the build.py command +
- +
-''​vagrant@guest:​~/​git-repos/​linux-stable$ **~/​kernelci-build/​build.py -c tinyconfig -p CIP-KernelCI**''​ +
- +
-13. The Web Server is already running in the background. when you navigate from page to page the logs are written to the screen. To get back to the command line, simply press Enter. On subsequent boots, you will need to start the Web Server with the following command: +
- +
-''​vagrant@guest:​~$ **/​vagrant/​scripts/​start_webserver.sh**''​ +
- +
-14. On your host machine, open a web browser ​and enter the following in the address box: +
- +
-''​**http://​localhost:​5000**''​ +
- +
-15. You will see the KernelCI Website home page from which, you can navigate to the different builds and Trees that you've created (see Example Builds below) +
-{{ :​cip:​kernelci-homepage2.png?​nolink&​600 |}} +
- +
-16. Click on the Jobs button at the top of the page and you will see all of the available Trees  +
-{{ :​civilinfrastructureplatform:​build_details_tyrannosaurus-available-jobs.png?​600 |}} +
- +
-17. Click on the cip-tyrannosaurus Tree and you will see the list of available builds, or kernel versions. +
-{{ :​civilinfrastructureplatform:​build_details_tyrannosaurus-available-builds.png?​600 |}} +
- +
-18. Click on the v4.4.27 kernel and you will see the list of build configurations. The tinyconfig ​configuration ​is shown below, but the allnoconfig is also available. +
-{{ :​civilinfrastructureplatform:​build_details_tyrannosaurus-tinyconfig.png?​600 |}} +
- +
-19. The files that resulted from the build are available in the KernelCI website by navigating to the Tree Name, Kernel version, and Configuration. They are stored on the hard drive at: +
- +
-''/​var/​www/​images/​kernel-ci/​TREE_NAME/​KERNEL_VERSION/​ARCH_CONFIG''​ +
- +
-For instance, for the build with the following parameters:  +
- +
-   * TREE_NAME: **cip-tyrannosaurus** +
-   * KERNEL_VERSION:​ **v4.4.27** +
-   * ARCH_CONFIG:​ **arm_tinyconfig** +
- +
-The files will be located at: +
- +
-''/​var/​www/​images/​kernel-ci/​cip-tyrannosaurus/​v4.4.27/​arm-tinyconfig''​ +
- +
- +
-==== Example Builds ==== +
- +
-20. Included in the /​vagrant/​scripts directory, there is a script named create_builds.sh. It clones the CIP Kernel and builds it with the following: Three different tree names and two different build configurations each. +
- +
-* TREE_NAME=cip-tyrannosaurus +
-   * tinyconfig +
-   * allnoconfig +
- +
-* TREE_NAME=cip-stegosaurus +
-   * sunxi_defconfig +
-   * axm55xx_defconfig +
- +
-* TREE_NAME=cip-triceratops +
-   * tinyconfig +
-   * allnoconfig +
- +
- +
-[[ciptesting|Back to the parent page]]+
civilinfrastructureplatform/testingkernelcivmsetup.1486268587.txt.gz · Last modified: 2017/02/05 04:23 by sesa126914