This patch contains several test cases:
 * Execute "guest-sync" command to guest agent
 * Halt guest with command "guest-shutdown"
 * Reboot guest with command "guest-shutdown"
 * Shutdown guest with command "guest-shutdown"
 * Check the guest status with command "guest-fsfreeze-status"
 * Freeze guest with command "guest-fsfreeze-freeze"
 * Thaw guest with command "guest-fsfreeze-thaw"

Changes from V2:
 * Add some hook method which can inject test steps in
   guest fsfreeze testing.
   The methods are:
    - _action_before_fsfreeze
    - _action_after_fsfreeze
    - _action_before_fsthaw
    - _action_after_fsthaw
Signed-off-by: NQingtang Zhou <qzhou@redhat.com>

Create a new class QemuGuestAgentTest which contains
qemu guest agent installation/startup action.
Signed-off-by: NQingtang Zhou <qzhou@redhat.com>

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

The reboot variant is also test name. This leads to automatical runs
of this test when reboot test is specified. Changing this variant name
to reset should fix this issue.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Make it easier to apply and verify patches going on the
virt-test repo.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

The standalone_test script sets log directory for every
separated virt test now. But the log_line function in
utils_misc module can't work with this new directory
structure when there are multiple tests, it only checks
log file name, ignores file path info, and writes all
guest logs into the first virt test's log file.

This patch makes this log_line function check opened
file list with the full path of a file, to make log
msg are written into separated file for every test.
Signed-off-by: NQingtang Zhou <qzhou@redhat.com>

Signed-off-by: NShuping Cui <scui@redhat.com>

Currently, the commit test just use qemu_img, which
install in the system as default, to make the backup
file, and use the qemu_img_binary which get the path
from env file. Thus may bring some bugs.

For example, if just use the qemu source code and
don't make install to the system(that means the
system haven't installed a qemu to /usr/local/bin
or other system bin path, and autotest just test
the qemu using the git tree), the test will not
find the qemu_img_binary to create the backing_file.

and another problem is the binary used to backup and
commit may be different version, this may cause a bug.

To solve the problem, make the same binary to backup
and commit.
Signed-off-by: NMike Qiu <qiudayu@linux.vnet.ibm.com>

Those tools are more useful in the virt_test than they
are on autotest:

 * cd_hash.py: Tool to get disk md5/sha1 sums from files
 * regression.py: Tool to analyze regression results
 * virt_disk.py: Tool to create virtual cds and floppies
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

We might use 'iterations' parameters to execute one case
repeatedly, this patch makes the filename unique.
Signed-off-by: NAmos Kong <akong@redhat.com>

Expected result when opening virtconsole on windows is fail.
(actually it's dependent on the way we open it and currently
we use exclusive access so this test is not exactly related
to virtconsole, but to windows CreateFile function)
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Don't pass *args to Exceptions, use '%' instead.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Console version of test_rw_notconnect_guest used the second vio port,
but should use the first one instead. Test might fail in case VM
was recreated by the test.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

The bus handling in virtio_ports is broken. This patch modifies
it to realy work as described:
1) manual port definition
2) virtio_port_spread
3) without definition (but create the first bus)
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This setting suits the current version of virtio_console loopback
test.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This test starts loopback between first 2 ports and do the interruption.
Than it verifies, whether new data still arrives and the loss/dup is
in the allowed range. Multiple interruption loops are supported.

Variants:
* stop and cont
* port replug (sender, receiver, random)
* hibernate (S4)
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch adds _reconnect_none_mode version of the loopback thread.
It works as ordinary none_mode, but additionally disconnects in case
the port is unreadable and reconnects when possible.

It was necessarily to make virt global variable to be able to access
it in this thread.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch adds new features to GuestWorker:
* read_nonblocking - read-out the output of guest script (used when
                     the test fails and we want to see the output)
* ThSendCheck - adds reduced_set option (use only A-Z, simplifies debuging
* ThRecvCheck - adds debug mode. This mode executes completely different
                loop. It's better for debuging purposes. Not all
                functionalities are kept so you should know when you want
                to use it.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

The main loop of ThSendCheck worked incorrectly in case of port
reconnection. It could end-up with infinite number of reconnection
although only 10 was allowed. This patch makes ThSendCheck work
as it should.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

_init_guest() doesn't execute the worker. We have to do that manualy
before calling self._init_guest()
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

These settings were by default in subtests.cfg and windows version
overwrote this in guest-os.cfg. I'd like to move them to guest-os.cfg
for booth versions thus the'll be on the same place and it's gonna
be possible to get them in other tests too.

I put a comment to subtests.cfg about required variables.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch adds 2 variants of reboot test.
1) stressed - stresses all ports and gently reboots VM (supersede the
              poweroff test)
2) unplugged_ports - unplugs all ports and gently reboots VM
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch makes all virtio_console subtests contest_aware. This should
help debugging failures in subtests called from another subtest's body.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch stores the qemu_id to each VirtioPort. This is crucial
for virtio_console hotplug tests.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch adds new test failed_boot. It tries to create VM
and checks the error message.

As an example boot_nr0 test is added to cfg. It tries to create
VM with virtio port number = 0 (nr=0) which should fail due
to backward compatibility issue.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This allows to specify extra params of virtio_ports using
virtio_port_params_$name = "$param1 $param_2 ...".

Whitespaces are stripped and replaced with ','.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Add missing docstrings.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

On linux guest the guest_worker runs as a daemon so we have to
also kill the worker and remove it's pipes. Otherwise the new
instance would only connect to the old running version.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

1) Start migration with stressed VM.
2) Wait cancel_delay and then cancel migration.
3) Check if machine is alive on source host.
4) Stop stress of VM.
5) Migrate machine again.
6) Check if machine is alive on destination host.
Signed-off-by: NJiří Župka <jzupka@redhat.com>

Move this tapfd_helper tool from autotest repo into
this virt-test repo, since it's a virt-test only tool.

This script can help us boot up guest with autotest
generated qemu command line, it creates tap device
and updates the tapfd in given qemu cli.
Signed-off-by: NQingtang Zhou <qzhou@redhat.com>

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

Signed-off-by: NMarian Krcmarik <mkrcmari@redhat.com>

Signed-off-by: NMarian Krcmarik <mkrcmari@redhat.com>

Signed-off-by: NMarian Krcmarik <mkrcmari@redhat.com>

Form catches keyEvents and store them into a text file.
Signed-off-by: NMarian Krcmarik <mkrcmari@redhat.com>

Keys based on their scancodes are sent to client VM through monitor
when spice session of guest VM is in focused on the client VM.
Key events are caught on the guest VM and compared with expected
keycodes.
Signed-off-by: NMarian Krcmarik <mkrcmari@redhat.com>

When migration fails we have to emit exit_event to background threads
otherwise there are confusing errors in log.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Fail virtio_console subtest when background threads fails.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Make the loopback test fail when the background loopback thread
fails.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Supported tests:
* open
* multi_open
* close
* rw_host_offline
* basic_loopback
* migration
* poweroff
* hotplug
* rw_notconnect_guest
* max_ports

Note that current drivers often fails port initialization, corrupt
data and doesn't work as they should.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>