1# 2# This config is an example usage of ktest.pl with a kvm guest 3# 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. 6 7MACHINE = Guest 8 9 10# Use virsh to read the serial console of the guest 11CONSOLE = virsh console ${MACHINE} 12 13# Use SIGKILL to terminate virsh console. We can't kill virsh console 14# by the default signal, SIGINT. 15CLOSE_CONSOLE_SIGNAL = KILL 16 17#*************************************# 18# This part is the same as test.conf # 19#*************************************# 20 21# The include files will set up the type of test to run. Just set TEST to 22# which test you want to run. 23# 24# TESTS = patchcheck, randconfig, boot, test, config-bisect, bisect, min-config 25# 26# See the include/*.conf files that define these tests 27# 28TEST := patchcheck 29 30# Some tests may have more than one test to run. Define MULTI := 1 to run 31# the extra tests. 32MULTI := 0 33 34# In case you want to differentiate which type of system you are testing 35BITS := 64 36 37# REBOOT = none, error, fail, empty 38# See include/defaults.conf 39REBOOT := empty 40 41 42# The defaults file will set up various settings that can be used by all 43# machine configs. 44INCLUDE include/defaults.conf 45 46 47#*************************************# 48# Now we are different from test.conf # 49#*************************************# 50 51 52# The example here assumes that Guest is running a Fedora release 53# that uses dracut for its initfs. The POST_INSTALL will be executed 54# after the install of the kernel and modules are complete. 55# 56POST_INSTALL = ${SSH} /sbin/dracut -f /boot/initramfs-test.img $KERNEL_VERSION 57 58# Guests sometimes get stuck on reboot. We wait 3 seconds after running 59# the reboot command and then do a full power-cycle of the guest. 60# This forces the guest to restart. 61# 62POWERCYCLE_AFTER_REBOOT = 3 63 64# We do the same after the halt command, but this time we wait 20 seconds. 65POWEROFF_AFTER_HALT = 20 66 67 68# As the defaults.conf file has a POWER_CYCLE option already defined, 69# and options can not be defined in the same section more than once 70# (all DEFAULTS sections are considered the same). We use the 71# DEFAULTS OVERRIDE to tell ktest.pl to ignore the previous defined 72# options, for the options set in the OVERRIDE section. 73# 74DEFAULTS OVERRIDE 75 76# Instead of using the default POWER_CYCLE option defined in 77# defaults.conf, we use virsh to cycle it. To do so, we destroy 78# the guest, wait 5 seconds, and then start it up again. 79# Crude, but effective. 80# 81POWER_CYCLE = virsh destroy ${MACHINE}; sleep 5; virsh start ${MACHINE} 82 83 84DEFAULTS 85 86# The following files each handle a different test case. 87# Having them included allows you to set up more than one machine and share 88# the same tests. 89INCLUDE include/patchcheck.conf 90INCLUDE include/tests.conf 91INCLUDE include/bisect.conf 92INCLUDE include/min-config.conf 93INCLUDE include/bootconfig.conf