| Summary: |
New Qemu can not be launched from eclipse |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
brian avery <brian.avery> |
| Component: |
Scripts and Tools | Assignee: |
Joshua Lock <joshuagloe> |
| Status: |
VERIFIED
FIXED
|
QA Contact: |
Humberto Ibarra <humberto.ibarra.lopez> |
| Severity: |
normal
|
|
|
| Priority: |
Undecided
|
CC: |
humberto.ibarra.lopez, jose.perez.carranza, ross.burton, tim.orling
|
| Version: |
2.2 | |
|
| Target Milestone: |
--- | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
| Bug Depends on: |
|
|
|
| Bug Blocks: |
10214
|
|
|
| Attachments: |
|
Created attachment 3429 [details] runqemu failure in eclipse sdk env. Eclipse launches qemu from a randomish directory and it has only access to whatever vars are in environment-setup-XXXX-poky-linux. Here's a way to check if runqemu can work w/out using eclipse: Build what Eclipse needs: 1 bitbake core-image-sato-sdk && bitbake core-image-sato-sdk -c populate_sdk && bitbake meta-ide-support From a clean bash shell w/ no bitbake env vars set do: 1 mkdir /tmp/cow;cd /tmp/cow 2 source <path to tmpdir>/environment-setup-i586-poky-linux 3 runqemu-extract-sdk <path to tmpdir>/deploy/images/qemux86/core-image-sato-sdk-qemux86.tar.bz2 QEMU_ROOTFS 4 runqemu qemux86 <path to tmpdir>/deploy/images/qemux86/bzImage /tmp/cow/QEMU_ROOTFS Ideally this would work. This represents a shell with no knowledge other than what is in the environment-setup script and is in a directory that has no bblayers.conf hidden underneath it. This is what Eclipse is doing since it runs this from the eclipse workspace. The runqemu-extract-sdk makes a userspace nfs mountable filesystem with pseudo support. Attaching the failed result which says "no bblayers.conf found"