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>

Notify user that he have to install python and pywin32 on his
tested machine.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch changes the GuestWorker to run on windows and adjusts
virtio_console test also to support windows testing.

Currently supported tests are:
* open
* multiopen
* close
* max_serials_and_conosles (windows won't initialize consoles. I need
           to check it with the developer if this is a bug or feature)
* rw_host_offline (fails, need to check with developer the expected
                   results)
* basic_loopback (fails, data are corrupted)
* loopback (fails, data are corrupted)
* migrate (fails, data are corrupted)
* hotplug (fails, windows won't initialize consoles properly)
* shutdown

Beware on my laptop in 50% the ports were not initialized properly,
VM reboot usually helped (not always). You might use "Winobj" program
to list \\Device\vport* ports or \\.\$port_name devices/symlinks.

I checked the data corruption and it happends (winXP->Fedora18)
pretty regularly even with Amit's C++ testing script.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch adds windows support for sending/receiving data
from/to guest.

It also adds send_loop support for guest sender thread.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch enables virtio_console_guest.py to initiate loopback
under windows.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This patch enables virtio_console_guest.py script to run on Windows.
It's a first very limited version.

VirtioGuest class now contains all functions, which might be used in
virtio_console tests and should be implemented.

The Posix version is the original Linux version with minor bugfixes.

The Nt version is simplified version which currently doesn't support
port reconnection (migration) and implements only "open" and "close"
features.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

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

Signed-off-by: Yu Mingfei<yumingfei@cn.fujitsu.com>

Signed-off-by: Yu Mingfei<yumingfei@cn.fujitsu.com>

Signed-off-by: Yu Mingfei<yumingfei@cn.fujitsu.com>

Signed-off-by: Yu Mingfei<yumingfei@cn.fujitsu.com>

It took us a while to notice that the source for good
images was incorrect in the backup code:

10/19 08:07:59 DEBUG|   storage:0185| Copying
/tmp/kvm_autotest_root/images/win7-64-sp1.qcow2.backup ->
/tmp/kvm_autotest_root/images_archive/win7-64-sp1.qcow2.good.XWUf
10/19 08:07:59 INFO |   storage:0189| No source file
/tmp/kvm_autotest_root/images/win7-64-sp1.qcow2.backup, skipping copy...

Let's fix that.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Test the command virsh nodecpustats

(1) Call the virsh nodecpustats command for all cpu host cpus
    separately
(2) Get the output
(3) Check the against /proc/stat output(o) for respective cpu
    user: o[0] + o[1]
    system: o[2] + o[5] + o[6]
    idle: o[3]
    iowait: o[4]
(4) Call the virsh nodecpustats command with an unexpected option
(5) Call the virsh nodecpustats command with libvirtd service stop
Signed-off-by: NSatheesh Rajendran <sathnaga@linux.vnet.ibm.com>

Signed-off-by: NSatheesh Rajendran <sathnaga@linux.vnet.ibm.com>

Signed-off-by: NSatheesh Rajendran <sathnaga@linux.vnet.ibm.com>

connect_uri is used for canonical_uri(),but it will not
be changed even remote test. While the connect_uri for
remote test should be target_uri.

Signed-off-by: Yu Mingfei<yumingfei@cn.fujitsu.com>

The tools subdirectory will include useful scripts for
users of the virt tests. The first app is the koji/brew
pkg spec tool, that allows people to list information
about a koji or brew build.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Pylint correction makes migration_multi_host_fd test dysfunctional.
Signed-off-by: NJiří Župka <jzupka@redhat.com>

The test iterates through pkt_sizes even we're not on
windows, so move its definition up.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

I found later that the problem I was referring in the
below issue relates only to the virsh vcpupin testcase
since it uses qemu_monitor_command function.

After the introduction of virsh class, there is a function
named 'command' got introduced, which was getting conflict
with the command variable and below patch solves the issue.

https://github.com/autotest/autotest/issues/555

Excerpt of error log:
----
17:52:44 DEBUG| Destroying VM
17:52:44 WARNI| Requested MAC address release from persistent vm vm1.
Ignoring.
17:52:44 ERROR| FAIL -> TypeError: 'str' object is not callable
FAIL (3.42 s)
----

Sorry for the confusion if any caused.
Signed-off-by: NSatheesh Rajendran <sathnaga@linux.vnet.ibm.com>

Adding a test to verify a remote-viewer connection
with the full screen option the guest takes the
resolution of the client, and it also supports the
negative test if connected w/o the full screen
option the resolution of the guest will not take
on the resolution of the client.
Signed-off-by: NVimal Patel <vipatel@redhat.com>

The purpose of the test is to setup the VMs for
the full screen tests, change the resolution of
the guest VM so the VMs have different resolutions,
and start spice-vdagentd prior to remote-viewer
connection.
Signed-off-by: NVimal Patel <vipatel@redhat.com>

Signed-off-by: NVimal Patel <vipatel@redhat.com>

Defining fullscreen_setup & fullscreen tests, and
add a full_screen parameter to the rv_connect test.
Signed-off-by: NVimal Patel <vipatel@redhat.com>

Signed-off-by: NVimal Patel <vipatel@redhat.com>

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

This patch groups multihost test into one group to which is
added machine types variant of test.
Signed-off-by: NJiří Župka <jzupka@redhat.com>

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