run: Make safe behavior the default, change options

In order to save time in virt-test:

1) The JeOS image is uncompressed once and reused
   every test, unless it is explicitly asked with
   --restore-image

2) After a test is done, the VMs won't be shut down
   unless it is explicitly asked with --restart-vm

3) After a test is done, the pristine image won't
   be restored, unless it is explicitly asked with
   --restore-image-between-tests

All of those behaviors, while might bring speed ups
to the test process, they are not safe. As users
frequently don't have the visibility of that when
using the test suite, we found out that it's in the
best interest of users and developers that the
defaults are changed to safer options.

With this, the options mentioned above changed to

--keep-guest-running
--keep-image
--keep-image-between-tests

The wording 'guest' was chose over 'vm' due to the
fact we already have --guest-os. So, mostly an attempt
to keep consistency.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
Merge pull request #1227 from autotest/change-defaults-runner

run: Introduce new options, change virt-test default behavior
qemu.tests.cpuinfo_query: Fix #1198

The test is wired up to check RHEL machine types, that
will not be present on anything that is not strictly
RHEL 6.4, so restrict the test to those hosts.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
Merge pull request #1237 from autotest/fix-1198

qemu.tests.cpuinfo_query: Fix #1198
tools/run_pylint.py: Handle unforseen exceptions running pylint

In some testing scenarios, such as daily pylint checking
on py 2.4, we noticed the attempt to inspect some pygtk
code generated problems such as:

RuntimeError: could not open display

Making the rest of the checks to be aborted. Let's handle
the exceptions and print the messages as we should.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
Merge pull request #1241 from autotest/run-pylint-fix

tools/run_pylint.py: Handle unforseen exceptions running pylint
code checking: Drop exception handling for run_pylint

As we moved the check down the stack (given that we might
want to simply run run_pylint.py instead of the full blown
check_patch.py script).

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
virttest.env_process: try to catch windows guest bsod

This patch add bsod images catch when do crash check.
script will check whether the screendump image looks like a
bsod image by calculate the screendump image hamming distance
from the reference image(bsod image). if two images hamming
distance is less than the threshold(10), will mark this
screendump image as suspect, and raise guest BSOD error.
Configureation:
    check_guest_bsod = yes
    bsod_reference_img = XX.jpg (if not configure will use
    all the image under "share/deps/bsod_img")

Signed-off-by: Yunping Zheng <yunzheng@redhat.com>