2 # This config is an example usage of ktest.pl with a vmware guest
6 # - Edit the Virtual Machine ("Edit virtual machine settings")
8 # - You almost certainly want it set "Connect at power on"
9 # - Select "Use socket (named pipe)"
10 # - Select a name that you'll recognize, like 'ktestserialpipe'
12 # - To: A Virtual Machine
14 # - Make sure you note the name, it will be in the base directory of the
15 # virtual machine (where the "disks" are stored. The default
16 # is /var/lib/vmware/<virtual machine name>/<the name you entered above>
18 # - Make note of the path to the VM
21 # The guest is called 'Guest' and this would be something that
22 # could be run on the host to test a virtual machine target.
26 # Name of the serial pipe you set in the VMware settings
27 VMWARE_SERIAL_NAME = <the name you entered above>
29 # Define a variable of the name of the VM
30 # Noting this needs to be the name of the kmx file, and usually, the
31 # name of the directory that it's in. If the directory and name
32 # differ change the VMWARE_VM_DIR accordingly.
33 # Please ommit the .kmx extension
34 VMWARE_VM_NAME = <virtual machine name>
36 # VM dir name. This is usually the same as the virtual machine's name,
37 # but not always the case. Change if they differ
38 VMWARE_VM_DIR = ${VMWARE_VM_NAME}
40 # Base directory that the Virtual machine is contained in
41 # /var/lib/vmware is the default on Linux
42 VMWARE_VM_BASE_DIR = /var/lib/vmware/${VMWARE_VM_DIR}
44 # Use ncat to read the unix pipe. Anything that can read the Unix Pipe
45 # and output it's contents to stdout will work
46 CONSOLE = /usr/bin/ncat -U ${VMWARE_VM_BASE_DIR}/${VMWARE_SERIAL_NAME}
48 # Define what version of Workstation you are using
49 # This is used by vmrun to use the appropriate appripriate pieces to
50 # test this. In all likelihood you want 'ws' or 'player'
52 # ws - Workstation (Windows or Linux host)
53 # fusion - Fusion (Mac host)
54 # player - Using VMware Player (Windows or Linux host)
55 # Note: vmrun has to run directly on the host machine
58 # VMware provides `vmrun` to allow you to do certain things to the virtual machine
59 # This should hard reset the VM and force a boot
60 VMWARE_POWER_CYCLE = /usr/bin/vmrun -T ${VMWARE_HOST_TYPE} reset ${VMWARE_VM_BASE_DIR}/${VMWARE_VM_NAME}.kmx nogui
62 #*************************************#
63 # This part is the same as test.conf #
64 #*************************************#
66 # The include files will set up the type of test to run. Just set TEST to
67 # which test you want to run.
69 # TESTS = patchcheck, randconfig, boot, test, config-bisect, bisect, min-config
71 # See the include/*.conf files that define these tests
75 # Some tests may have more than one test to run. Define MULTI := 1 to run
79 # In case you want to differentiate which type of system you are testing
82 # REBOOT = none, error, fail, empty
83 # See include/defaults.conf
87 # The defaults file will set up various settings that can be used by all
89 INCLUDE include/defaults.conf
92 #*************************************#
93 # Now we are different from test.conf #
94 #*************************************#
97 # The example here assumes that Guest is running a Fedora release
98 # that uses dracut for its initfs. The POST_INSTALL will be executed
99 # after the install of the kernel and modules are complete.
101 POST_INSTALL = ${SSH} /sbin/dracut -f /boot/initramfs-test.img $KERNEL_VERSION
103 # Guests sometimes get stuck on reboot. We wait 3 seconds after running
104 # the reboot command and then do a full power-cycle of the guest.
105 # This forces the guest to restart.
107 POWERCYCLE_AFTER_REBOOT = 3
109 # We do the same after the halt command, but this time we wait 20 seconds.
110 POWEROFF_AFTER_HALT = 20
113 # As the defaults.conf file has a POWER_CYCLE option already defined,
114 # and options can not be defined in the same section more than once
115 # (all DEFAULTS sections are considered the same). We use the
116 # DEFAULTS OVERRIDE to tell ktest.pl to ignore the previous defined
117 # options, for the options set in the OVERRIDE section.
121 # Instead of using the default POWER_CYCLE option defined in
122 # defaults.conf, we use virsh to cycle it. To do so, we destroy
123 # the guest, wait 5 seconds, and then start it up again.
124 # Crude, but effective.
126 POWER_CYCLE = ${VMWARE_POWER_CYCLE}
131 # The following files each handle a different test case.
132 # Having them included allows you to set up more than one machine and share
134 INCLUDE include/patchcheck.conf
135 INCLUDE include/tests.conf
136 INCLUDE include/bisect.conf
137 INCLUDE include/min-config.conf