KVM-Autotest/TODO: Difference between revisions

From KVM
No edit summary
m (Add categories)
 
(122 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.


* kickstart installation support [Lucas] [Nearly DONE]
== Pradeep ==
* kvm-autotest auto resolve qemu-kvm backtraces
* 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)
* 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]
* Add support for kvm-trace.
* 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]


== Tests ==
* SLES support - 
** Owner - Onkar n Mahajan (currently working)
** Expected delivery to community -


* Find out how to use Autotest's netperf test with guests [Yolkfull]
* virtio-blk disk serial # test (extend physical_resource_check test)
* If needed, write a netperf/iperf test [jasowang] [NEEDS MORE WORK]
** Owner -  
* cpu hotplug [Glauber]
** Expected delivery to community-
* pci net hot plug [Yolkfull]
* pci block hot plug [Yolkfull]
* pxe boot * net types [jasowang]
* qcow1, qcow2, vmdk, vhd
* qcow2 internal snapshots
* Further migration [jasowang]
* Multiple nics [jasowang]
* multiple disks
* 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
* Guest_S4 [Yolkfull]


== Misc ==
* 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 docstrings to all functions that still lack them, including the ones in stepmaker.py, stepeditor.py and kvm_tests.py [Michael]
* Add use QED image format during tests.
* Document the setupssh.iso and setuptelnet.iso creation procedures in the wiki
** Owner -
* Rename all Windows ISOs currently used to their official MSDN names
** Expected delivery to community- 1-Dec-2011
* 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 ==
* virsh stream.
** Owner -
** Expected delivery to community-


* Please open bugs on the [[http://autotest.kernel.org/newticket autotest defect tracking system]]
* 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
 
[[Category:Docs]][[Category:Historical]][[Category:Testing]][[Category:Redirects]]

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
Retrieved from "https://linux-kvm.org/index.php?title=KVM-Autotest/TODO&oldid=173292"