11193 2017-03-21 00:18:33 +0000 runqemu can not launch image if enable "rm_work" 2017-04-10 21:08:09 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 2.3 x86 Multiple RESOLVED DUPLICATE 11266 High normal 2.3 M4 1 yi.zhao Qi.Chen eduard.bartosh jose.perez.carranza poky.bs.watcher poky.watcher Qi.Chen ross.burton --- Regression (Used to work) No (bug/feature does not impact docs) oldest_to_newest 71495 0 yi.zhao 2017-03-21 00:18:33 +0000 Git rev: master/6e20b31d5d17133e0fca086e12a0ad06ab5c4cc8 Steps: 1. Download the poky source and set environment. 2. Add INHERIT += "rm_work" to conf/local.conf 3. bitbake core-image-minimal 4. runqemu qemuarm Error message: #################################### $ runqemu qemuarm runqemu - INFO - Assuming MACHINE = qemuarm runqemu - INFO - Running MACHINE=qemuarm bitbake -e... runqemu - INFO - MACHINE: qemuarm runqemu - INFO - DEPLOY_DIR_IMAGE: /buildarea/poky/build-test/tmp/deploy/images/qemuarm runqemu - INFO - Running ls -t /buildarea/poky/build-test/tmp/deploy/images/qemuarm/*.qemuboot.conf... runqemu - INFO - CONFFILE: /buildarea/poky/build-test/tmp/deploy/images/qemuarm/core-image-minimal-qemuarm-20170320051519.qemuboot.conf runqemu - INFO - Overriding conf file setting of STAGING_DIR_NATIVE to /buildarea/poky/build-test/tmp/work/armv5e-poky-linux-gnueabi/defaultpkgname/1.0-r0/recipe-sysroot-native from Bitbake environment runqemu - INFO - Overriding conf file setting of STAGING_BINDIR_NATIVE to /buildarea/poky/build-test/tmp/work/armv5e-poky-linux-gnueabi/defaultpkgname/1.0-r0/recipe-sysroot-native/usr/bin from Bitbake environment runqemu - INFO - Continuing with the following parameters: KERNEL: [/buildarea/poky/build-test/tmp/deploy/images/qemuarm/zImage--4.10.2+git0+69bfa87234_ad30e5e8b9-r0-qemuarm-20170320051519.bin] DTB: [/buildarea/poky/build-test/tmp/deploy/images/qemuarm/zImage-versatile-pb.dtb] MACHINE: [qemuarm] FSTYPE: [ext4] ROOTFS: [/buildarea/poky/build-test/tmp/deploy/images/qemuarm/core-image-minimal-qemuarm-20170320051519.rootfs.ext4] CONFFILE: [/buildarea/poky/build-test/tmp/deploy/images/qemuarm/core-image-minimal-qemuarm-20170320051519.qemuboot.conf] runqemu - INFO - Running /sbin/ip link... runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap1.lock... runqemu - INFO - Using preconfigured tap device tap1 runqemu - INFO - If this is not intended, touch /tmp/qemu-tap-locks/tap1.skip to make runqemu skip tap1. runqemu - INFO - QEMU binary not found in /buildarea/poky/build-test/tmp/work/armv5e-poky-linux-gnueabi/defaultpkgname/1.0-r0/recipe-sysroot-native/usr/bin/qemu-system-arm, trying host's QEMU runqemu - INFO - Trying: /buildarea/poky/scripts/qemu-system-arm runqemu - INFO - Trying: /buildarea/poky/bitbake/bin/qemu-system-arm runqemu - INFO - Trying: /home/zhaoyi/bin/qemu-system-arm runqemu - INFO - Trying: /usr/local/sbin/qemu-system-arm runqemu - INFO - Trying: /usr/local/bin/qemu-system-arm runqemu - INFO - Trying: /usr/sbin/qemu-system-arm runqemu - INFO - Trying: /usr/bin/qemu-system-arm runqemu - INFO - Trying: /sbin/qemu-system-arm runqemu - INFO - Trying: /bin/qemu-system-arm runqemu - INFO - Trying: /usr/games/qemu-system-arm runqemu - INFO - Trying: /usr/local/games/qemu-system-arm runqemu - INFO - Trying: /snap/bin/qemu-system-arm runqemu - INFO - Releasing lockfile for tap device 'tap1' runqemu - ERROR - In order for this script to dynamically infer paths kernels or filesystem images, you either need bitbake in your PATH or to source oe-init-build-env before running this script. Dynamic path inference can be avoided by passing a *.qemuboot.conf to runqemu, i.e. `runqemu /path/to/my-image-name.qemuboot.conf` No QEMU binary '/buildarea/poky/build-test/tmp/work/armv5e-poky-linux-gnueabi/defaultpkgname/1.0-r0/recipe-sysroot-native/usr/bin/qemu-system-arm' could be found ######################################## The runqemu try to fine the qemu-system-arm in "defaultpkgname" directory, but there is no such directory. This issue only happens when enable rm_work feature. 72254 1 eduard.bartosh 2017-04-10 21:08:09 +0000 this is duplicate for bug 11266 *** This bug has been marked as a duplicate of bug 11266 ***