KVM-Autotest/TODO: Difference between revisions
From KVM
No edit summary |
No edit summary |
||
Line 24: | Line 24: | ||
* Make it possible to install virtio nw driver under windows xp/2003 guests without having to resort to the msi installer | * Make it possible to install virtio nw driver under windows xp/2003 guests without having to resort to the msi installer | ||
=== | === Done === | ||
* Include support for host kernel install on the KVM default control file - Using autotest standard API to get it done | * Include support for host kernel install on the KVM default control file - Using autotest standard API to get it done | ||
** | ** Resolved a bunch of bugs to reach to full functionality | ||
* Apply network patchset (Yay!) | * Apply network patchset (Yay!) | ||
Revision as of 22:43, 13 October 2010
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
- Make cache=off the default for guest images
- Multi host migration
- 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
- Include support for host kernel install on the KVM default control file - Using autotest standard API to get it done
- Resolved a bunch of bugs to reach to full functionality
- Apply network patchset (Yay!)
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
Very old, possibly no longer relevant
- Add docstrings to all functions that still lack them, including the ones in stepmaker.py, stepeditor.py and kvm_tests.py
- Rename all Windows ISOs currently used to their official MSDN names
- Fill the sections "Working with step files" and "Step file creation tips" in the wiki
akong
- 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
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
(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)
Bugs
- Please open bugs on the [autotest defect tracking system]