From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] qemu-aarch64 applications misbehaving
Date: Mon, 3 Dec 2018 09:16:04 +0100 [thread overview]
Message-ID: <20181203091604.7dc36318@windsurf.home> (raw)
In-Reply-To: <CAKAbLo9SzmvsEGfhRyZRYLgRSocJUEgEbR=a9v2cBUsdqeKVig@mail.gmail.com>
Hello,
On Mon, 19 Nov 2018 17:04:52 +0100, Zeno Endemann wrote:
> Applications run under qemu-aarch64 are misbehaving for me. For example,
> minimal (console only) Qt application are crashing on startup, and also the
> BusyBox's "df" (disk usage) is printing out silly numbers. While I'm not
> positive I suspect these are bugs in qemu.
>
> I build the guest os using buildroot 2018.08.2,
> qemu_aarch64_virt_defconfig, and running it as instructed (minus network,
> don't need it):
>
> qemu-system-aarch64 -M virt -cpu cortex-a57 -nographic -smp 1 -kernel
> output/images/Image -append "root=/dev/vda console=ttyAMA0" -drive
> file=output/images/rootfs.ext4,if=none,format=raw,id=hd0 -device
> virtio-blk-device,drive=hd0
>
> (Host os is Ubuntu 18.04, QEMU emulator version 2.11.1(Debian
> 1:2.11+dfsg-1ubuntu7.7))
>
> Can someone confirm this? Any hints would be much appreciated.
>
> While at it, another side question: Is there a reason why the
> qemu_aarch64_virt_defconfig built kernel does not include the drivers for
> qemu graphics emulation?
This should probably be fixed in uClibc with:
https://git.buildroot.org/buildroot/commit/?id=2179ca4a61b4574854075e4cdc1e2b851fa0d5b3
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-03 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 16:04 [Buildroot] qemu-aarch64 applications misbehaving Zeno Endemann
2018-11-20 2:11 ` Ricardo Martincoski
2018-11-20 10:39 ` Thomas Petazzoni
2018-12-03 8:16 ` Thomas Petazzoni [this message]
2018-11-20 13:55 Zeno Endemann
2018-11-20 16:13 ` Thomas Petazzoni
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=20181203091604.7dc36318@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.