kvm.conf 2.8 KB

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