Back to home page

OSCL-LXR

 
 

    


0001 #
0002 # This config is an example usage of ktest.pl with a vmware guest
0003 #
0004 # VMware Setup:
0005 # -------------
0006 # - Edit the Virtual Machine ("Edit virtual machine settings")
0007 # - Add a Serial Port
0008 #   - You almost certainly want it set "Connect at power on"
0009 #   - Select "Use socket (named pipe)"
0010 #   - Select a name that you'll recognize, like 'ktestserialpipe'
0011 #   - From: Server
0012 #   - To: A Virtual Machine
0013 #   - Save
0014 # - Make sure you note the name, it will be in the base directory of the
0015 #   virtual machine (where the "disks" are stored.  The default
0016 #   is /var/lib/vmware/<virtual machine name>/<the name you entered above>
0017 #
0018 # - Make note of the path to the VM
0019 # </End VMware setup>
0020 #
0021 # The guest is called 'Guest' and this would be something that
0022 # could be run on the host to test a virtual machine target.
0023 
0024 MACHINE = Guest
0025 
0026 # Name of the serial pipe you set in the VMware settings
0027 VMWARE_SERIAL_NAME = <the name you entered above>
0028 
0029 # Define a variable of the name of the VM
0030 # Noting this needs to be the name of the kmx file, and usually, the
0031 # name of the directory that it's in.  If the directory and name
0032 # differ change the VMWARE_VM_DIR accordingly.
0033 # Please ommit the .kmx extension
0034 VMWARE_VM_NAME = <virtual machine name>
0035 
0036 # VM dir name.  This is usually the same as the virtual machine's name,
0037 # but not always the case.  Change if they differ
0038 VMWARE_VM_DIR = ${VMWARE_VM_NAME}
0039 
0040 # Base directory that the Virtual machine is contained in
0041 # /var/lib/vmware is the default on Linux
0042 VMWARE_VM_BASE_DIR = /var/lib/vmware/${VMWARE_VM_DIR}
0043 
0044 # Use ncat to read the unix pipe.  Anything that can read the Unix Pipe
0045 # and output it's contents to stdout will work
0046 CONSOLE = /usr/bin/ncat -U ${VMWARE_VM_BASE_DIR}/${VMWARE_SERIAL_NAME}
0047 
0048 # Define what version of Workstation you are using
0049 # This is used by vmrun to use the appropriate appripriate pieces to 
0050 # test this.  In all likelihood you want 'ws' or 'player' 
0051 # Valid options:
0052 #       ws - Workstation (Windows or Linux host)
0053 #       fusion - Fusion (Mac host)
0054 #       player - Using VMware Player (Windows or Linux host)
0055 # Note: vmrun has to run directly on the host machine
0056 VMWARE_HOST_TYPE = ws
0057 
0058 # VMware provides `vmrun` to allow you to do certain things to the virtual machine
0059 # This should hard reset the VM and force a boot
0060 VMWARE_POWER_CYCLE = /usr/bin/vmrun -T ${VMWARE_HOST_TYPE} reset ${VMWARE_VM_BASE_DIR}/${VMWARE_VM_NAME}.kmx nogui
0061 
0062 #*************************************#
0063 # This part is the same as test.conf  #
0064 #*************************************#
0065 
0066 # The include files will set up the type of test to run. Just set TEST to
0067 # which test you want to run.
0068 #
0069 # TESTS = patchcheck, randconfig, boot, test, config-bisect, bisect, min-config
0070 #
0071 # See the include/*.conf files that define these tests
0072 #
0073 TEST := patchcheck
0074 
0075 # Some tests may have more than one test to run. Define MULTI := 1 to run
0076 # the extra tests.
0077 MULTI := 0
0078 
0079 # In case you want to differentiate which type of system you are testing
0080 BITS := 64
0081 
0082 # REBOOT = none, error, fail, empty
0083 #  See include/defaults.conf
0084 REBOOT := empty
0085 
0086 
0087 # The defaults file will set up various settings that can be used by all
0088 # machine configs.
0089 INCLUDE include/defaults.conf
0090 
0091 
0092 #*************************************#
0093 # Now we are different from test.conf #
0094 #*************************************#
0095 
0096 
0097 # The example here assumes that Guest is running a Fedora release
0098 # that uses dracut for its initfs. The POST_INSTALL will be executed
0099 # after the install of the kernel and modules are complete.
0100 #
0101 POST_INSTALL = ${SSH} /sbin/dracut -f /boot/initramfs-test.img $KERNEL_VERSION
0102 
0103 # Guests sometimes get stuck on reboot. We wait 3 seconds after running
0104 # the reboot command and then  do a full power-cycle of the guest.
0105 # This forces the guest to restart.
0106 #
0107 POWERCYCLE_AFTER_REBOOT = 3
0108 
0109 # We do the same after the halt command, but this time we wait 20 seconds.
0110 POWEROFF_AFTER_HALT = 20
0111 
0112 
0113 # As the defaults.conf file has a POWER_CYCLE option already defined,
0114 # and options can not be defined in the same section more than once
0115 # (all DEFAULTS sections are considered the same). We use the
0116 # DEFAULTS OVERRIDE to tell ktest.pl to ignore the previous defined
0117 # options, for the options set in the OVERRIDE section.
0118 #
0119 DEFAULTS OVERRIDE
0120 
0121 # Instead of using the default POWER_CYCLE option defined in
0122 # defaults.conf, we use virsh to cycle it. To do so, we destroy
0123 # the guest, wait 5 seconds, and then start it up again.
0124 # Crude, but effective.
0125 #
0126 POWER_CYCLE = ${VMWARE_POWER_CYCLE}
0127 
0128 
0129 DEFAULTS
0130 
0131 # The following files each handle a different test case.
0132 # Having them included allows you to set up more than one machine and share
0133 # the same tests.
0134 INCLUDE include/patchcheck.conf
0135 INCLUDE include/tests.conf
0136 INCLUDE include/bisect.conf
0137 INCLUDE include/min-config.conf