On 2026-04-07 13:26, Benjamin Drung wrote: > On Tue, 2026-04-07 at 13:16 +0200, Benjamin Drung wrote:>> I could reproduce > your results with a patched dracut: >> >> ``` >> $ lsinitrd /boot/initrd.img-6.19.11+deb14-amd64 >> [...] >> dracut cmdline: >> root=/dev/mapper/loop77p2 rootfstype=ext4 rootflags=rw,relatime >> ``` >> >> But I verified in a chroot that the patch works as intended >> (hostonly_cmdline is enabled before but disabled with the patch). >> >> We need to further investigate what went wrong in your example. At least >> I see "Version: dracut-110-9" in the lsinitrd output. So the initrd was >> regenerated after the package update. > > Okay. Found it: dracut in installed and generates the initrd. Some time > later /dev is mounted: > > Exec: ['mount', '--bind', '/dev', '/tmp/tmp8sopd0qw/dev'] > Exec: ['mount', '--bind', '/sys', '/tmp/tmp8sopd0qw/sys'] > Exec: ['mount', '--bind', '/proc', '/tmp/tmp8sopd0qw/proc'] > > Then your modscript.sh is executed: > > Processing triggers for dracut (110-9) ... > update-initramfs: Generating /boot/initrd.img-6.19.11+deb14-amd64 > > This time hostonly mode is not disabled, because /dev is mounted.
Thank you for figuring this one out. So my testing methodology was flawed. Unfortunately, I don't know any other way that autopkgtest-build-qemu could be tested, at least not easily (I supposed some --mirror could be hacked). If you are confident enough with the change, that's more than good enough for me. And a -9 upload will enable a regular test. Best, Christian
