KVM-Autotest/TODO: Difference between revisions

From KVM
No edit summary
No edit summary
Line 15: Line 15:
== Tests ==
== Tests ==


= Client-side =
=== Client Side Test ===


* Find out how to use Autotest's netperf test with guests [Yolkfull]
* Find out how to use Autotest's netperf test with guests [Yolkfull]
Line 44: Line 44:
* Guest_S4 test[Yolkfull]
* Guest_S4 test[Yolkfull]


= Server-side =
=== Server Side Tests ===


* Run server-side netperf test between two guests [Yolkfull]
* Run server-side netperf test between two guests [Yolkfull]
* Server-side migration with/without workload(dbench,lmbench etc) [Yolkfull]
* Server-side migration with/without workload(dbench,lmbench etc) [Yolkfull]


== Misc ==
== Misc ==

Revision as of 03:22, 30 September 2009

KVM-Autotest To-Do list

Framework

  • kickstart installation support [Lucas] [Nearly DONE]
  • 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

Client Side Test

  • Find out how to use Autotest's netperf test with guests [Yolkfull]
  • If needed, write a netperf/iperf test [jasowang] [NEEDS MORE WORK]
  • cpu hotplug [Glauber]
  • 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 [Feng Yang]
  • 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 test[Yolkfull]

Server Side Tests

  • Run server-side netperf test between two guests [Yolkfull]
  • Server-side migration with/without workload(dbench,lmbench etc) [Yolkfull]

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