2 # This config is an example usage of ktest.pl with a kvm guest
4 # The guest is called 'Guest' and this would be something that
5 # could be run on the host to test a virtual machine target.
10 # Use virsh to read the serial console of the guest
11 CONSOLE = virsh console ${MACHINE}
13 #*************************************#
14 # This part is the same as test.conf #
15 #*************************************#
17 # The include files will set up the type of test to run. Just set TEST to
18 # which test you want to run.
20 # TESTS = patchcheck, randconfig, boot, test, config-bisect, bisect, min-config
22 # See the include/*.conf files that define these tests
26 # Some tests may have more than one test to run. Define MULTI := 1 to run
30 # In case you want to differentiate which type of system you are testing
33 # REBOOT = none, error, fail, empty
34 # See include/defaults.conf
38 # The defaults file will set up various settings that can be used by all
40 INCLUDE include/defaults.conf
43 #*************************************#
44 # Now we are different from test.conf #
45 #*************************************#
48 # The example here assumes that Guest is running a Fedora release
49 # that uses dracut for its initfs. The POST_INSTALL will be executed
50 # after the install of the kernel and modules are complete.
52 POST_INSTALL = ${SSH} /sbin/dracut -f /boot/initramfs-test.img $KERNEL_VERSION
54 # Guests sometimes get stuck on reboot. We wait 3 seconds after running
55 # the reboot command and then do a full power-cycle of the guest.
56 # This forces the guest to restart.
58 POWERCYCLE_AFTER_REBOOT = 3
60 # We do the same after the halt command, but this time we wait 20 seconds.
61 POWEROFF_AFTER_HALT = 20
64 # As the defaults.conf file has a POWER_CYCLE option already defined,
65 # and options can not be defined in the same section more than once
66 # (all DEFAULTS sections are considered the same). We use the
67 # DEFAULTS OVERRIDE to tell ktest.pl to ignore the previous defined
68 # options, for the options set in the OVERRIDE section.
72 # Instead of using the default POWER_CYCLE option defined in
73 # defaults.conf, we use virsh to cycle it. To do so, we destroy
74 # the guest, wait 5 seconds, and then start it up again.
75 # Crude, but effective.
77 POWER_CYCLE = virsh destroy ${MACHINE}; sleep 5; virsh start ${MACHINE}
82 # The following files each handle a different test case.
83 # Having them included allows you to set up more than one machine and share
85 INCLUDE include/patchcheck.conf
86 INCLUDE include/tests.conf
87 INCLUDE include/bisect.conf
88 INCLUDE include/min-config.conf