On Tue, 2026-04-07 at 13:16 +0200, Benjamin Drung wrote: > On Tue, 2026-04-07 at 12:34 +0200, Christian Kastner wrote: > > On 2026-04-07 12:07, Benjamin Drung wrote: > > > On Tue, 2026-04-07 at 11:44 +0200, Benjamin Drung wrote: > > > > Those two reports gave me a clue. I assume the opposite. You want > > > > hostonly disabled. The patch fix-dracut-enable-hostonly_cmdline-in- > > > > hostonly-mode-again.patch enables hostonly-cmdline by default again, but > > > > this: > > > > > > > > dracut[W]: Turning off host-only mode: /dev is not mounted! > > > > > > > > does not turn off hostonly-cmdline which causes the host config to leak > > > > into the initrd. I'll prepare a fix for dracut. > > > > > > Here comes the fix: https://github.com/dracut-ng/dracut-ng/pull/2351 > > > > > > Can you test that this fix solves your issue? > > > > It seems not, I'm afraid. > > > > I tested this by first rebuilding -8 with your newest change. > > > > Then telling autopkgtest-build-qemu to install these rebuilt packages > > with the following post-creation script: > > > > modscript.sh > > ~~~~~~~~~~~~ > > #!/bin/sh > > > > # autopkgtest-build-qemu passes the chroot as $1 > > [ -n "$1" ] || exit 1 > > > > cp /tmp/rebuild/*.deb "$1"/ > > chroot "$1" dpkg -i dracut_110-8_all.deb dracut-core_110-8_amd64.deb > > dracut-install_110-8_amd64.deb > > ~~~~~~~~~~~~ > > > > $ autopkgtest-build-qemu --script=modscript.sh --boot=efi unstable > > /tmp/unstable-amd64.img > > > > And finally booting with the qemu-system-x86_64 command string that I > > shared earlier. It still hangs at the same spot, referencing loop0p1. > > > > > > I tested this exact same procedure above with the -7 from snapshot.d.o, > > and that worked fine, so the procedure itself seems correct. > > > > I can also confirm that the warning printed is not relevant, as it also > > appears in the -7 as I just noticed. It must have been an added after > > trixie, as extra information. > > 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. -- Benjamin Drung Debian & Ubuntu Developer
