10465 2016-10-20 01:53:22 +0000 devtool runqemu can not launch the qemu image 2017-12-06 17:12:40 +0000 1 1 6 Yocto Project Subprojects eSDK eSDK 2.2 x86 Multiple RESOLVED DUPLICATE 10447 Undecided normal --- 1 yi.zhao bluelightning humberto.ibarra.lopez jose.perez.carranza yi.zhao --- Regression (Used to work) No (bug/feature does not impact docs) oldest_to_newest 67398 0 yi.zhao 2016-10-20 01:53:22 +0000 Git rev: morty/4b94b498e21aeba945fe7e72a6b7c4bb0314fb83 Steps: 1. Build and install eSDK: $ bitbake core-image-sato -c populate_sdk_ext 2. Build an image $ devtool build-image 3. Boot up the image $ devtool runqemu Error message: ################################# $ devtool runqemu runqemu - INFO - Assuming MACHINE = qemux86-64 runqemu - INFO - Can't find qemuboot conf file, DEPLOY_DIR_IMAGE is NULL! runqemu - INFO - Running MACHINE=qemux86-64 bitbake -e... runqemu - INFO - Overriding conf file setting of STAGING_DIR_NATIVE to /buildarea1/poky_sdk_core2-64/tmp/sysroots/x86_64-linux from Bitbake environment runqemu - INFO - Overriding conf file setting of STAGING_BINDIR_NATIVE to /buildarea1/poky_sdk_core2-64/tmp/sysroots/x86_64-linux/usr/bin from Bitbake environment Traceback (most recent call last): File "/buildarea1/poky_sdk_core2-64/layers/poky/scripts/runqemu", line 1019, in <module> ret = main() File "/buildarea1/poky_sdk_core2-64/layers/poky/scripts/runqemu", line 1007, in main config.check_and_set() File "/buildarea1/poky_sdk_core2-64/layers/poky/scripts/runqemu", line 559, in check_and_set self.check_fstype() File "/buildarea1/poky_sdk_core2-64/layers/poky/scripts/runqemu", line 451, in check_fstype raise Exception("FSTYPE is NULL!") Exception: FSTYPE is NULL! ################################ 67399 1 bluelightning 2016-10-20 01:55:43 +0000 Thanks, but this was already identified in bug 10447. There's a patch on the mailing list to resolve it. *** This bug has been marked as a duplicate of bug 10447 *** 67401 2 yi.zhao 2016-10-20 02:32:08 +0000 (In reply to comment #1) > Thanks, but this was already identified in bug 10447. There's a patch on the > mailing list to resolve it. > > *** This bug has been marked as a duplicate of bug 10447 *** Sorry, I didn't notice it. 67402 3 bluelightning 2016-10-20 02:44:04 +0000 No problem :)