Add acpiphp for hotplug tests for suse products

Signed-off-by: Lin Ma <lma@suse.com>
Merge pull request #1511 from morecache/add-acpiphp-for-hotplug-tests

Add acpiphp for hotplug tests for suse products
perf: add scripts to collect guest/host sysinfo

The shell scripts are prepared for RHEL OS, the bat script is prepared for
Windows guests, user can write their own scripts to collect what they want
to get. These scripts are just referenced examples.

V2: improve call function (Lukas)

Signed-off-by: Amos Kong <akong@redhat.com>
Merge pull request #1489 from kongove/logscripts

perf: add scripts to collect guest/host sysinfo
Merge remote-tracking branch 'upstream/master'
Add a parameter to make using a custom path for the env file optional.

The parameter 'other_tests_dirs' is already used for defining
alternative directory for virt tests and using it as a custom
path for the env file is ambiguous. It also forces the file in
that directory for every user with custom virt tests. This commit
separates the parameters allowing for custom env directory and
custom virt tests directory.

Signed-off-by: Plamen Dimitrov <pdimitrov@pevogam.com>
Make guest Autotest verbosity configurable.

Signed-off-by: Plamen Dimitrov <pdimitrov@pevogam.com>
Move any libvirt related warnings that appear even when using solely qemu to a more appropriate place.

The warnings about missing libvirtd come from a check during
importing of the utils_libvirtd module. The module is imported
in env_process and therefore the warnings appear regardless of
whether we use libvirt or qemu. With this commit, the check will
still be performed but the warning will appear only if the user
actually intends to use the libvirtd control system.

Signed-off-by: Plamen Dimitrov <pdimitrov@pevogam.com>
Update network configuration together with all other parameters on QEMU VM creation.

The expected VM behavior is that with the creation of a VM, its
parameters will be updated. This is indeed how it works, however,
with the exception of network configuration which for some reasons
remains the old one and can be updated only if the entire VM object
is reinitialized.

Since in a virt test the VM is generally retrieved from the
environment, we should keep this well defined practice and avoid
reinitializing the VM object ourselves.

Signed-off-by: Plamen Dimitrov <pdimitrov@pevogam.com>
Allow fetching results from multiple guest Autotest runs during one virt test.

This is one of the upgrades necessary for running Autotest on
multiple guests and expanding the original idea of running only
on one main guest (main_vm). There are use cases (e.g. a networking
test) where more than one virtual machines are necessary. In such
cases the guest_autotest_results folder is overwritten by each
following Autotest run on a guest and as a result the folder
contains only the results from the last guest. This patch allows
for generating multiple guest result folders ordered by time of
execution.

Signed-off-by: Plamen Dimitrov <pdimitrov@pevogam.com>