Unable to boot OpenBMC image in QEMU for AST2500
Andrew Jeffery
andrew at aj.id.au
Wed Sep 25 14:28:58 AEST 2019
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
More information about the openbmc
mailing list