tools/check_patch.py: Accept multiple patchwork patch IDs

Different from github, patches on patchwork are individual
and there's no concept of a patchset. Therefore, verifying
a large patchset is a painful process.

Make it easier by allowing to specify several IDs, separated
by comma.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
virt: Add get_primary_serial functions for VMXML class.

Signed-off-by: Yu Mingfei <yumingfei@cn.fujitsu.com>
virt: Add ttyconsole function for virsh module.

Signed-off-by: Yu Mingfei <yumingfei@cn.fujitsu.com>
virt-libvirt: Add configuration for virsh ttyconsole test.

Signed-off-by: Yu Mingfei <yumingfei@cn.fujitsu.com>
virt-libvirt: Add test module of virsh ttyconsole.

Signed-off-by: Yu Mingfei <yumingfei@cn.fujitsu.com>
virt: add virsh function for virsh domjobabort

Signed-off-by: liyang <liyang.fnst@cn.fujitsu.com>
libvirt: Add new test virsh_domjobabort

Signed-off-by: liyang <liyang.fnst@cn.fujitsu.com>
virttest.qemu_virtio_port: Log the GW output on failure

Log the output on failure after read-out too.

Signed-off-by: Lukáš Doktor <ldoktor@redhat.com>
qemu.tests.virtio_console: Check for new data in loopback test

Thread might be alive, but hung on data recv/send. With this check
the test is interrupted after 1s of inactivity. It doesn't check for
new data on the sender thread as with some settings (big send buffer
and small recv buffers) the queue might be filled and this thread
has to wait for new data. This is expected behaviour.

Signed-off-by: Lukáš Doktor <ldoktor@redhat.com>
qemu.tests.virtio_console: Fix incorrect variable name and style

Signed-off-by: Lukáš Doktor <ldoktor@redhat.com>
virttest.qemu_virtio_port: Modify GuestWorker cleanup to suit windows

Windows doesn't have killall command and the worker is killed by the
missing connection anyway.

Signed-off-by: Lukáš Doktor <ldoktor@redhat.com>
Add MAINTAINERS file

Add a file with the maintainer's names for the virt
test project.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
check_patch.py: Catch exceptions during pylint run

pylint (or some of the dependent libraries) also has
bugs, so when they happen we don't want to spoil our
entire run. Let's catch the exceptions and report them.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
tools/check_patch.py: Exclude files from check only on old python

We do all possible to run static checking of modules
on older python, given that it is easier to spot
python 2.4 non compliances. However, we have a bunch
of quirks with files on older python. Therefore, let's
skip certain files from the checks if running under
py < 2.5.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
virt: Ignore vim swap files

Signed-off-by: Chris Evich <cevich@redhat.com>
run: Introduce --use-malloc-perturb specific qemu flag

Setting the environment variable MALLOC_PERTURB_ to
a non zero value [1] helps to find out some subtle
memory allocation problems, and it is being used in
our test grid. However, by default, the virt test
runner doesn't use it.

Add the new, qemu test specific --use-malloc-perturb flag
and set it to 'yes' (use the env variable) by default.
This way we're being more strict, which makes sense
in the context of a test suite. If people want to double
check the behavior of the test without the flag, just
use '--use-malloc-perturb no'.

[1] http://udrepper.livejournal.com/11429.html

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
virt-libvirt: Add fakeroot as recommended program

We depend on '/usr/bin/fakeroot' to install from iso's, but
it was not required or suggested by get_started.py.

Signed-off-by: Chris Evich <cevich@redhat.com>
Merge pull request #293 from cevich/getstarted_fakeroot

virt-libvirt: Add fakeroot as recommended program
run: Add missing argument for disk_bus

Signed-off-by: Qingtang Zhou <qzhou@redhat.com>
qemu_storage: Stop ignoring failures creating VM images

By default, the qemu_storage code is ignoring failures
when qemu-img fails to create a disk image. This happens
because the failure is actually considered only if the
(terribly undocumented) param 'check_output' is set to
yes.

Since there's no 'check_output' on any .cfg file
in the virt-test repo, the failures will never be
considered and virt-tests will happily proceed, even
though a world of pain and suffering will follow.

Since there are future tests that might require the
output of the creation command, we'll fix the problem
by:

1) Introducing a ignore_errors boolean parameter to
the .create() method, when set to true it'll make
the method to not raise an error on failure.

2) Making the method return a fixed tuple
(path to the image created, object with the result
of the command). With the result object, it is easy
to get outputs as they are attributes of the said
object.

This also has the nice side effect of not requiring
the check_output parameter anymore.

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