KVM-Autotest/TODO: Difference between revisions

From KVM
No edit summary
m (Add categories)
 
(111 intermediate revisions by 11 users not shown)
Line 1: Line 1:
= KVM-Autotest To-Do list =
= KVM-Autotest TODO list - DEPRECATED =


== Framework ==
KVM autotest is the set of kvm tests implemented on top of the [http://autotest.github.com/ autotest] framework. The current documentation can be seen on the [https://github.com/autotest/autotest/wiki/KVMAutotest autotest wiki], please refer to it. We'll port the remaining items to the autotest issue tracker.


* Redirect guest monitor to serial and capture guest error messages written to console. Log the errors and also scan for specific problems (e.g. oops)
== Pradeep ==
* Support an "expected to fail" param (at least in our html report)
* Log a gdb-backtrace for tests (executables) which generate a core dump file.
* Enable "guest-load" for a VMs before/while tests are running (e.g. migration of a VM, while a movie is playing on it) [Michael]
* Fail upon indentation/white-space problems in the configuration file
* Add a way to shutdown the VMs when the whole job completes (compared to doing nothing or shutting-down after every test) [Michael]
* Integrate the following code into the framework:


  #!/usr/bin/python
* SLES support -  
** Owner - Onkar n Mahajan (currently working)
** Expected delivery to community -


import sys, os, re, random, ctypes, time
* virtio-blk disk serial # test (extend physical_resource_check test)
** Owner -
** Expected delivery to community-


tasks = sys.argv[1:]
* enhance virtio-blk hotplug test
** virsh based attach-disk/detach disk
** enumerate cloud scenarios (live add, reboot after, shutdown, etc.)
** migration after live add
** Owner -
** Expected delivery to community- 1-Oct-2011


threads = [int(t)
* Add use QED image format during tests.
            for k in tasks
** Owner -
            for t in os.listdir('/proc/%s/task' % (k,))]
** Expected delivery to community- 1-Dec-2011


cpus = [int(c[3:])
* virsh stream.
        for c in os.listdir('/sys/devices/system/cpu')
** Owner -
        if re.match(r'cpu[0-9]+', c)]
** Expected delivery to community-


rand = random.Random()
* pci-multi function testing (>32 virtio devices, disk and network)
** test out max number of virtio blk and nic devices
** Owner -
** Expected delivery to community-


sched_setaffinity = ctypes.CDLL('libc.so.6').sched_setaffinity
* virtfs patch inclusion to autotest.  
** Owner -
** Expected delivery to community-


while True:
* Windows support (ping, file_transfer, ... network tests needs to be added)
    pid = rand.choice(threads)
** Owner -
    cpu = rand.choice(cpus)
** Expected delivery to community-
    mask = 1 << cpu
    sched_setaffinity(ctypes.c_int(pid), ctypes.c_size_t(4),  
ctypes.byref(ctypes.c_int(mask)))
    try:
        time.sleep(0.01)
    except:
        break
* get the serial console information (BeiJing QE)
* Random generated macaddress and ifname (BeiJing QE)
* Postcommand for qemu-img check (BeiJing QE)


== Web Interface ==
* Svirt - sVirt is a community effort aimed at integrating Mandatory Access Control (MAC) security and Linux-based virtualization (KVM, lguest et al).
** Owner - Onkar N Mahajan (currently working)
** Expected delivery to community-


* Integrate Dror Russo's patches [Lucas]
* "Migration + other task with parallel "
** Owner -
** Expected delivery to community-


== Tests ==
* Network rate limiting
** Owner -
** Expected delivery to community-


=== Client Side Test ===
* Fix old autoetst patches/bugs
** Owner -
** Expected delivery to community-


* Find out how to use Autotest's netperf test with guests [Yolkfull]
* Include libvirt_cim in autotest
* If needed, write a netperf/iperf test [jasowang] [NEEDS MORE WORK]
** Owner -  
* cpu hotplug [Glauber]
** Expected delivery to community-  
* pxe boot * net types [BeiJing QE]
* qcow1, qcow2, vmdk, vhd
* qcow2 internal snapshots
* Further migration [BeiJing QE]
* Multiple nics [BeiJing QE]
* multiple disks [BeiJing QE]
* ksm [jasowang, jzupka, ldoktor]
* -vga stg, nographics
* kvm unit-tests
* Add unattended guest installations (using kickstart or answer-files) [jasowang]
* kvm_install -- keep src and build directories under <kvm_autotest_root> instead of under kvm_runtest_2.
* Stable tsc test - http://people.redhat.com/mingo/time-warp-test/MINI-HOWTO [jasowang]
* Guest installation with pv-block device/driver (for both windows and Linux)
* savevm test [jasowang]
* Guests with large page support [jzupka, ldoktor]
* Verify SMBIOS/DMI data (UUID, for example) [Yolkfull]
* Disk serial number (for IDE, SCSI, VirtIO drives) [Yolkfull]
* Test block device cancellation path using device mapper to generate errors ( after we had a crash in de_write_dma_cb)
* Pass through NICs / VFs to guest [Yolkfull]
* Different CPU flags support [BeiJing QE]
* Integrate the kvm unit test into kvm-autoteset [BeiJing QE]
* further vlan [BeiJing QE]
* ethtool test [BeiJing QE]
* Jumbo Frame test [BeiJing QE]
* Promisc Mode Nic test [BeiJing QE]
* Guest nic bonding test [BeiJing QE]
* Nic driver load/unload test [BeiJing QE]
* Ping test [BeiJing QE]
* Multicast test [BeiJing QE]
* Use private bridge and dnsmasq to do the unattended installation [BeiJing QE]
* Passthrough the perf keys of run_autotest to autotest server [BeiJing QE]


== Server Side Tests ==
* Power Support
** Owner - IBM
** Expected Delivery to the community - Oct. 2011


* Run netperf test between two guests [Yolkfull]
[[Category:Docs]][[Category:Historical]][[Category:Testing]][[Category:Redirects]]
* Migration with/without workload(dbench,lmbench etc) [Yolkfull] [Patch Sent,need review]
* Register the virtual machine into autotest server and run benchmark through autotest server [BeiJing QE]
 
== Misc ==
 
* Add docstrings to all functions that still lack them, including the ones in stepmaker.py, stepeditor.py and kvm_tests.py [Michael]
* Document the setupssh.iso and setuptelnet.iso creation procedures in the wiki
* Rename all Windows ISOs currently used to their official MSDN names
* Share all the stepmaker data somehow so other people can debug stepfiles
* Fill the sections "Working with step files" and "Step file creation tips" in the wiki [Michael]
 
== Bugs ==
 
* Please open bugs on the [[http://autotest.kernel.org/newticket autotest defect tracking system]]

Latest revision as of 16:11, 16 May 2015

KVM-Autotest TODO list - DEPRECATED

KVM autotest is the set of kvm tests implemented on top of the autotest framework. The current documentation can be seen on the autotest wiki, please refer to it. We'll port the remaining items to the autotest issue tracker.

Pradeep

  • SLES support -
    • Owner - Onkar n Mahajan (currently working)
    • Expected delivery to community -
  • virtio-blk disk serial # test (extend physical_resource_check test)
    • Owner -
    • Expected delivery to community-
  • enhance virtio-blk hotplug test
    • virsh based attach-disk/detach disk
    • enumerate cloud scenarios (live add, reboot after, shutdown, etc.)
    • migration after live add
    • Owner -
    • Expected delivery to community- 1-Oct-2011
  • Add use QED image format during tests.
    • Owner -
    • Expected delivery to community- 1-Dec-2011
  • virsh stream.
    • Owner -
    • Expected delivery to community-
  • pci-multi function testing (>32 virtio devices, disk and network)
    • test out max number of virtio blk and nic devices
    • Owner -
    • Expected delivery to community-
  • virtfs patch inclusion to autotest.
    • Owner -
    • Expected delivery to community-
  • Windows support (ping, file_transfer, ... network tests needs to be added)
    • Owner -
    • Expected delivery to community-
  • Svirt - sVirt is a community effort aimed at integrating Mandatory Access Control (MAC) security and Linux-based virtualization (KVM, lguest et al).
    • Owner - Onkar N Mahajan (currently working)
    • Expected delivery to community-
  • "Migration + other task with parallel "
    • Owner -
    • Expected delivery to community-
  • Network rate limiting
    • Owner -
    • Expected delivery to community-
  • Fix old autoetst patches/bugs
    • Owner -
    • Expected delivery to community-
  • Include libvirt_cim in autotest
    • Owner -
    • Expected delivery to community-
  • Power Support
    • Owner - IBM
    • Expected Delivery to the community - Oct. 2011