From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Andreas Reichel <andreas.reichel.ext@siemens.com>,
isar-users@googlegroups.com
Cc: Henning Schild <henning.schild@siemens.com>
Subject: Re: qemu test with start_vm fails
Date: Wed, 28 Nov 2018 20:34:58 +0300 [thread overview]
Message-ID: <7db5e0b2-52e8-f15f-96b6-88385de5a498@ilbers.de> (raw)
In-Reply-To: <20181128162524.GA12380@iiotirae>
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).
Maxim.
On 11/28/18 7:25 PM, Andreas Reichel wrote:
> 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.
>
> I thought, there was a CI that tested the builds with qemu on a
> regular basis?
>
> 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...
>
> kind regards
> Andreas
>
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2018-11-28 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 16:25 Andreas Reichel
2018-11-28 17:00 ` Henning Schild
2018-11-28 17:34 ` Maxim Yu. Osipov [this message]
2018-11-28 17:44 ` Jan Kiszka
2018-11-29 12:20 ` Andreas Reichel
2018-11-29 14:25 ` Maxim Yu. Osipov
2018-11-29 14:28 ` Jan Kiszka
2018-11-30 9:06 ` Henning Schild
2018-12-03 13:11 ` Henning Schild
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=7db5e0b2-52e8-f15f-96b6-88385de5a498@ilbers.de \
--to=mosipov@ilbers.de \
--cc=andreas.reichel.ext@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
/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