Boxbuild fails at image convert step

[Sven Wölfel]

Hi,

I'm sorry to be a bother again. But I'm getting the error:

[ ERROR   ]: 10:37:02 | KiwiError: Box build failed. Find build log at: './img-out/result.log'

Right after kiwi tries to convert the generated image to the qcow2 format. The result.log does not contain anything particularly useful (at least to me), it doesn't even contain the above mentioned error.

My kiwi-ng call is the following:

kiwi-ng --loglevel=10 --debug --profile kvm system boxbuild --box ubuntu --no-update-check --box-debug --  --description ./debian --target-dir ./img-out

So I would at least hope to be thrown in the console of the box, but that doesn't happen either. I tried it with the ubuntu and universal box both show the same result.

Is there a way to get more output? Or some additional information as to why it fails at this step?

My kiwi-ng version is 10.2.9, the used configuration and the build.log are attached to this mail.

I will try to see if this happens with image type raw as well but atm. I'm a bit clueless what happens here.

Regards

Sven

[Marcus Schäfer]

Hi,

> I'm sorry to be a bother again. But I'm getting the error:
>
> [ ERROR ]: 10:37:02 | KiwiError: Box build failed. Find build log at:
> './img-out/result.log'
>
> Right after kiwi tries to convert the generated image to the qcow2
> format. The result.log does not contain anything particularly useful
> (at least to me), it doesn't even contain the above mentioned error.

Hmm, that looks like your box, the kvm process on your host has died
unexpectedly. This is also the reason why you get dropped off from
the box without any shell and why the log file has no chance to log
anything more.

I can only speculate on the reasons.

* /img-out is a tmpfs and you are running out of memory ?
* /img-out has I/O issues ?
* the VM is running out of memory (but you should see oom-killer logs)
Thus unlikely

Overall I would say if there is any more log information you should
be able to see that in the logs of the system you are running boxbuild
on. For example dmesg, /var/log/messages, journalctl ...

Regards,
Marcus
--
Public Key available via: https://keybase.io/marcus_schaefer/key.asc
keybase search marcus_schaefer

[Sven Wölfel]

Argh.. yes OOM on the build host.

oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=qemu-system-x86,pid=6319,uid=1000
[ 1507.223752] Out of memory: Killed process 6319 (qemu-system-x86) total-vm:9555228kB, anon-rss:6969408kB, file-rss:128kB, shmem-rss:0kB, UID:1000 pgtables:14748kB oom_score_adj:0

That explains why the universal box stopped earlier during the build than the ubuntu box.

Thanks for the hint!