Fail to boot SLE-Micro 5.1 Beta2 on qemu-arm

[Thorsten Kukuk]

On Fri, Aug 13, Brice Dekany wrote:

> Hi,
> 
> I understand that raw image is meant to be flashed in card only for RPi.
> So the idea  of "flashing"-convert it in qcow2 is impossible?

It could work, but you have to emulate e.g. a real Raspberry Pi, so no virtio
drivers or something similar which does not exist on real hardware.
 
> Making a specific qcow2 could help qemu user but will not serve my use-case.
> 
> We need to test our application and the new ignition process in a CI-way before
> flash our hardware.

But if you use qemu, you don't test the ignition process used on your hardware...

> The idea behing using the same raw image was to minimize the difference.
> I really don't want to create a CI based on the ISO and then discover that the
> whole ignation process is wrong.

If you really want to test the process on real hardware, you have to use real
hardware. Or emulate real hardware in qemu, so that the system does not notice it's
running virtual.
Else ignition will use the qemu-workflow and not the bare metal workflow...

  Thorsten

> Thanks for your help.
> 
> My new question now is: how do I/we test the ignition process and app
> deployement without spending ages on flashing sdcard?
> 
> Regards
> 
> [cid]
> Brice DEKANY
> SE for France
> +33.6.37.12.53.24
> brice.dekany at suse.com
>  LinkedIn  | Twitter | YouTube  
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> De : micro-beta <micro-beta-bounces+brice.dekany=suse.com at lists.suse.com> de la
> part de Ignaz Forster <iforster at suse.de>
> Envoyé : vendredi 13 août 2021 16:21
> À : micro-beta at lists.suse.com <micro-beta at lists.suse.com>
> Objet : Re: Fail to boot SLE-Micro 5.1 Beta2 on qemu-arm
>  
> Am 13.08.21 um 12:00 Uhr schrieb Brice Dekany:
> > Hi there,
> >
> > I tried to boot the aarch64 raw image of SLE-Micro 5.1 Beta2 on qemu-arm
> > The process goes well to grub. It looks like the ignation file is read.
> 
> It seems that no Ignition configuration was found:
> 
> [   77.149196] localhost ignition[449]: Ignition 2.11.0
> [   77.195059] localhost ignition[449]: Stage: fetch-offline
> [   77.240441] localhost ignition[449]: no config dir at
> "/usr/lib/ignition/base.d"
> [   77.242479] localhost ignition[449]: no config dir at
> "/usr/lib/ignition/base.platform.d/metal"
> [   77.269157] localhost ignition[449]: parsed url from cmdline: ""
> [   77.283457] localhost ignition[449]: no config URL provided
> [   77.307189] localhost ignition[449]: reading system config file
> "/usr/lib/ignition/user.ign"
> [   77.323124] localhost ignition[449]: no config at
> "/usr/lib/ignition/user.ign"
> [   77.329128] localhost ignition[449]: noop provider fetching empty config
> [   77.338430] localhost ignition[449]: not a config (empty): provider
> config was empty, continuing with empty cache config
> [   77.540842] localhost ignition[449]: fetched base config from "system"
> [   77.615612] localhost ignition[449]: fetch-offline: fetch-offline passed
> [   77.617638] localhost ignition[449]: Ignition finished successfully
> 
> This is probably caused by the fact that the RPi images have
> `ignition.platform.id=metal` set in the KIWI configuration, so it
> doesn't try to search for the QEMU specific configuration file. This
> could be removed, an auto-detection will be attempted then.
> 
> > And then it crash
> > cat /run/initramfs/rdsosreport.txt >>> https://pastebin.com/1RV9zagr
> > <https://pastebin.com/1RV9zagr>
> 
> These are the relevant lines:
> 
> [   87.230528] localhost systemd[1]:
> dev-disk-by\x2duuid-6dd18fe1\x2d192e\x2d4627\x2daffc\x2d9bba001859aa.device:
> Job
> dev-disk-by\x2duuid-6dd18fe1\x2d192e\x2d4627\x2daffc\x2d9bba001859aa.device/
> start
> timed out.
> [   87.231660] localhost systemd[1]: Timed out waiting for device
> /dev/disk/by-uuid/6dd18fe1-192e-4627-affc-9bba001859aa.
> [   87.253797] localhost systemd[1]: Dependency failed for Initrd Root
> Device.
> [   87.259636] localhost systemd[1]: initrd-root-device.target: Job
> initrd-root-device.target/start failed with result 'dependency'.
> [   87.263634] localhost systemd[1]: initrd-root-device.target:
> Triggering OnFailure= dependencies.
> [   87.283626] localhost systemd[1]: Dependency failed for File System
> Check on /dev/disk/by-uuid/6dd18fe1-192e-4627-affc-9bba001859aa.
> [   87.312537] localhost systemd[1]: Dependency failed for /sysroot.
> 
> The root file system cannot be found, maybe because the the necessary
> kernel modules are missing from the initrd. (I've just seen that Jiri
> came to the same conclusion.)
> 
> Ignaz
> --
> Ignaz Forster <iforster at suse.com>
> Research Engineer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> 
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer
> 



-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)