summaryrefslogtreecommitdiffstats
path: root/README
blob: 45e2d11801b06076fc7bd07ee8d9aac6326db396 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
Test cases for testing the new virtio-console functionality that
exposes multiple ports to guests for generic communication.

Files:
test-virtserial.c: Standalone test program that can be run in the
  guest.
auto-virtserial.c: Runs automated tests. To be run on the host.
auto-virtserial-guest.c: Runs automated tests, to be run on the guest.
run-test.sh: Starts qemu and runs the automated tests

Setup:
In my guest (f11-auto.qcow2), I've put the auto-virtserial-guest
program in /etc/init.d/ and put a line in /etc/rc.local to invoke it
upon boot:

<guest /etc/rc.local>:
/etc/init.d/auto-virtserial-guest &

When run-test.sh is invoked with such a guest, when the guest comes
up, the tests start running automatically.

Some settings in the run-test.sh script should be tweaked to match
your environment (especially the guest image file, qemu location,
etc.).

These programs are sensitive to some details, like the host program
(auto-virtserial) has to be started before the guest invokes
auto-virtserial-guest program. Also the parameters passed to the qemu
invocation in run-test.sh are assumed to be in that order in
auto-virtserial.c, like the ports which have caching enabled,
throttling enabled, the byte limits and so on.

More work is needed to make these programs fully ready; if you wish
you contribute, send me an email at <amit.shah@redhat.com>

Amit