Filipe Brandenburger
14e0259b49
We currently use the host's kernel and initramfs in our QEMU tests. If the host is running on an encrypted LUKS partition, then the initramfs will have a crypttab setup looking for the particular root disk it needs to encrypt before booting into the system. However, this disk obviously doesn't exist in our QEMU VM, so it turns out our tests end up waiting for this device to become available, which will never actually happen, and boot hangs for 90s until that service times out. [*** ] A start job is running for /dev/disk/by-uuid/01234567-abcd-1234-abcd-0123456789ab (20s / 1min 30s) In order to prevent this issue, let's pass "rd.luks=0" to disable LUKS in the initramfs only as part of our default kernel command-line in our QEMU tests. This is enough to disable this behavior and prevent the timeout, while at the same time doesn't conflict with our tests that actually check for LUKS behavior in the systemd running under test (such as TEST-02-CRYPTSETUP). Tested: `sudo make -C TEST-02-CRYPTSETUP/ clean setup run`
systemd - System and Service Manager
Details
General information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.