tests: use the default crashkernel value

And with commit t5b31b099 ("Simplify the management of the kernel
parameter crashkernel"), the default crashkernel value will be
used for the kernel. But the test VM has a RAM of 768M thus this is no
actual reserved memory for kdump.  Even With the old crashkernel=224M,
network dumping tests like nfs-kdump will fail out of memory when
running against current Fedora Cloud images (>=F37).

This patch address the above two issues by
 1. increasing the RAM of test VM to 1G
 2. installing the kernel-modules which contains the squashfs module in
    order to use the dracut squash module for kdump initrd.

Thanks to the dracut squash module, now even crashkernel=192M (the
default crashkernel value for RAM between 1G and 4G) works for
network dumping. Another benefit brought by this change is the default
crashkernel value can be tested as well.

Signed-off-by: Coiby Xu <coxu@redhat.com>
Reviewed-by: Philipp Rudo <prudo@redhat.com>

tests/scripts/build-scripts/base-image.sh

@@ -3,8 +3,7 @@
 img_inst_pkg grubby\
 	dnsmasq\
 	openssh openssh-server\
-	dracut-network dracut-squash squashfs-tools ethtool snappy
+	dracut-network dracut-squash squashfs-tools ethtool snappy kernel-modules
 
 img_run_cmd "grubby --args systemd.journald.forward_to_console=1 systemd.log_target=console --update-kernel ALL"
 img_run_cmd "grubby --args selinux=0 --update-kernel ALL"
-img_run_cmd "grubby --args crashkernel=224M --update-kernel ALL"

tests/scripts/test-lib.sh

@@ -8,7 +8,7 @@
 DEFAULT_QEMU_CMD="-nodefaults \
 -nographic \
 -smp 2 \
--m 768M \
+-m 1G \
 -monitor none"
 
 _YELLOW='\033[1;33m'