instead of website
Signed-off-by: NWenli Quan <wquan@redhat.com>

1. When netdst is switch, set specified mtu on host/client/guest
(linux/windows) before netperf start tests.
2. The end of jumbo test, set back to default mtu
3. Update all error to error_context
Signed-off-by: NWenli Quan <wquan@redhat.com>

Enabled that two params bring a slightly cpu enlarge in test, so diable
them for performance issue.
Signed-off-by: NWenli Quan <wquan@redhat.com>

Ksm uses a lot of processing power, we need to disable it. it takes
30% cpu usage (16cpus) in my tests.
Signed-off-by: NWenli Quan <wquan@redhat.com>

Netperf client can not handle so many sessions(sessions_rr = 500)
Signed-off-by: NMaosheng Zhang <mazhang@redhat.com>

Signed-off-by: NXu Tian <xutian@redhat.com>

Now the guest statys collect functions are implemented and tested with
RHEL and Fedora guests. It may cause problem for other guests. So set
it default to no, only enable it for RHEL and Fedora guests.
Signed-off-by: NYiqiao Pu <ypu@redhat.com>

User wants to collect sysinfo of host/guest, but different users
might have different requests, and many kinds of system might be
used. So I would like to use custom-built scripts to collect the
information that will make users happy.

User needs to add shell scripts to autotest/client/tests/virt/shared/scripts/,
and set the script path in config file.

eg:
 #log_hostinfo_script = scripts/rh_perf_log_hostinfo_script.sh
 #log_guestinfo_script = scripts/rh_perf_log_guestinfo_script.sh
 #log_guestinfo_exec = bash
 #log_guestinfo_path = /tmp/log_guestinfo.sh

Then the script output will be saved to $test.resultsdir/sysinfo,
analyzer can use 'diff' to compare the system information when
regression occurs.

I will send a pull request to add to example scripts to virt-tests repo.
Signed-off-by: NAmos Kong <akong@redhat.com>

'rpm -qa |grep kvm' might return multiple packages

[amos@amosk logs]$ rpm -qa |grep kvm
qemu-kvm-1.6.1-3.fc20.x86_64
libvirt-daemon-kvm-1.1.3.3-2.fc20.x86_64

[amos@amosk logs]$ rpm -q qemu-kvm
qemu-kvm-1.6.1-3.fc20.x86_64
Signed-off-by: NAmos Kong <akong@redhat.com>

Signed-off-by: NAmos Kong <akong@redhat.com>

The largest timeout_netperf_start should be int(l) * 0.5,
if netperf threads start all at once, it will still need
int(l) * 0.5 time waste. Therefore, the netperf_start_timeout
overhead is not needed.
Signed-off-by: NWenli Quan <wquan@redhat.com>

During the review of the repository split, it was pointed
out that 'agnostic' was a rather strange word, so we'll go
with 'generic'. I opted for not rebasing the PR, since I
had many problems when trying to do so.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

This will make it easier when we're splitting these
tests into their own repositories.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Get netperf src package from web;
Make the script compatible with netperf 2.6.0;
Modify the method of get winutils vol;
Modify the method of start netserver in windows guest
Using wait_for  to wait until all net perf clients start to work;
Reorganize the configure file.
Signed-off-by: NYunping Zheng <yunzheng@redhat.com>

Remove the limit of virtio_net, make the test support different types of
network adapters like e1000 and rtl8139
Signed-off-by: NYunping Zheng <yunzheng@redhat.com>

this patch:
1.fix the issue netperf cannot login with two nics,
2.add  netperf test support tcp_crr protocol
3.add an automated way to get the cdrom drive number.
4.modify the file path of netperf.tar.gz. now should
put the src file under "virt/shared/deps"
5.add more step info

some options were added into netperf.py, but it's only assigned for
netperf_win, this patch adds them for linux netperf.
Enable bridge parameters by default, use can fix it in tests.cfg if it's
needed.

We experientially suggest test-time should be not less than 60s.
Signed-off-by: NAmos Kong <akong@redhat.com>

We've only spot this mistake now :(
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Enable demo mode of netperf, process mixed demo results to drop
unstable factors, only compute the effective demo results when
all the threads work. This would make performance result more
stable.

We start many clients and watch the demo output, if all the threads
really work, then start to record the interrupt/packet number, and
count the cpu usage. After a fixed test time, record the final
interrupt/packet number.
Signed-off-by: NAmos Kong <akong@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

In order to have self describing tests, split the original
subtests.cfg in several per test files, and create subtests.cfg
out from this information.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>