Re: qemu test with start_vm fails

[Jan Kiszka <jan.kiszka@siemens.com>]

On 28.11.18 18:34, Maxim Yu. Osipov wrote:
> Hi Andreas,
> 
> I would suggest to double check your statements before blaming that something is
> not working
> 
> 1. CI is performed on regular basis on isar-build.org.
> 
> The easy way to run it on your debian PC just call
> * isar$./scripts/ci_build.sh -q
> * isar/build$ source isar-init-build-env
> * isar/build$vm_smoke_test -q
> 
> You should see something like that:
> 
> vm_smoke_test -f -q
> -------------------------------------------------
> Testing Isar [stretch] image for [arm] machine:
> Check login prompt: PASSED
> Check example module: PASSED
> -------------------------------------------------
> Testing Isar [stretch] image for [amd64]
> 
> ...
> 
> Recently the "faster" (to build/try reduced set of configurations) version of CI
> was introduced - just pass additional key '-f' to ci_build.sh and vm_smoke_test.
> 
> Moreover you are encouraged to run these scripts on your own before submitting
> your patches - this will save a lot of time to maintainer.
> 
> Instead launching on your own PC - active developers are granted account on
> Jenkins on isar-build.org - CI is automated by Jenkins. Just ask Baurzhan for an
> account.
> 
> 2. CI is not launched in docker.
> 
> 3. On my stretch laptop I've just checked out the latest next, built
> multiconfig:qemuarm-stretch:isar-image-base and launched start_vm:
> 
> isar/build$ start_vm -a arm -d stretch
> + qemu-system-arm -m 1024M -M virt -cpu cortex-a15 -nographic -kernel
> /home/myo/work/isar/src/isar/build/tmp/deploy/images/qemuarm/isar-image-base-debian-stretch-qemuarm.vmlinuz-4.9.0-8-armmp
> -initrd
> /home/myo/work/isar/src/isar/build/tmp/deploy/images/qemuarm/isar-image-base-debian-stretch-qemuarm.initrd.img-4.9.0-8-armmp
> -append console=ttyAMA0 root=/dev/vda rw -drive
> file=/home/myo/work/isar/src/isar/build/tmp/deploy/images/qemuarm/isar-image-base-debian-stretch-qemuarm.ext4.img,if=none,format=raw,id=hd0
> -device virtio-blk-device,drive=hd0
> [    0.000000] Booting Linux on physical CPU 0x0
> [    0.000000] Linux version 4.9.0-8-armmp (debian-kernel@lists.debian.org) (gcc
> version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.130-2
> (2018-10-27)
> 
> [snip]
> 
> After a while (wait for some 3-4 min) I've got
> 
> Debian GNU/Linux 9 isar ttyAMA0
> 
> isar login:
> 
> 
> When reporting a problem please provide more details about your environment
> (host/target/distro/Isar tree commit id etc).
> 

We discussed this locally a bit, and one explanation could be that something
goes wrong with the overall image size calculation run on the hos due to the
underlying file system. Andreas will follow-up with detailed analysis as time
permits.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux