[Buildroot] qemu-aarch64 applications misbehaving

[Buildroot] qemu-aarch64 applications misbehaving

[Zeno Endemann]

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?

Thanks,
Zeno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20181119/eff621a1/attachment.html>

[Buildroot] qemu-aarch64 applications misbehaving

[Ricardo Martincoski]

Hello,

On Mon, Nov 19, 2018 at 02:04 PM, 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))

I have exactly the same host OS and qemu version.

> 
> Can someone confirm this? Any hints would be much appreciated.

I confirm 'df' printing silly numbers with both these images:
2018.08.2 : https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/122632959
2018.11-rc1 : https://gitlab.com/buildroot.org/buildroot/-/jobs/118747268

On 2018.08.2 I also did this:
make qemu_aarch64_virt_defconfig
make menuconfig # and enable BR2_PACKAGE_HOST_QEMU_SYSTEM_MODE
make host-qemu # to build qemu 2.12.1
output/host/bin/qemu-system-aarch64 ...
and the issue with 'df' still occurs.

On current master (00d63a153d) I did this:
make qemu_aarch64_virt_defconfig
make menuconfig # and enable BR2_TOOLCHAIN_EXTERNAL
make clean
make
qemu-system-aarch64 ... # using the system-provided qemu 2.11.1
and the issue with 'df' does not occur.

> 
> 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?

Regards,
Ricardo

[Buildroot] qemu-aarch64 applications misbehaving

[Thomas Petazzoni]

Hello,

On Tue, 20 Nov 2018 00:11:13 -0200, Ricardo Martincoski wrote:

> I confirm 'df' printing silly numbers with both these images:
> 2018.08.2 : https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/122632959
> 2018.11-rc1 : https://gitlab.com/buildroot.org/buildroot/-/jobs/118747268
> 
> On 2018.08.2 I also did this:
> make qemu_aarch64_virt_defconfig
> make menuconfig # and enable BR2_PACKAGE_HOST_QEMU_SYSTEM_MODE
> make host-qemu # to build qemu 2.12.1
> output/host/bin/qemu-system-aarch64 ...
> and the issue with 'df' still occurs.

So you tested with the default C library, uClibc ? Could you test with
glibc ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] qemu-aarch64 applications misbehaving

[Thomas Petazzoni]

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

[Buildroot] qemu-aarch64 applications misbehaving

[Thomas Petazzoni]

Hello,

+Waldemar in Cc, as the uClibc-ng maintainer.

On Tue, 20 Nov 2018 14:55:32 +0100, Zeno Endemann wrote:
> > Hello,
> > 
> > On Tue, 20 Nov 2018 00:11:13 -0200, Ricardo Martincoski wrote:
> >   
> >> I confirm 'df' printing silly numbers with both these images:
> >> 2018.08.2 : https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/122632959
> >> 2018.11-rc1 : https://gitlab.com/buildroot.org/buildroot/-/jobs/118747268
> >> 
> >> On 2018.08.2 I also did this:
> >> make qemu_aarch64_virt_defconfig
> >> make menuconfig # and enable BR2_PACKAGE_HOST_QEMU_SYSTEM_MODE
> >> make host-qemu # to build qemu 2.12.1
> >> output/host/bin/qemu-system-aarch64 ...
> >> and the issue with 'df' still occurs.  
> > 
> > So you tested with the default C library, uClibc ? Could you test with
> > glibc ?  
> 
> Indeed, all problems were resolved by changing to glibc. Thanks!

OK, so there's a uClibc-ng bug somewhere. Waldemar ? :-)

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] qemu-aarch64 applications misbehaving

[Zeno Endemann]

> Hello,
> 
> On Tue, 20 Nov 2018 00:11:13 -0200, Ricardo Martincoski wrote:
> 
>> I confirm 'df' printing silly numbers with both these images:
>> 2018.08.2 : https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/122632959
>> 2018.11-rc1 : https://gitlab.com/buildroot.org/buildroot/-/jobs/118747268
>> 
>> On 2018.08.2 I also did this:
>> make qemu_aarch64_virt_defconfig
>> make menuconfig # and enable BR2_PACKAGE_HOST_QEMU_SYSTEM_MODE
>> make host-qemu # to build qemu 2.12.1
>> output/host/bin/qemu-system-aarch64 ...
>> and the issue with 'df' still occurs.
> 
> So you tested with the default C library, uClibc ? Could you test with
> glibc ?

Indeed, all problems were resolved by changing to glibc. Thanks!

> 
> Thanks,
> 
> Thomas
> -- 
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com