Control: reopen -1
On 2026-04-07 13:37, Christian Kastner wrote:
> On 2026-04-07 13:26, Benjamin Drung wrote:
>> 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.
> 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.
I tested 110-9, and I'm afraid the problem is still present. A boot with
qemu-system-x86 shows it's again hangs at
(1 of 2) Job dev-mapper-loop0p1.device/start running (3s / no limit)
(2 of 2) Job dracut-initqueue.service/start running (8s / no limit)
I'm very much embarrassed, but I now see that for the autopkgtest
*running*, I repeatedly blind-typed the wrong command. Muscle memory, I
guess... Of course, the runner also needs the EFI option:
$ autopkgtest -B -U dracut -- qemu --boot=efi /tmp/unstable-amd64.img
^^^^
However: the qemu-system-x86_64 command I shared earlier was correct,
and the way I reproduced the two messages from boot above.
Best,
Christian
