From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Michael Goldish <mgoldish@redhat.com>
Cc: autotest@test.kernel.org, kvm@vger.kernel.org, ryanh@us.ibm.com
Subject: Re: [Autotest] [KVM-AUTOTEST PATCH] KVM test: make use of tcpdump optional
Date: Tue, 25 May 2010 20:47:25 -0300 [thread overview]
Message-ID: <1274831245.2567.3.camel@freedom> (raw)
In-Reply-To: <1274102975-32453-2-git-send-email-mgoldish@redhat.com>
On Mon, 2010-05-17 at 16:29 +0300, Michael Goldish wrote:
> To disable tcpdump, set 'run_tcpdump = no' in a config file.
> If 'run_tcpdump' isn't set at all, it defaults to 'yes'.
>
> (Currently TAP mode cannot be used without tcpdump.)
Ok, I agree with your reasoning, commited as:
http://autotest.kernel.org/changeset/4562
Copying Ryan.
> Signed-off-by: Michael Goldish <mgoldish@redhat.com>
> ---
> client/tests/kvm/kvm_preprocessing.py | 2 +-
> client/tests/kvm/tests_base.cfg.sample | 1 +
> 2 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/client/tests/kvm/kvm_preprocessing.py b/client/tests/kvm/kvm_preprocessing.py
> index 50db65c..e11207a 100644
> --- a/client/tests/kvm/kvm_preprocessing.py
> +++ b/client/tests/kvm/kvm_preprocessing.py
> @@ -196,7 +196,7 @@ def preprocess(test, params, env):
> if "tcpdump" in env and not env["tcpdump"].is_alive():
> env["tcpdump"].close()
> del env["tcpdump"]
> - if "tcpdump" not in env:
> + if "tcpdump" not in env and params.get("run_tcpdump", "yes") == "yes":
> command = "/usr/sbin/tcpdump -npvi any 'dst port 68'"
> logging.debug("Starting tcpdump (%s)...", command)
> env["tcpdump"] = kvm_subprocess.kvm_tail(
> diff --git a/client/tests/kvm/tests_base.cfg.sample b/client/tests/kvm/tests_base.cfg.sample
> index c9dfd0b..1276267 100644
> --- a/client/tests/kvm/tests_base.cfg.sample
> +++ b/client/tests/kvm/tests_base.cfg.sample
> @@ -46,6 +46,7 @@ nic_mode = user
> #nic_mode = tap
> nic_script = scripts/qemu-ifup
> address_index = 0
> +run_tcpdump = yes
>
> # Misc
> run_kvm_stat = yes
prev parent reply other threads:[~2010-05-25 23:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 13:29 [KVM-AUTOTEST PATCH] KVM test: formatting improvements to scan_results.py Michael Goldish
2010-05-17 13:29 ` [KVM-AUTOTEST PATCH] KVM test: make use of tcpdump optional Michael Goldish
2010-05-17 13:29 ` [KVM-AUTOTEST PATCH] KVM test: use command line option wrapper functions Michael Goldish
2010-05-26 13:49 ` [Autotest] " Lucas Meneghel Rodrigues
2010-05-17 13:35 ` [KVM-AUTOTEST PATCH] KVM test: make use of tcpdump optional Lucas Meneghel Rodrigues
2010-05-17 14:32 ` [Autotest] " Michael Goldish
2010-05-25 23:47 ` Lucas Meneghel Rodrigues [this message]
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=1274831245.2567.3.camel@freedom \
--to=lmr@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mgoldish@redhat.com \
--cc=ryanh@us.ibm.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;
as well as URLs for NNTP newsgroup(s).