civilinfrastructureplatform:testingkernelcivmsetup
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
civilinfrastructureplatform:testingkernelcivmsetup [2017/01/28 21:54] sesa126914 |
civilinfrastructureplatform:testingkernelcivmsetup [2017/02/09 16:51] kristderman [Get CIP Kernel using git] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== “Board @ Desk - Single Developer” testing setup ===== | ===== “Board @ Desk - Single Developer” testing setup ===== | ||
| - | The current setup requires (2) Virtual Machines; one for KernelCI and the other for LAVA v2 | + | The current setup requires (2) Virtual Machines; one for KernelCI and the other for LAVA v2. The LAVA v2 VM Setup and Configuration can be found here: |
| + | |||
| + | [[https://wiki.linuxfoundation.org/doku.php?id=civilinfrastructureplatform/testinglavav2vmsetup]] | ||
| ==== Setting up KernelCI VM ==== | ==== Setting up KernelCI VM ==== | ||
| Line 22: | Line 24: | ||
| ''[user@host Downloads] $ **sudo dpkg -i virtualbox-5.1_5.1.8-111374-Ubuntu-xenial_amd64.deb**'' | ''[user@host Downloads] $ **sudo dpkg -i virtualbox-5.1_5.1.8-111374-Ubuntu-xenial_amd64.deb**'' | ||
| - | 3. Get the CIP KernelCI Project | + | 3. Get the CIP KernelCI Project (*Needs updating to new repo with merged VMs) |
| ''[user@host ~/git] $ **git clone [[https://gitlab.com/cip-project/testing.git]]**'' | ''[user@host ~/git] $ **git clone [[https://gitlab.com/cip-project/testing.git]]**'' | ||
| - | 4. Change to the testing directory | + | 4. Change to the testing directory (*This directory name will be different too) |
| ''[user@host ~/git] $ **cd testing**'' | ''[user@host ~/git] $ **cd testing**'' | ||
| Line 51: | Line 53: | ||
| 8. Clone the CIP Linux Kernel | 8. Clone the CIP Linux Kernel | ||
| - | ''vagrant@guest:~/git-repos$ **git clone [[https://gitlab.com/cip-project/linux-cip.git]]**'' | + | ''vagrant@guest:~/git-repos$ **git clone [[git://git.kernel.org/pub/scm/linux/kernel/git/bwh/linux-cip.git]]**'' |
| 9. Find the branch of the kernel version you want (i.e. 4.4.27) | 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$ **cd linux-cip**'' |
| - | ''vagrant@guest:~/git-repos/linux-stable$ **git tag -l | grep 4.4.y**'' | + | ''vagrant@guest:~/git-repos/linux-cip$ **git tag -l | grep 4.4.y**'' |
| 10. Create a new branch using that tag. | 10. Create a new branch using that tag. | ||
| - | ''vagrant@guest:~/git-repos/linux-stable$ **git checkout -b cip_v4.4.27 v4.4.27**'' | + | ''vagrant@guest:~/git-repos/linux-cip$ **git checkout -b cip_v4.4.27 v4.4.27**'' |
| Line 68: | Line 70: | ||
| 11. Set the environment variables | 11. Set the environment variables | ||
| - | ''vagrant@guest:~/git-repos/linux-stable$ **export TREE_NAME=cip-test**'' | + | ''vagrant@guest:~/git-repos/linux-cip$ **export TREE_NAME=cip-test**'' |
| - | ''vagrant@guest:~/git-repos/linux-stable$ **export ARCH=arm**'' | + | ''vagrant@guest:~/git-repos/linux-cip$ **export ARCH=arm**'' |
| - | ''vagrant@guest:~/git-repos/linux$ **export CROSS_COMPILE=arm-linux-gnueabi-**'' | + | ''vagrant@guest:~/git-repos/linux-cip$ **export CROSS_COMPILE=arm-linux-gnueabi-**'' |
| //Note: Don't forget the dash (-) at the end of the ''CROSS_COMPILE'' line!// | //Note: Don't forget the dash (-) at the end of the ''CROSS_COMPILE'' line!// | ||
| Line 78: | Line 80: | ||
| 12. Execute the build.py command | 12. Execute the build.py command | ||
| - | ''vagrant@guest:~/git-repos/linux-stable$ **~/kernelci-build/build.py -c tinyconfig -p CIP-KernelCI**'' | + | ''vagrant@guest:~/git-repos/linux-cip$ **~/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: | 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: | ||
| Line 88: | Line 90: | ||
| ''**http://localhost:5000**'' | ''**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 Optional Exercises below) | + | 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-homepage.png?nolink&600 |}} | + | {{ :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'' | ||
| - | ==== Optional Exercises ==== | ||
| - | 1. Make some Alternate Trees | + | ==== Example Builds ==== |
| - | ''vagrant@guest:~/git-repos/linux-stable$ **export TREE_NAME=cip-tyrannosaurus**'' | + | 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. |
| - | ''vagrant@guest:~/git-repos/linux-stable$ **export TREE_NAME=cip-stegosaurus**'' | + | * TREE_NAME=cip-tyrannosaurus |
| + | * tinyconfig | ||
| + | * allnoconfig | ||
| - | 2. Build Alternate Configurations | + | * TREE_NAME=cip-stegosaurus |
| + | * sunxi_defconfig | ||
| + | * axm55xx_defconfig | ||
| - | ''vagrant@guest:~/git-repos/linux-stable$ **~/kernelci-build/build.py -c allnoconfig -p CIP-KernelCI**'' | + | * TREE_NAME=cip-triceratops |
| + | * tinyconfig | ||
| + | * allnoconfig | ||
| - | ''vagrant@guest:~/git-repos/linux-stable$ **~/kernelci-build/build.py -c sunxi_defconfig -p CIP-KernelCI**'' | ||
| [[ciptesting|Back to the parent page]] | [[ciptesting|Back to the parent page]] | ||
civilinfrastructureplatform/testingkernelcivmsetup.txt · Last modified: 2017/02/19 01:33 by Agustin Benito Bethencourt
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
