From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: KVM mailing list <kvm@vger.kernel.org>,
Autotest mailing list <autotest@test.kernel.org>
Cc: Michael Goldish <mgoldish@redhat.com>
Subject: Latest kvm autotest patch queue
Date: Mon, 22 Jun 2009 10:24:23 -0300 [thread overview]
Message-ID: <1245677063.2778.30.camel@freedom> (raw)
KVM Autotest patch queue
--------------------------------------------------------------------------------
Michael Goldish (mgoldish@redhat.com)
1) KVM test: optionally convert PPM files to PNG format after test - Reviewed
2) Step file tests: introducing a new feature and some small changes - Reviewed
3) Introducing kvm_subprocess - Reviewed
--------------------------------------------------------------------------------
Jason Wang (jasowang@redhat.com)
1) TAP network support in kvm-autotest
Michael Goldish has a similar patch to this one, so we need to decide which one
is going to be used. Michael, when possible, please send your patch to support
TAP network on the kvm test.
--------------------------------------------------------------------------------
David Huff (dhuff@redhat.com)
1) Unattended installs - Needs review
Reviewed. Changes made to the unattended script, would like to create a python
module to handle the unattended install and study the possibility of doing things
with cobbler.
2) Move kvm functional tests to a 'test' directory
http://kerneltrap.org/mailarchive/linux-kvm/2009/5/26/5812453
I have reworked this patch and made my own version. I need to split it into
smaller patches though.
Needs review
--------------------------------------------------------------------------------
Yogi (anantyog@linux.vnet.ibm.com)
1) Support for remote migration
http://kerneltrap.org/mailarchive/linux-kvm/2009/4/30/5607344/thread
Rebased the patch. However, the patch review and discussion shows that we want
to implement remote migration as a server side test instead of a client side
one. The rebase is just in case we need this in the future.
Probably not going to apply, look at a different way to implement the test.
--------------------------------------------------------------------------------
Alexey Eromenko (aeromenk@redhat.com)
1) New test module: iperf
http://kerneltrap.org/mailarchive/linux-kvm/2009/5/31/5840973/thread
Rebase made, made some comments to it.
* The idea of shipping binaries doesn't look very appealing to me
* Autotest already has an iperf test, might be worth a look for linux guests
Pending some issues during review.
--------------------------------------------------------------------------------
next reply other threads:[~2009-06-22 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 13:24 Lucas Meneghel Rodrigues [this message]
2009-06-23 4:12 ` Latest kvm autotest patch queue sudhir kumar
2009-06-25 13:02 ` jason wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1245677063.2778.30.camel@freedom \
--to=lmr@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mgoldish@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox