Re: qemu test with start_vm fails

[Henning Schild <henning.schild@siemens.com>]

Am Wed, 28 Nov 2018 17:25:24 +0100
schrieb "[ext] Andreas Reichel" <andreas.reichel.ext@siemens.com>:

> Hi,
> 
> I built
> 
> multiconfig:qemuarm-stretch:isar-image-base
> 
> and wanted to test the image with
> 
> start_vm -a arm -d stretch
> 
> which failed inside my docker container so I extracted the qemu
> command generated and started qemu outside of docker.
> 
> This failed to work because the generated ext4 image had no
> space left and the kernel root parameter is set to "rw" by the
> output of start_vm script, causing systemd to hang.

That is interesting because we should have 64M of ROOTFS_EXTRA in
there, did you play with that variable?

> I thought, there was a CI that tested the builds with qemu on a
> regular basis?

There is, unfortunately the results are not publicly available.

Have a look at scripts/ci_build.sh and scripts/vm_smoke_test

arm stretch should be covered, there has been some restructuring
lately, but this is a prime target ... not sure it is using the ext4
class

> I could start the image with "root=/dev/vda ro" parameter.
> 
> If such basic things are not tested regularly this can cost
> developers a lot of time...

You can say a lot of bad things about the testing, but i am almost
100% certain that is covered.
If we do not have a test booting an ext4 arm stretch, you could propose
one.

Henning
 
> kind regards
> Andreas