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

Since 0.14.0 is the current version of autotest being
shipped on Fedora through RPMs, make the virt tests
compatible with this version. When we get to 0.15.0
routinely available, we might drop this change.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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

Refactor virt_test_assistant to create the config files
in the appropriate places, so listing tests works out of
the box, even if user didn't run get_started.py first.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

We're not supposed to install JeOS, unless on the libvirt
case, where we have to import the JeOS image so libvirt
can create a domain XML for it. So restrict tests with
JeOS to only those mentioned.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

When looking at the test list, we should only list
supported tests for each virt type (it doesn't make
sense to run virsh tests on kvm, as well as it's not
possible run tests that require a monitor interface
to work).
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Introduce an additional param, virt_test_type,
that is a list of virt backends where the given
test works on, for example:

virt_test_type = kvm libvirt

Means the test can run under the kvm and libvirt
tests, while

virt_test_type = libvirt

Means the test is libvirt exclusive.

This will be used to filter available tests,
and help to fail incompatible tests.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

If the default base directory that holds guest images
and isos was modified, the setup stage won't be able
to find out the jeos images, and therefore, will
re-download the images to a location where it will not
be useful.

Let's figure out the correct base_dir from the location
of image1 instead.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Chris pointed out it's appropriate to ask whether the
user wants to download the minimal guest image instead
of just going ahead and downloading it. So be polite
and ask first on non interactive setup.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

In case '7za' is missing, we better report to the user
straight away, rather than just failing silently.
Also, we want to avoid as much as possible config
files not in their right places.

In order to accomplish that goal, check for 7za's
presence in the system on virt_test_assistant, and
throw an exception if it's not present. Also,
make sure we catch exceptions when calling
virt_test_assistant, to present error information
in a good way.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

In order to avoid confusion, move setup to the script
initially printed headers, so it can't be mistaken with
a regular test.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

In some cases, the test variant is irrelevant, in others,
JeOS lacks a toolchain for it to work. So, let's remove
them and leave a more meaningful list of tests for
people interested in JeOS.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Allow jeos tests to work fine if you choose to run
libvirt tests. The user will have to be educated to
specify unattended_install.import.import if he/she
wants to run tests dependent on guests.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Since now the default tests.cfg is based on JeOS, we
cleaned up the old file and added more useful examples,
such as sets similar to the ones we run on our automated
KVM regression infrastructure.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

With the new functionality to run tests, even when specifying
a custom config file we were applying a 'only migrate' block,
that's very likely to restrict all the tests run by the
specific configuration.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Now that run can list the tests available, also allow
to specify a list of tests (space separated):

./run -t kvm --tests boot_with_usb reboot_with_usb

And it'll select and run those.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Add an option --test-list, that has to be used in
conjunction with -t (test_type):

./run -t kvm --list-tests
(display list of tests)

It'll connect the list to a less pipe, if less is
available, similar to what git does. It'll show all
tests available for the JeOS so one of them can be
chosen.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

This introduces the flag --qemu-bin, that allows people
to specify an arbitrary qemu built on your box, such as:

./run -t kvm --qemu-bin /home/lmr/Code/virt-test.git/kvm/install_root/bin/qemu-system-x86_64

And this will automatically run the tests with that qemu.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

There's no reason why all tests can't use a single roof
for their activities, moreover, /var/tmp is a safer place
to store isos and disk images, considering that we might
have /tmp on tmpfs on Fedora 18 on.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Now setup log goes to main debug log, setup phase is
displayed as a test. Also, there was a bug on the
uncompress stage in case the image was already
uncompressed, fixed by passing the right flags to 7za.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

In Fedora, it requires less dependencies.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Modify the virt assistant function to:

 1) Download the JeOS image
 2) Setup the environment non interactively

So it all will be done without user intervention.
The first time the JeOS will have to be built,
a couple of minutes to download the 120MB compressed
image + 1 minute to uncompress the image will be
required, after that it'll keep using the uncompressed
image, unless you want to replace it by the pristine
file you have on your hard drive, then you have to call
run with --restore-image.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

After exploring some possibilities, we came up with a
minimal Fedora install, which presents an interesting
compromise between features and disk space. The idea
is to host the compressed image on my FedoraPeople
area and have code to automatically download it if it's
missing, and subsequently cache it.

