aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/images
AgeCommit message (Collapse)Author
2018-11-07build-appliance-image: Update to rocko head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-05-23build-appliance-image: Update to rocko head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-14build-appliance-image: Update to rocko head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-06image-live.bbclass: add MLPREFIX to core-image-minimal-initramfsRobert Yang
The 32bit core-image-minimal-initramfs should be built when build lib32-iso, e.g.: MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" IMAGE_FSTYPES += "iso" $ bitbake lib32-core-image-minimal Exception: FileExistsError: [Errno 17] File exists: '/path/to/tmp/sysroots-components/core2-64/qemuwrapper-cross/usr/bin/crossscripts/qemuwrapper' -> '/path/to/tmp/work/qemux86_64-pokymllib32-linux/lib32-core-image-minimal/1.0-r0/lib32-recipe-sysroot/usr/bin/crossscripts/qemuwrapper' This was because: lib32-core-image-minimal -> core-image-minimal-initramfs core-image-minimal-initramfs -> qemuwrapper-cross lib32-core-image-minimal -> lib32-qemuwrapper-cross So we got the error, build lib32-core-image-minimal-initramfs can fix the problem. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> (cherry picked from commit eee3ec805cf150f1c701427a2d182a537a67e8f5) Signed-off-by: Armin Kuster <akuster808@gmail.com>
2017-12-09build-appliance: Fix branch nameRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-07build-appliance-image: Update to rocko head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-09-22core-image-tiny-initramfs: Enable running poky-tiny on qemux86-64Alejandro Hernandez
Building poky-tiny for x86-64 seems fine, but when executing qemu it complains during boot time about not being able to execute init: [ 5.409730] Failed to execute /init (error -8) And then it drops to a login prompt (which it should't do on tiny) This is supposed to be complaining about init's format, it only happens on x86-64 architectures so perhaps is a 32/64 bit issue, but since core-image-tiny-initramfs does not actually provide a traditional init, the script is simply meant to drop to shell, we can workaround the issue by specifying the kernel to run the init script via busybox's sh, dropping to shell correctly on x86-64 leaving x86 unaffected. Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-09-21core-image-tiny-initramfs: initramfs recipes should not generate an actual ↵Alejandro Hernandez
image file core-image-tiny-initramfs was used to generate a wic image, which was conceptually wrong since initrafms recipes should only generate the boot artifacts that can later be used by another recipe to generate an image using the tool of their choice. Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-08-23build-appliance-image: include proxy on pip3 installationLeonardo Sandoval
Otherwise, we get timeouts, leading to errors: pip._vendor.requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='pypi.python.org', port=443): Max retries exceeded with url: /pypi/pip/json (Caused by ConnectTimeoutError(<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7ff741bb3ef0>, 'Connection to pypi.python.org timed out. (connect timeout=5)')) WARNING: TOPDIR/tmp/work/qemux86-poky-linux/build-appliance-image/15.0.0-r0/temp/run.do_populate_poky_src.185123:1 exit 1 from 'pip3 install --user -I -U -v -r TOPDIR/tmp/work/qemux86-poky-linux/build-appliance-image/15.0.0-r0/rootfs/home/builder/poky/bitbake/toaster-requirements.txt' DEBUG: Python function do_image finished Complete log at [1] [1] http://errors.yoctoproject.org/Errors/Build/43393/ Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-18build-appliance-image: Don't use COREBASE/LICENSE for checksummingSaul Wold
This file lists the licenses that the OE-Core meta data falls under but should not be used as a LIC_FILES_CHKSUM, use the MIT license file. Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-07-30image: Convert vmdk/vdi/qcow2 to strict CONVERSION_CMD typesTom Rini
The vmdk/vdi/qcow2 IMAGE_FSTYPEs predate wic. As such, they provide some similar underlying functionality in order to produce a "disk" image that in turn can be converted into different formats that various hypervisor types work with. They do not however provide the ability for other disk image types to be converted into these same output types. Furthermore, they are less flexible than what wic does provide. This drops the old style vmdk/vdi/qcow2 types and re-introduces them under the CONVERSION_CMD framework. The equivalent of vmdk is now wic.vmdk and so forth for the other types. Signed-off-by: Tom Rini <trini@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-07-30Revert "core-image-minimal-initramfs: use initramfs-framework by default"Richard Purdie
This reverts commit 28fc6ba761ed4a47efa7c43e7f7dff5e2fe72b5e since it causes runqemu.RunqemuTests.test_boot_machine_iso and runqemu.RunqemuTests.test_boot_deploy_hddimg to fail in oe-selftest.
2017-07-27core-image-minimal-initramfs: use initramfs-framework by defaultuninative-1.7Ng, Wei Tee
Use the initramfs-framework for initialization by default due to the modularity and expansibility. [YOCTO #10987] Signed-off-by: Ng, Wei Tee <wei.tee.ng@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-05-01build-appliance-image: Update to master head revisionyocto-2.32017-04-pyro2017-04Richard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-04-29build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-04-29build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-04-21build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-04-20build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-04-20build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-16build-appliance-image: ensure pod2man present in BAJuro Bystricky
"pod2man" went missing from BA, but it is required. This patch fixes the Toaster error: <...> ERROR: These tools appear to be unavailable in PATH, please install them in order to proceed: pod2man <...> [YOCTO#11144] Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-16build-appliance-image: fix build errorsJuro Bystricky
Remove any symlinks before creating new ones to avoid potential build errors such as: FileExistsError: [Errno 17] File exists: '../../usr/src/kernel' -> ... ' Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-16build-appliance-image: use pip3-nativeJuro Bystricky
Do not rely on pip3 being installed on the host. Use pip3-native instead. [YOCTO#10909] [YOCTO#11022] Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-13run-postinsts: simplify the logic of whether to install it to imagesAlexander Kanavin
The logic is scattered all over the place, but amounts to "install, unless the rootfs is read only". Let's express that directly. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-02-01build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-01-31core-image-tiny-initramfs: Fix error message shown after a successful initrd ↵Alejandro Hernandez
boot When booting core-image-tiny-initramfs, since we want to live on initrd, on purpose, we never find a rootfs image to switch root to, this causes init to show an error as it would with other images, this patch replaces the message shown to the user, avoiding confusion when it was indeed a successful boot. Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
2017-01-31core-image-tiny-initramfs: Add and image creating image artifacts onlyTom Zanussi
Add an image that simply creates image artifacts using image-live-artifacts support instead of creating an actual image. The image artifacts can then be subsequently assembled by an external tool such as wic to create an actual image. This eliminates redundant image creation when using such tools. Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
2017-01-23build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-01-16build-appliance-image: support for ToasterJuro Bystricky
Various changes needed to enable to run Toaster in the Build Appliance: 1. Pre-install packages as specified by the file "bitbake/toaster-requirements.txt" 2. Include pip3 in the image 3. Include tzdata in the image (needed by django) 4. Bump SRCREV to a commit with proper settings.py (ALLOWED_HOSTS) for Django 1.8.16 5. Added README_VirtualBox_Toaster.txt to provide steps for configuring VirtualBox network adapters (NAT or Bridged) and steps to launch Toaster [YOCTO#10767] Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-11-06build-appliance-image: Fix incorrect PATHJuro Bystricky
When modifying the PATH variable in .bashrc, double quote characters were used, resulting in expanding the variable $PATH with the value of PATH of the system building the Build Appliance. The original intent was to enter an un-expanded (literal) $PATH. In order to that, one must use single quotes instead of double quotes. [YOCTO#10434] [YOCTO#10504] Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-10-26build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-10-25build-appliance-image: add /sbin to PATHJuro Bystricky
runqemu script fails with an error when executed in Build Appliance. Typical use case: $ bitbake core-image-minimal $ runqemu qemux86 Observed error: runqemu - ERROR - In order for this script to dynamically infer paths ...snip... runqemu-ifup, runqemu-ifdown or ip not found The error is caused by the fact that "ip" is located in /sbin, however /sbin is not in user's ("builder") PATH. To fix this we add /sbin to PATH. The simplest place to do this is in user's .bashrc. [YOCTO#10434] Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-10-15build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-10-11build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-10-11build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-10-11build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-19build-appliance-image: Create image in correct locationJuro Bystricky
Due to the recipe now using variable IMGDEPLOYDIR instead of DEPLOY_DIR_IMAGE, the final Build Appliance image ended up being created in a wrong location. This patch assures the final ZIP image is created in identical location as before: tmp/deploy/images/<machine>/Yocto_Build_Apliance.zip [YOCTO#10274] Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-04image: Deploy images to IMGDEPLOYDIREd Bartosh
Changed deployment directory from DEPLOY_DIR_IMAGE to IMGDEPLOYDIR to make sstate machinery to do final deployment and generate manifest. Renamed variable deploy_dir to deploy_dir_image in selftest code to avoid confusion with DEPLOYDIR variable. Updated the code of rootfs.py:Rootfs class to use IMGDEPLOYDIR variable as it's now used as a new deployment destination. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-21build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-21build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-16build-appliance-image: Add LC_ALL setting and drop pseudo piecesRichard Purdie
The pseudo pieces here date from times gone by when bitbake ran in two phases. Its long since obsolete and can be dropped. Also set LC_ALL so that bitbake works correctly and uses the local we're already installing into the image so we have utf-8 available. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-16build-appliance-image: Install network componentsJuro Bystricky
Explicitly add network components into Build Appliance image, do not rely on packagegroup-self-hosted to pull them in. Network related dependencies were removed from packagegroup-self-hosted. YOCTO #9758 Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-16build-appliance-image: Update to master head revisionRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-03build-appliance-image: update version to 15.0.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-22core-image-{minimal, testmaster}-initramfs: set COMPATIBLE_HOSTMartin Jansa
* use the same COMPATIBLE_HOST restriction as initramfs-live-install(-testfs) to resolve ugly error when trying to build them e.g. for ARM: ERROR: Nothing RPROVIDES 'initramfs-live-install-testfs' (but /home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-extended/images/core-image-testmaster-initramfs.bb RDEPENDS on or otherwise requires it) ERROR: initramfs-live-install-testfs was skipped: incompatible with host arm-oe-linux-gnueabi (not in COMPATIBLE_HOST) NOTE: Runtime target 'initramfs-live-install-testfs' is unbuildable, removing... Missing or unbuildable dependency chain was: ['initramfs-live-install-testfs'] ERROR: Required build target 'core-image-testmaster-initramfs' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-testmaster-initramfs', 'initramfs-live-install-testfs'] ERROR: Nothing RPROVIDES 'initramfs-live-install' (but /home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-core/images/core-image-minimal-initramfs.bb RDEPENDS on or otherwise requires it) ERROR: initramfs-live-install was skipped: incompatible with host arm-oe-linux-gnueabi (not in COMPATIBLE_HOST) NOTE: Runtime target 'initramfs-live-install' is unbuildable, removing... Missing or unbuildable dependency chain was: ['initramfs-live-install'] ERROR: Required build target 'core-image-minimal-initramfs' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal-initramfs', 'initramfs-live-install'] Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-05-21build-appliance-image: use 'lnr' instead of 'ln -sr'Ming Liu
For portability, not all hosts are running sufficiently new coreutils. Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-19kernel: moves KERNEL_SRC_PATH to bitbake.confMing Liu
"/usr/src/kernel" is being hard-coded in multiple recipes so far, move its definition to bitbake.conf. Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-04-29build-appliance: Switch to master branch post releaseRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-04-19build-appliance-image: Update to krogoth head revisionyocto-2.12016-42016-04-krogothRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-04-18build-appliance-image: Load TUN at startupJuro Bystricky
This patch addresses the issue of not being able to execute "runqemu" in the Build Appliance. The root cause of the problem was that TAP/TUN was not available, although required by "runqemu". In addition, the recommended remedy $ sudo modprobe tun would fail for two reasons: modprobe not in PATH (user builder), and "iptables" located in /usr/sbin but expected in /sbin. [YOCTO #9437] Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-04-18images: zero out the rootfs_extra_space in initramfs imagesStephano Cetola
Setting IMAGE_ROOTFS_EXTRA_SPACE impacts the initramfs images, results in an error about INITRAMFS_MAXSIZE. Signed-off-by: Stephano Cetola <stephano.cetola@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>