KVM

From KVM

(Difference between revisions)
Revision as of 10:13, 28 October 2010
Lmr (Talk | contribs)

← Previous diff
Revision as of 11:21, 4 November 2010
Lmr (Talk | contribs)

Next diff →
Line 20: Line 20:
* Multi host migration - priority increased * Multi host migration - priority increased
 +* Infrastructure for testing different vm storage backends: file/lvm/iSCSI
* Work on setting up the conmux server for our internal test grid * Work on setting up the conmux server for our internal test grid
* Research how to trigger jobs based on events rather than using the web interface setting recurrent jobs * Research how to trigger jobs based on events rather than using the web interface setting recurrent jobs

Revision as of 11:21, 4 November 2010

Contents

KVM-Autotest TODO list

raw idea

  • more vhost_net test
  • Add Multi-guests transfer test
  • transfer test between guest(s) and extra boxs
  • add more whql tests (virtio_net,virtio_blk)

general

Note: This session is for major, multi-person items. We'll update the status weekly based on the status of the subtasks attributed to persons.

  • Libvirt integration - Will hold on this work item for the next couple of months due to resource constraints.

lmr

TODO

  • Multi host migration - priority increased
  • Infrastructure for testing different vm storage backends: file/lvm/iSCSI
  • Work on setting up the conmux server for our internal test grid
  • Research how to trigger jobs based on events rather than using the web interface setting recurrent jobs
  • Set up a qemu-block job, with kwolf's qemu-block tree
  • Set up a vhost job, with the upstream job (mst's trees for kernel and userspace)
  • Add a BLOCKED status on the autotest database, that tells the user that some feature testing was left out due to a problem on its dependencies.
  • Eventually get rid of all dependency on slirp/userspace networking to do any feature testing, since it is not a supported feature. Slipstreaming the kickstart in the install CD is a possibility, and it ends up being simpler than configuring an internal network thing for testing.
  • Make it possible to install virtio nw driver under windows xp/2003 guests without having to resort to the msi installer

Done

  • Send code to retrieve host kernels based on koji/brew tags upstream
  • Resolved UUID mount point check problem
  • QMP suite integrated upstream
  • Wrote code to retrieve kernels based on koji/brew tags

mgoldish

  • Make WHQL tests run on our internal server
  • Enable "guest-load" for a VMs before/while tests are running (e.g. migration of a VM, while a movie is playing on it)
    • This may just be a matter of moving useful code from tests to kvm_test_utils.py to make it reusable
  • Post-commit review of new network patches (committed on Oct 7 2010)
  • Use more exceptions in utility functions:
    • Add convenience functions to kvm_subprocess.py to make running shell commands shorter
    • Add convenience functions to the VM class
  • Refactor _get_command_output() and friends in kvm_monitor.py and add cmd_raw(), cmd_obj() and cmd_qmp() as required by Luiz Capitulino's test suite
  • Use select() instead of sleep() in kvm_monitor.py
  • Simplify migration code if possible (in kvm_vm.py and kvm_test_utils.py)
  • Fix VM.get_ifname() somehow (uses self.vnc_port -- bad)

akong

  • Report problem with multiple NICs and MAC address tracking
  • Using dnsmasq in unattended_install to replace userspace network with private bridge
  • Bonding test
  • Add a new test: check if guest transmits packets when link is up/down

yolkfull

  • Run netperf test between two guests
  • Migration with/without workload(dbench,lmbench etc)
  • Verify SMBIOS/DMI data (UUID, for example)
  • Disk serial number (for IDE, SCSI, VirtIO drives)

Beijing QE

  • pxe boot * net types
  • Further migration
  • Multiple nics
  • multiple disks
  • Test block device cancellation path using device mapper to generate errors ( after we had a crash in de_write_dma_cb)
  • Extend pci_assignable to support other PCI devices (USB, video cards, TV card etc)
  • Different CPU flags support
  • Passthrough the perf keys of run_autotest to autotest server
  • Register the virtual machine into autotest server and run benchmark through autotest server

Bugs

Views Article Discussion Edit History
Personal tools:  Log in / create account
Toolbox What links here Related changes Upload file Special pages Printable version