Bug 5669 - Check if the directfb image can be built - rootfs is missing in tmp/deploy/images/qemuarm
Summary: Check if the directfb image can be built - rootfs is missing in tmp/deploy/im...
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.5.1
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.5.2
Assignee: Robert Yang
QA Contact: Ionut Chisanovici
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-12-16 12:33 UTC by Ionut Chisanovici
Modified: 2015-08-07 13:51 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ionut Chisanovici 2013-12-16 12:33:23 UTC 
STATUS: RUNNING
BUILD: 1.5.1: 8e410e9e46e3335458a7747cdd32e05f5c19ccbb
ENVIRONMENT: Multiple environments
STEPS TO REPRODUCE: 
1. Download poky source and prepare the build environment
2. Set MACHINE to qemuarm in conf/local.conf
3. Remove "x11" from DISTRO_FEATURES in meta/conf/distro/include/default-distrovars.inc, use "directfb" instead of it:
    DISTRO_FEATURES ?= "alsa argp bluetooth ext2 irda largefile pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g directfb ${DISTRO_FEATURES_LIBC}"
4. Run "bitbake core-image-directfb" to build a directfb image

EXPECTED OUTCOME: The directfb image can be built.

ACTUAL OUTCOME: image is successfully built but the rootfs image is missing

[ionut@ionut-fedora build]$ ll tmp/deploy/images/qemuarm/
total 280268
-rw-r--r-- 1 ionut ionut 237705216 Dec 16 14:19 core-image-directfb-qemuarm-20131216110624.rootfs.ext3
-rw-r--r-- 1 ionut ionut  70604582 Dec 16 14:18 core-image-directfb-qemuarm-20131216110624.rootfs.tar.bz2
lrwxrwxrwx 1 ionut ionut        54 Dec 16 14:19 core-image-directfb-qemuarm.ext3 -> core-image-directfb-qemuarm-20131216110624.rootfs.ext3
lrwxrwxrwx 1 ionut ionut        57 Dec 16 14:19 core-image-directfb-qemuarm.tar.bz2 -> core-image-directfb-qemuarm-20131216110624.rootfs.tar.bz2
-rw-rw-r-- 2 ionut ionut  26726668 Dec 16 14:14 modules--3.10.17+git0+6ad20f049a_5714b747cf-r0-qemuarm-20131216110624.tgz
lrwxrwxrwx 2 ionut ionut        73 Dec 16 14:14 modules-qemuarm.tgz -> modules--3.10.17+git0+6ad20f049a_5714b747cf-r0-qemuarm-20131216110624.tgz
-rw-rw-r-- 2 ionut ionut       294 Dec 16 14:18 README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt
lrwxrwxrwx 2 ionut ionut        72 Dec 16 14:14 zImage -> zImage--3.10.17+git0+6ad20f049a_5714b747cf-r0-qemuarm-20131216110624.bin
-rw-r--r-- 2 ionut ionut   4049304 Dec 16 14:14 zImage--3.10.17+git0+6ad20f049a_5714b747cf-r0-qemuarm-20131216110624.bin
lrwxrwxrwx 2 ionut ionut        72 Dec 16 14:14 zImage-qemuarm.bin -> zImage--3.10.17+git0+6ad20f049a_5714b747cf-r0-qemuarm-20131216110624.bin
[ionut@ionut-fedora build]$ runqemu qemuarm
Couldn't find a qemuarm rootfs image in /home/ionut/work/poky/build/tmp/deploy/images/qemuarm.

Cheers,
IonutC
Comment 1 Ionut Chisanovici 2013-12-16 12:47:08 UTC 
Forgot to mention the build env:

Build Configuration:
BB_VERSION        = "1.20.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-19"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "qemuarm"
DISTRO            = "poky"
DISTRO_VERSION    = "1.5.1"
TUNE_FEATURES     = "armv5 thumb dsp"
TARGET_FPU        = "soft"
meta              
meta-yocto        
meta-yocto-bsp    = "dora:8e410e9e46e3335458a7747cdd32e05f5c19ccbb"
Comment 2 Saul Wold 2013-12-17 19:28:50 UTC 
Huh, this is the rootfs image right here: 
-rw-r--r-- 1 ionut ionut 237705216 Dec 16 14:19 
core-image-directfb-qemuarm-20131216110624.rootfs.ext3
lrwxrwxrwx 1 ionut ionut        54 Dec 16 14:19 
core-image-directfb-qemuarm.ext3-> 
core-image-directfb-qemuarm-20131216110624.rootfs.ext3

what do you think is missing?
Comment 3 Ionut Chisanovici 2013-12-18 08:28:42 UTC 
(In reply to comment #2)
> Huh, this is the rootfs image right here: 
> -rw-r--r-- 1 ionut ionut 237705216 Dec 16 14:19 
> core-image-directfb-qemuarm-20131216110624.rootfs.ext3
> lrwxrwxrwx 1 ionut ionut        54 Dec 16 14:19 
> core-image-directfb-qemuarm.ext3-> 
> core-image-directfb-qemuarm-20131216110624.rootfs.ext3
> 
> what do you think is missing?

I saw that too but runqemu is unable to lunch the image.

[ionut@ionut-fedora build]$ runqemu qemuarm
Couldn't find a qemuarm rootfs image in /home/ionut/work/poky/build/tmp/deploy/images/qemuarm.

So is this an issue or not ?
Comment 4 Alexandru Georgescu 2013-12-19 13:59:42 UTC 
(In reply to comment #2)
> Huh, this is the rootfs image right here: 
> -rw-r--r-- 1 ionut ionut 237705216 Dec 16 14:19 
> core-image-directfb-qemuarm-20131216110624.rootfs.ext3
> lrwxrwxrwx 1 ionut ionut        54 Dec 16 14:19 
> core-image-directfb-qemuarm.ext3-> 
> core-image-directfb-qemuarm-20131216110624.rootfs.ext3
> 
> what do you think is missing?

Hi Saul,
I think the description is a little misleading.
Ionut could build the qemuarm, and the rootfs was created as shown in his "ll" command. The issue he is facing is that the command "runqemu qemuarm" without specifying what type of image is doesn't start and it gives the error that the rootfs is missing.

For the record, I tried with a qemux86 and I don't have this issue (tested on DORA).
Comment 5 Saul Wold 2013-12-19 15:39:19 UTC 
There is a patch in master for runqemu that could be backported:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=fc0bb31aa73b8105206c58dff66297c8fb1d2b3b
Comment 6 Robert Yang 2013-12-20 01:57:09 UTC 
(In reply to comment #5)
> There is a patch in master for runqemu that could be backported:
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/
> ?id=fc0bb31aa73b8105206c58dff66297c8fb1d2b3b

Hi Saul, thanks, I will add it.

// Robert
Comment 8 Ionut Chisanovici 2014-02-27 11:17:21 UTC 
This has been verified with 81f4de35fcfb748867d55c66330345183dd5473e and the issue is fixed.

Cheers,
Ionut C