To support both Python 3 and 2, use next(iter) or iter.__next__()
Signed-off-by: NHaotong Chen <hachen@redhat.com>

Signed-off-by: NXu Han <xuhan@redhat.com>

Signed-off-by: NXu Han <xuhan@redhat.com>

env["balloon_test_setup_ready"] value will keep available between
cases which lead to following two cases fail if run them together
with other balloon cases:
 - balloon_in_use..during_bg_test
 - driver_load_stress.with_balloon.during_bg_test
Signed-off-by: NLi Jin <lijin@redhat.com>

It will takes 90/180 seconds for guests getting to stable state in
balloon_check, it should send signal when it's ready so that other
operation can start after that.
driver_in_use should start background test only when guest memory get
to stable state to avoid bg_test check failure.
Signed-off-by: NLi Jin <lijin@redhat.com>

balloon service should be in running status after send INTERROGATE
signal via windows cmd.
Signed-off-by: NLi Jin <lijin@redhat.com>

1. When windows guest mem is small(e.g.1024M), calculated mem
min_size will be larger than ori_mem if ratio=0.5, which will
lead balloon cases fail.
2. When do balloon operation in linux guest, we should consider
crashkernel value as well,leaving enough memory for guest to
avoid guest OOM.

So modify the formula and leave a balloon buffer(300M in default)
for guest min_sz.
Signed-off-by: NLi Jin <lijin@redhat.com>

original sleep time(90s) is too small, balloon_check get guest used
memory at the very early stage. The value is not correct as it will
increase after all guest application up.
Signed-off-by: NLi Jin <lijin@redhat.com>

Signed-off-by: NYumei Huang <yuhuang@redhat.com>

Signed-off-by: NYumei Huang <yuhuang@redhat.com>

100s is a little short for some host, update the default value to 300,
otherwise need to update lots cfg file
Signed-off-by: NSuqin Huang <shuang@redhat.com>

qemu.tests.balloon_check:
1.set windows evict balloon_illegal_value to "0"

Signed-off-by:Aihua Liang<aliang@redhat.com>

qemu.tests.balloon_check:
1.get guest memory after system's up for windows guest
2.modify scripts for balloon_illegal test
3.remove param "os_type"
4.add get_win_mon_free_mem() under class BallooningTestWin()

qemu.test.cfg.balloon_check:
1.add new param "balloon_min_win"
2.remove param "os_type"
Signed-off-by: NAihua Liang <aliang@redhat.com>

Signed-off-by: NSuqin Huang <shuang@redhat.com>

Signed-off-by: NSuqin Huang <shuang@redhat.com>

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

sleep some seconds before check ballooned memory
Signed-off-by: NAihua Liang <aliang@redhat.com>

qemu.tests.balloon_check:
1.Optimize minimum ballooned size for windows guest
2.Optimize illegal test for windows guest
3.Seperate illegal as an individual cfg file
4.Compare windows guest's used memory for balloon check.
5.add function get_used_mem
6.modify the log info

qemu.tests.balloon_service:
1.Optimize code for balloon_service test.

qemu.tests.cfg.balloon_illegal:
1.add new cfg "balloon_illegal.cfg".
2.Adjust code for balloon_illegal test
3.Optimize code for windows's minimum balloon size

qemu.tests.cfg.balloon_service:
1.Set ratio to 0.1

qemu.tests.cfg.balloon_check:
1.Set ratio to 0.1
Signed-off-by: NAihua Liang <aliang@redhat.com>

No need to call get_ballooned_memory() again after
utils_misc.wait_for(lambda: compare_mem ==
                    self.get_ballooned_memory(),...)
Signed-off-by: NWei Jiangang <weijg.fnst@cn.fujitsu.com>

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

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

Clean up imports across the board in tp-qemu. The criteria
followed was:

1) Remove unnecessary imports
2) Turn multi imports from a single entry point to one
   import per line. This increases both patch and
   source code readability.
3) Separate blocks of imports with a line:
   * Python standard library imports
   * Autotest imports
   * virttest imports
   * Internal tp-qemu imports
4) Remove try/except blocks refering autotest libs and
   stick with the virttest.staging copy

This paves the way for the future removal of autotest
references, replacing those references with avocado ones.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

The new pep8 adds W503 line break before %s check. This is mass style
update of autotest framework without any actual changes.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Some subtest like reboot will cause memory inside guest ballooned
from original value again. So need wait for the memory size inside
guest adjust to the ballooned value again after the subtest finished.
Signed-off-by: NYiqiao Pu <ypu@redhat.com>

There's no need to have the name of the "run_<name>" method (main
test entry point) depend on the test name. So, for simplicity sake,
let's just name the test entry point "run".

I have decided to not fallback gracefully to the previous naming
convention as I believe this can lead to confusion in the future.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Here, the author called out to exit(), which is not
the intended effect. The actual exit condition is
`return`.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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

Now have two different class for Windows and Linux balloon test. Most of the
functions in these classes are same and inherit from class BallooningTest.
They have different error_report and get_memory_status. Also add some different
method to set ballooned memory in cfg files. Now the ballooned memory size also
can be set by a given value or a ratio base on the assign memory value.
Signed-off-by: NYiqiao Pu <ypu@redhat.com>

Make virt-test to have a docstring style mostly compliant with
the sphinx's [1] format, reStructured text. This means that
we have to trade all '@' tags to be ':', mostly.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

With the help of the PEP8 script, a semi-automated clean
of the code base was made, and effectively changing some
of the coding style rules of our code base:

 * No more 2 lines spacing among functions
 * No more combined module imports

In the end, it was going to be too difficult to take
into consideration E501 (line length > 80) errors and
W601 (.has_key() is deprecated), so these were ignored,
at least for now.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

The memory should be reset to the origin value after
evict or enlarge. So that the next iterations tests can
pass when check memory before test
Signed-off-by: NMike Qiu <qiudayu@linux.vnet.ibm.com>

Use monitor.protocol to detect QMP and other QMP  monitor changes.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

This patch mainly does following improvements:

Update the method to check memory from check different ways
for different OS to check the memory change in the test which may
works for both Windows and Linux.

Add a param to check if run sub test to make the operation of
separate evict and enlarge cases easier.
Signed-off-by: NYiqiao Pu <ypu@redhat.com>

Confirm the memory status after sub tests from both monitor and
inside guests.

changes from v1:
  - error message update
Signed-off-by: NYiqiao Pu <ypu@redhat.com>

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

This test script has no error context and test step, this patch adds
them, and update some logging message.

Changes from V2:
 * Update docstring and error context message.
Signed-off-by: NQingtang Zhou <qzhou@redhat.com>

Make the free memory check command configurable.

changes from v1:
  - Add the Windows guest memory judge code as the value get from
    windows should charge with different method.
Signed-off-by: NYiqiao Pu <ypu@redhat.com>

This patch benefits from the better error message when key is missing
in config params. Instead of custom handling of missing param it
uses params[] directly.

I modified those params, where I was 100% certain that they are
required and doesn't have default value:
 * val = params.get(..) followed by if not val: raise...
 * int(params.get(...))
 * params.get(...).split()
 * commands which require string (eg. session.cmd(params.get(...)))

I didn't test all the tests before and after in order to verify
possible typos but I used pylint before and after, watching for
new errors (code rate before and after).
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

As part of our changes from kvm -> qemu.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>