Bug 6815 - Yocto image qemuppc do not boot and OS not load
Summary: Yocto image qemuppc do not boot and OS not load
Status: CLOSED NOTABUG
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 1.7
Hardware: Other ppc
: Medium+ major
Target Milestone: 1.7 M4
Assignee: Cristian Iorga
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-10-07 13:32 UTC by Andra Necula
Modified: 2014-10-22 11:51 UTC (History)
8 users (show)

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


Attachments
Yocto image qemuppc do not boot and OS not load (75.60 KB, image/jpeg)
2014-10-07 13:32 UTC, Andra Necula
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andra Necula 2014-10-07 13:32:18 UTC
Created attachment 2172 [details]
Yocto image qemuppc do not  boot and OS not load

Host Ubuntu 14.04 tested on 64 bits and 32 bits

Reproducing steps:
1) download qemuppc from autobuilder 
http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc3/machines/qemu/qemuppc/
2) build environmemt
 build oe-init-build-env
3) start qemuppc
  runqemu qemuppc or runqemu qemuppc core-image-sato-sdk or using the image path

Expecting output: Yocto image should boot and OS load 
  
The actual output:Qemu starts, but the qemu window is completely white.

The bug reproduce on Ubuntu 14.04 64 bits and 32 bits, but on Fedora qemuppc works perfectly fine
Comment 1 Cristian Iorga 2014-10-16 13:22:53 UTC
Hi Andra,
Can you please re-test this issue on the latest release candidate?

Thanks,
Cristian
Comment 2 Mihail Stanciu 2014-10-21 14:50:55 UTC
Both sato and sato-sdk images exhibit this behaviour on RC5: 924da20c6f2f183fa7e930e4c3c6b14c090acbe5

Please note that this only happens with downloaded images from AB. 
On previous tests, if we built an image locally it worked perfectly. Have not built a local image on RC5 yet, but suspect behaviour still present.

Same as before, this only happens on Ubuntu 14.04 machines; on Fedora the AB image works.
Comment 3 Mihail Stanciu 2014-10-21 15:04:27 UTC
Cristian has confirmed that using a locally built image works for RC5.

This suggests an issue with AB, in my opinion.
Comment 4 Yi Zhao 2014-10-22 07:24:58 UTC
I can not reproduce this issue on my ubuntu 14.04 x86-64.
Here are the steps:
1. download qemuppc image from ab: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc5
2. build poky environment
   source oe-init-build-env
   bitbake meta-ide-support

3. launch the qemuppc
   runqemu qemuppc  ~/qemuppc/vmlinux--3.14.19+git0+fb6271a942_73e2411cdd-r0-qemuppc-20141016220152.bin  ~/qemuppc/core-image-sato-sdk-qemuppc-20141018182036.rootfs.ext3

The system can boot without problem and the GUI is good.
Comment 5 Mihail Stanciu 2014-10-22 11:50:21 UTC
Not a bug.
Further research after Yi's comment revealed we were missing a required step when using pre-built images to run qemu.
Comment 6 Mihail Stanciu 2014-10-22 11:51:00 UTC
Closing.