Package: dracut / 109-5
Metadata
| Package | Version | Patches format |
|---|---|---|
| dracut | 109-5 | 3.0 (quilt) |
Patch series
view the series file| Patch | File delta | Description |
|---|---|---|
| udevsettle | (download) |
modules.d/80base/init.sh |
1 1 + 0 - 0 ! |
udevsettle In a KVM VM the network is not configured properly, it shows ens3 (instead of eth0), which is not in status up and no IP address. |
| fix systemd networkd install and enable systemd networkd .patch | (download) |
modules.d/11systemd-networkd/module-setup.sh |
4 4 + 0 - 0 ! |
fix(systemd-networkd): install and enable systemd-networkd-resolve-hook.socket New socket needed for v259~rc1, networkd fails if this is not installed and enabled Closes: #1120955 |
| test exit with code 77 if test is skipped.patch | (download) |
test/test-functions |
2 1 + 1 - 0 ! |
test: exit with code 77 if test is skipped |
| test run qemu do not expect initrd as first parameter.patch | (download) |
test/run-qemu |
20 14 + 6 - 0 ! |
test(run-qemu): do not expect -initrd as first parameter Check all parameters for `-initrd` instead of expecting it to be the first parameter. |
| test run qemu include in ARGS array.patch | (download) |
test/run-qemu |
8 5 + 3 - 0 ! |
test(run-qemu): include $@ in args array To simplify the code and as preparation for the following commit, include `$@` in the `ARGS` array. |
| test set console cmdline depending on the architecture.patch | (download) |
test/TEST-11-USR-MOUNT/test.sh |
2 1 + 1 - 0 ! |
test: set console cmdline depending on the architecture The QEMU process hangs (without printing anything) on some Debian/Ubuntu architectures. This is caused by the console device is called |
| test forward journald logs to console in V 1 or V 2.patch | (download) |
test/TEST-60-NFS/test.sh |
2 1 + 1 - 0 ! |
test: forward journald logs to console in v=1 or v=2 To ease debugging, forward systemd journald logs to console when `V=1` or `V=2` is set. |
| test replace rev command by sed.patch | (download) |
test/container/Dockerfile-debian |
1 0 + 1 - 0 ! |
test: replace rev command by sed On Debian-based systems, the `rev` command is shipped by the bsdextrautils package. Replace the `rev` command by `sed` which is an essential command and does not need additional packages. |
| test use UEFI for QEMU when available.patch | (download) |
test/TEST-12-UEFI/test.sh |
7 3 + 4 - 0 ! |
test: use uefi for qemu when available Move the `ovmf_code` function and related code to `run-qemu` and always use UEFI when available. This is a preperation for the following commit. |
| test run qemu support UEFI on ARM.patch | (download) |
test/run-qemu |
30 21 + 9 - 0 ! |
test(run-qemu): support uefi on arm The OVMF firmware files are builds of EDK II for 64-bit x86 virtual machines. They do not work on other architectures. So search for AAVMF files on ARM. Remove the `cfi.pflash01` driver setting because it does not work on Ubuntu arm64 and `readonly=on` is already set for the firmware file. Fixes: https://github.com/dracut-ng/dracut-ng/issues/1861 |
| test run qemu use hvc0 console on s390x.patch | (download) |
test/run-qemu |
3 3 + 0 - 0 ! |
test(run-qemu): use hvc0 console on s390x
The test `TEST-41-FULL-SYSTEMD` fails (hangs) on s390x:
```
CLIENT TEST START: readonly root
run-qemu: /usr/bin/qemu-system-s390x -cpu max -smp 2 -m 1024 -nodefaults -vga none -display none -no-reboot -watchdog-action poweroff -device virtio-rng-pci -serial stdio -device virtio-scsi-pci,id=scsi0 -drive if=none,format=raw,file=/var/tmp/dracut-test.LX2MPr/marker.img,id=drive-data0 -device scsi-hd,bus=scsi0.0,drive=drive-data0,id=data0,serial=marker -device virtio-scsi-pci,id=scsi1 -drive if=none,format=raw,file=/var/tmp/dracut-test.LX2MPr/root.btrfs,id=drive-data1 -device scsi-hd,bus=scsi1.0,drive=drive-data1,id=data1,serial=root -device virtio-scsi-pci,id=scsi2 -drive if=none,format=raw,file=/var/tmp/dracut-test.LX2MPr/root_crypt.btrfs,id=drive-data2 -device scsi-hd,bus=scsi2.0,drive=drive-data2,id=data2,serial=root_crypt -device virtio-scsi-pci,id=scsi3 -drive if=none,format=raw,file=/var/tmp/dracut-test.LX2MPr/usr.btrfs,id=drive-data3 -device scsi-hd,bus=scsi3.0,drive=drive-data3,id=data3,serial=usr -append 'console=ttyS0,115200 root=LABEL=dracut panic=1 oops=panic softlockup_panic=1 systemd.crash_reboot mount.usr=LABEL=dracutusr mount.usrflags=subvol=usr ro systemd.mask=systemd-sysusers systemd.mask=systemd-timesyncd systemd.mask=systemd-resolved ' -initrd /var/tmp/dracut-test.LX2MPr/initramfs.testing -kernel /boot/vmlinuz-6.16.12+deb14+1-s390x
[...]
[ OK ] Reached target initrd-switch-root.target - Switch Root.
[...]
[ 104.913552] systemd[1]: Starting testsuite.service - Testsuite service...
Starting testsuite.service - Testsuite service...
[ 105.245935] (test-init)[1028]: testsuite.service: Failed to set up standard input: No such file or directory
[ 105.249516] (test-init)[1028]: testsuite.service: Failed at step STDIN spawning /sbin/test-init: No such file or directory
[ 105.289084] systemd[1]: testsuite.service: Main process exited, code=exited, status=208/STDIN
[ 105.305982] systemd[1]: testsuite.service: Failed with result 'exit-code'.
[FAILED] Failed to start testsuite.service - Testsuite service.
[ 105.365771] systemd[1]: Failed to start testsuite.service - Testsuite service.
```
Replacing the default console `ttyS0` by the virtual console `hvc0`
makes the test succeed.
Bug-Debian: https://bugs.debian.org/1120955
Fixes: https://github.com/dracut-ng/dracut-ng/issues/1873
|
