KVM-Autotest/TODO: Difference between revisions

From KVM
(Added another item)
No edit summary
Line 8: Line 8:
* Add <tt>display</tt> parameter to enable user control of the QEMU display method (VNC/SDL/nographic)
* Add <tt>display</tt> parameter to enable user control of the QEMU display method (VNC/SDL/nographic)
* Implement VM.clone() -- to be used by tests that need to add new VMs by themselves
* Implement VM.clone() -- to be used by tests that need to add new VMs by themselves
* kickstart installation support
* kvm-autotest auto resolve qemu-kvm backtraces


== Tests ==
== Tests ==
Line 15: Line 17:
* Write a time drift test
* Write a time drift test
* Write a test which adds VMs until one of them becomes unresponsive, and records the maximum number of VMs successfully started
* Write a test which adds VMs until one of them becomes unresponsive, and records the maximum number of VMs successfully started
== Bugs ==

Revision as of 14:12, 17 March 2009

KVM-Autotest To-Do list

Framework

  • Verify MD5 sum of ISO image before starting a VM [DONE]
  • Enable multiple user controlled port redirections (with -redir)
  • Support TAP networking with a user specified MAC address for each NIC
  • Add display parameter to enable user control of the QEMU display method (VNC/SDL/nographic)
  • Implement VM.clone() -- to be used by tests that need to add new VMs by themselves
  • kickstart installation support
  • kvm-autotest auto resolve qemu-kvm backtraces

Tests

  • Find out how to use Autotest's netperf test with guests
  • If needed, write a netperf/iperf test
  • Write a time drift test
  • Write a test which adds VMs until one of them becomes unresponsive, and records the maximum number of VMs successfully started

Bugs