rapido-init.rs not working alongside Dracut based lio-local image

[ddiss]

Comparing current master and old-dracut branch behaviour, master fails to configure the lio-local loopback device in the autorun script. I'd guess this might be due filesystem mounts done by early-init. It needs further investigation.

[ddiss]

I'd guess this might be due filesystem mounts done by early-init. It needs further investigation.

This fixes it for me:

--- a/autorun/lio_local.sh
+++ b/autorun/lio_local.sh
@@ -24,6 +24,7 @@ udevadm settle || _fatal
 
 _vm_ar_configfs_mount
 
+modprobe loop || _fatal

[ddiss]

Looking at an strace of the failing losetup -f call, it looks like the old-dracut VM auto-loads the loop kernel module when losetup accesses the /dev/loop-control node.
According to https://stackoverflow.com/questions/73044468/which-kernel-function-does-on-demand-module-loading-triggered-by-accessing-a-non/73053477#73053477 it's the job of user-space to create those nodes, which systemd-tmpfiles-setup-dev.service generally handles. I'll add logic to rapido-init to handle this for non-systemd boot.