From: "Alex Bennée" <alex.bennee@linaro.org>
To: Ajay Garg <ajaygargnsit@gmail.com>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org,
rumpkernel-users@freelists.org
Subject: Re: [Qemu-devel] Crash when running hello-world unikernel for ARM
Date: Mon, 09 Apr 2018 13:45:22 +0100 [thread overview]
Message-ID: <87efjov999.fsf@linaro.org> (raw)
In-Reply-To: <CAHP4M8VnuS5KijfVw9eDz41KPwaT4rJ+4VEU==EbBgdwgFKJhA@mail.gmail.com>
Ajay Garg <ajaygargnsit@gmail.com> writes:
> Hi All.
>
> We did the following :
>
> a)
> Cross-compile rumprun for ARM on a linux x86_64 :
>
> ajay@latitude-3480:~/rumprun-arm-hw/rumprun$
> CC=arm-linux-gnueabihf-gcc ./build-rr.sh hw
<snip>
>
> c)
> Tried running on x86_64, via qemu, but got the crash :
>
> ######################################################################
> ajay@latitude-3480:~/rumprun-arm-hw/rumprun$ qemu-system-x86_64
> -nographic -kernel helloer.bin
> warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
> qemu: fatal: Trying to execute code outside RAM or ROM at 0x00000000000a01f1
>
<snip>
>
>
> Where should we be looking to start to fix?
qemu-system-x86_64 is expecting an x86 binary blob. I assume you need
qemu-system-arm. More importantly you need to specify a -M machine type
that matches whatever rumprun is expecting.
--
Alex Bennée
next prev parent reply other threads:[~2018-04-09 12:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 9:34 [Qemu-devel] Crash when running hello-world unikernel for ARM Ajay Garg
2018-04-09 12:45 ` Alex Bennée [this message]
2018-04-09 12:57 ` Ajay Garg
2018-04-09 13:29 ` Alex Bennée
2018-04-10 4:14 ` Ajay Garg
2018-04-10 4:21 ` Ajay Garg
2018-04-10 7:38 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2018-04-10 8:16 ` Ajay Garg
2018-04-10 9:20 ` Peter Maydell
2018-04-10 10:19 ` Ajay Garg
2018-04-11 7:19 ` Ajay Garg
2018-04-12 4:26 ` Ajay Garg
2018-04-12 4:53 ` Ajay Garg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efjov999.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=ajaygargnsit@gmail.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rumpkernel-users@freelists.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).