This test cover some device assignment feature test case
Signed-off-by: NFeng Yang <fyang@redhat.com>

sr_iov_hotunplug.py is not only used by sr-iov test case. So rename it
as pci_hotunplug.py
Signed-off-by: NFeng Yang <fyang@redhat.com>

Signed-off-by: NFeng Yang <fyang@redhat.com>

test:
   guest_suspend
   guest_pause_resume
Signed-off-by: NJiří Župka <jzupka@redhat.com>

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

1). add step that reboot guest when it recover from s3/s4
2). update workaround_eject_time from 0s to 5s
Signed-off-by: NXu Tian <xutian@redhat.com>

systemd add new udev rule to prevent media eject, this commit will
disabled the udev rules before cdrom test to avoid test failed;
Signed-off-by: NXu Tian <xutian@redhat.com>

New test to mirroring block device to nfs server/iscsi disk
Signed-off-by: NXu Tian <xutian@redhat.com>

This tests the disk hotplug/unplug functionality.
 1) prepares multiple disks to be hotplugged
 2) hotplugs them
 3) verifies that they are in qtree/guest system/...
 4) unplugs them
 5) verifies they are not in qtree/guest system/...
 6) repeats $repeat_times
 *) During the whole test stress_cmd might be executed
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

As the parameter name is changed in qemu_storage.py. Update the cfg file
to fit it.
Signed-off-by: NYiqiao Pu <ypu@redhat.com>

Use the unified configs (scsiid=>unit, lun=>port) and store the images
in the usual location. The location '/tmp/%s' was used before because
python was unable to execute that long command and this prefix shorten
it significantly. Now autotest supports the way to deal with long
commands so we can finally store the images in the right location.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Before upstream qemu commit

  commit 56c4bfb3f07f3107894c00281276aea4f5e8834d
  Author: Laszlo Ersek <lersek@redhat.com>
  Date:   Tue Aug 6 12:37:11 2013 +0200

      dump: rebase from host-private RAMBlock offsets to guest-physical
      addresses

the dump-guest-memory QMP command used to write incorrect vmcores for
x86_64 guests with more than 3.5GB RAM. Add a testcase that creates a 4GB
guest, dumps its core, copies it into the guest, and analyzes it there
with the "crash" utility.

Related RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=981582
Related RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=990118Suggested-by: NAdemar de Souza Reis Jr. <areis@redhat.com>
Signed-off-by: NLaszlo Ersek <lersek@redhat.com>

We need step reboot guest after hotplug/unplug pci device to verify guest
not crash or hang when reboot;
Signed-off-by: NXu Tian <xutian@redhat.com>

Make some modification
Signed-off-by: NYunping Zheng <yunzheng@redhat.com>

Signed-off-by: NFeng Yang <fyang@redhat.com>

Run CrystalDiskMark in guest during s3 and s4.
Signed-off-by: NYiqiao Pu <ypu@redhat.com>

Add cmd /c to let the cmd session wait util the autoit scripts finished.
Otherwise it will return immediately after the autoit scripts start.
Also correct the script name.
Signed-off-by: NYiqiao Pu <ypu@redhat.com>

Using the program codespell

https://github.com/lucasdemarchi/codespell

We found a number of spelling mistakes, that could be
found and fixed. The result of the automated script
was double checked, of course.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

fix not all disk listed issue, get cdrom drive letter with
utils_misc.get_winutils_vol();
Signed-off-by: NXu Tian <xutian@redhat.com>

As an active NetworkManager may give us problems during
testing, stop the daemon before bonding. add a random wait
time before and after set_link.
Signed-off-by: NYunping Zheng <yunzheng@redhat.com>

Add missed test scenario '1 0', AKA "indirect_desc on, event_idx off" test;
Signed-off-by: NXu Tian <xutian@redhat.com>

Boot up a guest and malloc memory in host to force it to move
among the nodes of host.
Signed-off-by: NYiqiao Pu <ypu@redhat.com>

Boot up a guest have the same number of node as host. Each node in guest
only have 1 cpu. Try to malloc inside the guest with taksset. The memory
allocated in host should also in the same node as the cpu thread.
Signed-off-by: NYiqiao Pu <ypu@redhat.com>

Get host numa topology. Start and bind guest to the cpu in each node
one by one. Then check the memory status for qemu process.
The qemu process should mainly used the memory from the node that it
is binded to.
Signed-off-by: NYiqiao Pu <ypu@redhat.com>

Signed-off-by: NQingtang Zhou <zhouqt@gmail.com>

Signed-off-by: NQingtang Zhou <zhouqt@gmail.com>

Signed-off-by: NQingtang Zhou <qzhou@redhat.com>

Signed-off-by: NQingtang Zhou <qzhou@redhat.com>

Signed-off-by: NQingtang Zhou <qzhou@redhat.com>

Signed-off-by: NQingtang Zhou <qzhou@redhat.com>

Signed-off-by: NQingtang Zhou <qzhou@redhat.com>

Signed-off-by: NQingtang Zhou <qzhou@redhat.com>

Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>

Add some new variants/rules that will run some tests using
additional cpu_model_flags values. Especially:

 * CPU models that require "+apic" to be run on RHEL-6 hosts on Intel
   CPUs
 * CPU models that require "-abm,-sse4a" on Intel CPUs
 * CPU models that require using "-svm" because we don't enable nesting
   by default
Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>

We don't have any dumps for nokvm mode, so there's no point in enabling
all those variants that won't run because of missing dump files.
Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>

This will allow us to filter/document cases that require a specific host
CPU vendor. Enable only host_cpu_vendor=unknown by default.
Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>

This way we can make filters that include/exclude all RHEL-6 versions.
Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>

Add extra CPU model flags to some CPU models when the full CPU model
can't be tested easily.

Note that the code loads the reference files using the CPU flags as part
of the file name too (so we can be sure we're reading the right dump
file)  This way we can be sure we are comparing the output of "-cpu
Foo,-flag" against a dump that was surely generated using "-cpu
Foo,-flag" as well (not just "-cpu Foo").
Signed-off-by: NEduardo Habkost <ehabkost@raisama.net>

Those bits were changed on RHEL-6.1 without any compat code, so we need
to ignore the differences we find.
Signed-off-by: NEduardo Habkost <ehabkost@raisama.net>

The CPUID dump test kernel doesn't need USB devices.

This allows some older QEMU versions to be tested.
Signed-off-by: NEduardo Habkost <ehabkost@raisama.net>