KVM-Autotest/TODO: Difference between revisions

From KVM
No edit summary
m (Add categories)
 
(86 intermediate revisions by 10 users not shown)
Line 1: Line 1:
= KVM-Autotest TODO list =
= KVM-Autotest TODO list - DEPRECATED =


== Network Patchset ==
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.


Problems with nw patchset
== Pradeep ==


2) netperf
* SLES support -   
17:35:11 DEBUG| Execute netperf client test: /root/autotest/client/tests/netperf2/netperf-2.4.5/src/netperf -t TCP_CRR -H  10.16.74.142 -l 60 -- -m 1
** Owner - Onkar n Mahajan (currently working)
  17:35:45 ERROR| Fail to execute netperf test, protocol:TCP_CRR
** Expected delivery to community -
17:35:45 DEBUG| Execute netperf client test: /root/autotest/client/tests/netperf2/netperf-2.4.5/src/netperf -t UDP_RR -H 10.16.74.142 -l 60 -- -m 1
17:36:06 ERROR| Fail to execute netperf test, protocol:UDP_RR


3) vlan
* virtio-blk disk serial # test (extend physical_resource_check test)
TestError: Fail to configure ip for eth0.1
** Owner -  
17:46:27 DEBUG| Sending command: ifconfig eth0.1 192.168.1.1
** Expected delivery to community-
17:46:27 DEBUG| Command failed; status: 255, output: SIOCSIFADDR: No such device eth0.1: unknown interface: No such device
17:46:27 DEBUG| Sending command: if [[ -e /proc/net/vlan/eth0.1 ]];then vconfig rem eth0.1;fi
17:46:27 DEBUG| Sending command: if [[ -e /proc/net/vlan/eth0.1 ]];then vconfig rem eth0.1;fi
17:46:28 INFO | rem eth0.1
17:46:28 DEBUG| Sending command: if [[ -e /proc/net/vlan/eth0.2 ]];then vconfig rem eth0.2;fi
17:46:28 DEBUG| Sending command: if [[ -e /proc/net/vlan/eth0.2 ]];then vconfig rem eth0.2;fi
17:46:28 INFO | rem eth0.2
17:46:28 DEBUG| Sending command: if [[ -e /proc/net/vlan/eth0.3 ]];then vconfig rem eth0.3;fi
17:46:28 DEBUG| Sending command: if [[ -e /proc/net/vlan/eth0.3 ]];then vconfig rem eth0.3;fi
17:46:28 INFO | rem eth0.3
17:46:28 DEBUG| Sending command: if [[ -e /proc/net/vlan/eth0.4 ]];then vconfig rem eth0.4;fi
17:46:29 DEBUG| Sending command: if [[ -e /proc/net/vlan/eth0.4 ]];then vconfig rem eth0.4;fi
17:46:29 INFO | rem eth0.4
17:46:29 DEBUG| Sending command: if [[ -e /proc/net/vlan/eth0.5 ]];then vconfig rem eth0.5;fi
17:46:29 DEBUG| Sending command: if [[ -e /proc/net/vlan/eth0.5 ]];then vconfig rem eth0.5;fi
17:46:29 INFO | rem eth0.5
17:46:29 ERROR| Test failed: TestError: Fail to configure ip for eth0.1


4) ethtool
* enhance virtio-blk hotplug test
Address comment from mst:
** 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


> > Initialize the callbacks first and execute all the sub
* Add use QED image format during tests.
> > tests one by one, all the result will be check at the
** Owner -
> > end. When execute this test, vhost should be enabled,
** Expected delivery to community- 1-Dec-2011
> > then most of new features can be used. Vhost doesn't
> > support VIRTIO_NET_F_MRG_RXBUF, so do not check large
> > packets in received offload test.


Well, it does support that now, in any case VIRTIO_NET_F_MRG_RXBUF
* virsh stream.
is not required for large packets: it's an optimization saving
** Owner -
guest memory, really. So no need to special-case.
** Expected delivery to community-


== Framework ==
* 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-


* Fix problem with serial_login() - probably we forgot to setup the guest in a way that we hook up a getty in the serial port - DONE, by jasowang
* virtfs patch inclusion to autotest.
** Owner -
** Expected delivery to community-


* 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.
* Windows support (ping, file_transfer, ... network tests needs to be added)
** Owner -
** Expected delivery to community-


* 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.
* 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-


* Make it possible to install virtio nw driver under windows xp/2003 guests without having to resort to the msi installer - assignee? Considerations: We would like to avoid slipstreaming the drivers in the iso cdrom, since we feel it is too messy. If after honest try we can't find another way, let's give slipstreaming a try.
* "Migration + other task with parallel "
** Owner -
** Expected delivery to community-


* Re-schedule the unittest job on the autotest server. DONE
* Network rate limiting
** Owner -
** Expected delivery to community-


* Multi host migration - 1 week to recap the patch that was sent by QA, improve on it, have an updated patch by then - lmr
* Fix old autoetst patches/bugs
Deadline: 09/15 - Could not meet it, has to postpone
** Owner -
New tentative deadline: 09/22
** Expected delivery to community-


* Libvirt integration - 1 week coordinating what it needs to be done, another 4 weeks (at least) implementing it - QA, lmr, mgoldish, help from libvirt developers
* Include libvirt_cim in autotest
Deadline: 09/15 - Could not meet it, has to postpone
** Owner -  
New tentative deadline: 09/22
** Expected delivery to community-  


* Include support for host kernel install on the KVM default control file - Using autotest standard API to get it done - lmr
* Power Support
Tentative deadline: 09/22
** Owner - IBM
** Expected Delivery to the community - Oct. 2011


* 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]
[[Category:Docs]][[Category:Historical]][[Category:Testing]][[Category:Redirects]]
* Add a way to shutdown the VMs when the whole job completes (compared to doing nothing or shutting-down after every test) [Michael]
* Random generated macaddress and ifname (BeiJing QE)
 
 
=== Client Side Test ===
 
* Using dnsmasq in unattended_install to replace userspace network with private bridge [Amos] status: have implemented in internal tree
* Bonding test [Amos]
* If needed, write a netperf/iperf test [jasowang] [NEEDS MORE WORK]
* pxe boot * net types [BeiJing QE]
* Further migration [BeiJing QE]
* Multiple nics [BeiJing QE]
* multiple disks [BeiJing QE]
* -vga stg, nographics
* 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)
* Extend pci_assignable to support other PCI devices (USB, video cards, TV card etc)
* Different CPU flags support [BeiJing QE]
* Use private bridge and dnsmasq to do the unattended installation [BeiJing QE]
* Passthrough the perf keys of run_autotest to autotest server [BeiJing QE]
 
== Server Side Tests ==
 
* Run netperf test between two guests [Yolkfull]
* Migration with/without workload(dbench,lmbench etc) [Yolkfull]
* Register the virtual machine into autotest server and run benchmark through autotest server [BeiJing QE]
 
== 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
* Fill the sections "Working with step files" and "Step file creation tips" in the wiki [Michael]
 
== Bugs ==
 
* Please open bugs on the [[http://autotest.kernel.org/newticket autotest defect tracking system]]

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"