If the host supports kvm, use is. If this is not the case but the kqemu
module is loaded, run qemu with kqemu optimization. Otherwise fall-back to
pure usermode qemu.
If we purport to test booting to an md raid, we may as well test it.
We do not need the plymouth module and the normal crypt module to include
duplicate functionality.
Also create the root filesystem from within the virtual env, this way there
will be no nasty suprises w.r.t interactions with the host machine. This
is important when we test booting to LVM, LUKS, and mdraid.
Otherwise it would succeed silently when we KNOW it would fail, which is not cool.
Usually this means you didn't build switch_root in your dracut checkout and you used dracut -l.
(This currently cannot be done in a check script, because of the current design of check.
Andreas intends on discussing a redesign on the list.)
Prevent messages such as the following when booting dracut:
++ mknod /dev/null c 1 3
mknod: `/dev/null': File exists
The plymouth-start.sh script tries to create device nodes it needs, but which
have already been created by the /init script.
This patch makes the mknod calls conditional.
diffstat dracut-plymouth-prevent-mknod-errormsg.patch
plymouth-start.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
remove "-d" as a short-alias for --debug. It collides with the
--driver short-alias.
If --debug is set, inst_script() spews binary "garbage" to the screen
which are interpreted as control characters by the terminal, prompting
the user to call "reset" after dracut has finished. This is related to
set -x printing binary headers from files to stdout.
As inst_script() is only checking if it is a script it should copy by
reading the first 80chars of the file and checking for the shebang line,
it is safe to call tr on the read in data and remove all unprintable
chars if the debug switch is set.
Andreas Thienemann