Bug 10465

Summary: devtool runqemu can not launch the qemu image
Product: [Yocto Project Subprojects] eSDK Reporter: Yi Zhao <yi.zhao>
Component: eSDKAssignee: Paul Eggleton <bluelightning>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Undecided CC: humberto.ibarra.lopez, jose.perez.carranza, yi.zhao
Version: 2.2   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)

Description Yi Zhao 2016-10-20 01:53:22 UTC 
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!
################################
Comment 1 Paul Eggleton 2016-10-20 01:55:43 UTC 
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 ***
Comment 2 Yi Zhao 2016-10-20 02:32:08 UTC 
(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.
Comment 3 Paul Eggleton 2016-10-20 02:44:04 UTC 
No problem :)