Unable to boot OpenBMC image in QEMU for AST2500

[Stephen Beckwith]

Mr. Geissler;
    Thank you for your comments/suggestion.
1)  I fetched the version referenced in the document.  This replaced the
installed version in /usr/bin on the host system.  The previous version was
12MB and version was:
sbeckwit at ubuntu:~/yocto_dev/openbmc-master/build$ qemu-system-arm.old
-version
QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.18)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
 - the “new” version installed is 65MB and is version:
sbeckwit at ubuntu:~/yocto_dev/openbmc-master/build$ sudo qemu-system-arm
--help
QEMU emulator version 4.1.0 (v4.0.0-rc1-2953-g0d7c1ec-dirty)
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
 -  The “new” version did not work either.
2) Per the command line arguments being passed to qemu-system-arm, the copy
of this is a “built” copy as part of the openbmc build process, located in
the following directory and is the newer version:
sbeckwit at ubuntu:~/yocto_dev/openbmc-master/build/tmp/work/qemuarm-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/recipe-sysroot-native/usr/bin$
./qemu-system-arm -version
QEMU emulator version 4.1.0
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
3) My initial build of the openbmc project was to “bake” the “meta-aspeed”
- per some information/notes I found in the openbmc documentation.  (it
also said you needed to source the setup script to set this up - which I
did).  So stepping back, maybe this was the wrong target to build.   So I
spend another 2 hrs, 32 minutes “baking” the “meta-evb”, the rational being
that maybe the first image was missing something required by qemu (i.e.
some boot/driver stuff??).   After this was built, and using the “runqemu”
script, alas, the same result:  qemu will not boot and run the image.


Mr. Jeffery;
   Thank you for your comments/suggestion, I will work on this approach
today.  Regarding your question:
1)  re: cloning - I received an “access denied” message, eventhough I was
logged into gihub (using my personal account information).  Therefore, used
a zipped version that was downloaded ~ 1 week ago.

2) re: qemu machine - the qemu machine being used is the one that was built
as part fo the opembmc project.  If this qemu machine won’t work, then why
is it built as part of the project?  Why are there 13 copies of this
machine scattered through out the filesystem, consuming ~ 564MB of space,
if it’s the “wrong” machine?
 - so where do I obtain the “BMC-specific machine” ?  The one I installed
per Mr. Geissler?

3) if OpenBMC doesn’t properly integrate into the rumqemu scripts, then:
 A) why is this script here? B) why hasn’t anyone taken the time/effort to
correct the script so that it will integrate properly with OpenBMC?

4)  I will review the information in the link provided in your response.
Thank you.

Regards,
Stephen Beckwith

On Wed, Sep 25, 2019 at 12:28 AM Andrew Jeffery <andrew at aj.id.au> wrote:

>
>
> On Tue, 24 Sep 2019, at 06:16, Stephen Beckwith wrote:
> > Greetings,
> >  I am working on a Proof-of-Concept for OpenBMC. I am familiar with
> > SP/BMC setups using proprietary code. I have successfully built the
> > OpenBMC project (in a VM running Ubuntu 18.04) as well as
> > building/installing the eSDK. Note: system was built from a ZIP from
> > github, git clone failed due to access rights.
>
> How are you cloning it? Might be some issue with SSH vs HTTPS.
>
> >  When I completed the process, I tried to load the available image into
> > QEMU for ARM (which was also built) and received the following
> > error(s), depending upon the directory from which this is run (which is
> > also a question, why the difference?)
> >  I was successful in booting the Poky example from Yocto for both x86
> > and ARM into the respective QEMU machines, for the minimal image.
> >  Any pointers would be greatly provided.
> >
> > Regards,
> > Stephen Beckwith
> >
> > Failure #1: QEMU Hangs:
> > ==> Fresh shell:
> >
> > sbeckwit at ubuntu:~/yocto_dev/openbmc-master/build$ runqemu qemuarm
> > runqemu - INFO - Running MACHINE=qemuarm bitbake -e...
>
> You're running with the wrong qemu machine - the generic 'qemuarm' machine
> won't work for the images the build produces. You need to use one of the
> BMC-specific machines instead. Note that OpenBMC doesn't properly
> integrate into the runqemu scripts, and you're often better served by
> invoking
> it manually or (and!) sending a patch to make runqemu work properly.
>
> We have some info on running qemu manually in the cheatsheet in the docs
> repo:
>
> https://github.com/openbmc/docs/blob/master/cheatsheet.md#using-qemu
>
> Hope that helps,
>
> Andrew
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190925/ac13c53a/attachment-0001.htm>