public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Andreas Reichel <andreas.reichel.ext@siemens.com>
Cc: isar-users@googlegroups.com, Henning Schild <henning.schild@siemens.com>
Subject: Re: qemu test with start_vm fails
Date: Thu, 29 Nov 2018 17:25:03 +0300	[thread overview]
Message-ID: <3c25378a-446c-6ead-6776-89427a553349@ilbers.de> (raw)
In-Reply-To: <20181129122017.GA27213@iiotirae>

On 11/29/18 3:20 PM, Andreas Reichel wrote:
> On Wed, Nov 28, 2018 at 08:34:58PM +0300, Maxim Yu. Osipov wrote:
>> Hi Andreas,
>>
>> I would suggest to double check your statements before blaming that
>> something is not working
>>
> Hi,
> 
> well unfortunately I was correct. There is an error in Isar:
> the offline cache is included in the root file system :)

In your initial report you stated:

> -------- Forwarded Message --------
> Subject: qemu test with start_vm fails
> Date: Wed, 28 Nov 2018 17:25:24 +0100
> From: Andreas Reichel <andreas.reichel.ext@siemens.com>
> To: isar-users@googlegroups.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.

You said that you were unable to launch 'start_vm -a arm -d stretch'
without providing details of environment/feature enabled/commit id used.

At least now I know that you use offline cache (BTW, offline cache 
feature is broken in current next, so I may only guess on which commit 
id you base on).

I hope that it should be clear how to correctly report the problem next 
time.

> There is a /base-apt in the resulting .ext4.img.

I'll look on that and fix it if necessary (previously we had images with 
not cleaned up /var/cache/apt).

> This way I got a rootfs of 720 MB with no free space, despite the
> 64M extra space. (file system overhead).
> 
> In your CI you obviously do not use the offline cache feature,
> that's why in CI this did not happen.

I've just checked-in into 'next' the patch debe3392 "scripts/ci: enable 
use of cached base repository for fast build" and it passes OK in 'next' 
with the reverted patch d40a9ac0.

The easy way to run it on your debian PC just call

* isar$./scripts/ci_build.sh -q -f
* isar$ source isar-init-build-env
* isar/build$vm_smoke_test -q -f


Maxim.


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

  reply	other threads:[~2018-11-29 14:25 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
2018-11-28 17:44   ` Jan Kiszka
2018-11-29 12:20   ` Andreas Reichel
2018-11-29 14:25     ` Maxim Yu. Osipov [this message]
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=3c25378a-446c-6ead-6776-89427a553349@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