The unattended install variant is in fact only for
people that, for some weird reason want to rebuild
the minimal guest on a convenient way, nothing more
than that.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

+ libvirt_xml:
    + Improved docstring
    + Removed uuid module usage
    + Removed duplicate method definitions
    + Fixed comment spelling mistakes
    + Added os_arch_machine_map property to LibvirtXML

+ utils_misc:
    + Remove unused Closure Class
    + Fixed indentation / spacing
    + Added comments

+ utils_misc unittest:
    + Cleaned up nested class/method definitions
    + Unfolded some complex assignments
    + Fixed indentation / spacing
    + Add some dict-method unittests

+ virsh:
    + Updated/Clarified module docstring
    + Removed unnecessary DaArgMangler class
    + Fixed specialized VirshClosure Class
    + Cleaned up VIRSH_EXEC usage & warning
    + Replaced old use of PROPERTIES with __slots__ (resolved TODO)
    + Enforced setting of 'uri' and 'virsh_exec' properties
    + Made VirshSession class record the uri for later comparison
    + Major VirshPersistant cleanup/bugfix
        + Added session acounting (helps unittests)
        + Added close_session method to unify behavior
        + Fixed new_session to properly close alive existing sessions
        + Fixed set_uri to open new session only on uri change WRT old session
        + Cleaned up virsh.command to work with VirshPersistant properly

+ virsh_unittest:
    + Added back unittest module (some tests ignored if no libvirt)
    + Added 8 tests for VirshClosure
    + Added VirshPersistent session count check to ConstructorsTest
    + Added help command cache tests
    + Added VirshPersistant test teardown double-check session accounting

+ libvirt_vm: Cleaned up hvm/pvm arch and machine-type detection/check

+ guest-os.cfg.sample:
    + Added vm_arch_name param for every OS defaulting uname -m
    + Removed a few guest os types that aren't used anymore
Signed-off-by: NChris Evich <cevich@redhat.com>

Thanks to Yu Mingfei <yumingfei@cn.fujitsu.com> for the original
virsh_rename_domain test which this is based upon. Exercises
virsh define and virsh_undefine plus auto-generated uuids.
Signed-off-by: NChris Evich <cevich@redhat.com>

Signed-off-by: NChris Evich <cevich@redhat.com>

Follow a properties and accessor-method pattern so allowing higher
level code to ignore all details of underlying XML format.  Also,
provide intermediate methods for working with XML related virsh
commands along-side the abstracted XML-manupulator classes.
Signed-off-by: NChris Evich <cevich@redhat.com>

The virt networking code in utils_misc and base classes from the virsh
and libvirt_xml modules were duplicating a lot of functionality.  Moved
the comonalities under a new utils_misc PropCanBase base class. Added
new unittests for the new base class and fixed up all usage mismatches.

Also moved Closure class from virsh into utils_misc so it's more
centrally located for common use.
Signed-off-by: NChris Evich <cevich@redhat.com>

    Test uses virttest for virtual machine management.

    /tests/openvswitch/
    preparing test environment:
      ./get_started.py

    tests:
    1) Performance test.
    2) Vlan tests.
    3) Ping test.
Signed-off-by: NJiří Župka <jzupka@redhat.com>

Allow creating of machine with tap devices which are not
connected to bridge, and add function to fill virtnet
object with address.
Signed-off-by: NJiří Župka <jzupka@redhat.com>

When autotest tries add tap to bridge then test recognize if
test is bridge is standard linux or OpenVSwitch.

And add some utils for bridge manipulation.
Signed-off-by: NJiří Župka <jzupka@redhat.com>

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

Turns out this caused for a long time a namespace
collision that confused pylint. So, in order to get
a fully clean run_pylint.py -q in the entire tree,
let's rename the test to autotest_control.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

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

Add a script that will run all unittests available on
virt tests source dir. With this it'll be easier to
run the unittests and have a quick glance of the code
state.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Fedora 18 introduces 'xterm-256color', which was not
accounted for on initial versions of the bcolors class.
Let's add it so we get colored output for this new
version of Fedora.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

This test script runs live snapshot after guest
fs is frozen, then check if the file created on
guest disk is correct.
Signed-off-by: NQingtang Zhou <qzhou@redhat.com>

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>