-
Notifications
You must be signed in to change notification settings - Fork 1
GetStartedGuide
Getting Started¶
The first step towards using Avocado-VT is, quite obviously, installing it.
Installing Avocado¶
Start by following the instructions on this link.
Installing Avocado-VT¶
Having installed Avocado, you should already have the right repos enabled.
Note
If you use avocado from sources, use make link as described here.
Fedora and Enterprise Linux¶
Installing Avocado-VT on Fedora or Enterprise Linux is a matter of installing the avocado-plugins-vt package. Install it with:
$ yum install avocado-plugins-vt
Bootstrapping Avocado-VT¶
After the package, a bootstrap process must be run. Choose your test backend (qemu, libvirt, v2v, openvswitch, etc) and run the vt-bootstrap command. Example:
$ avocado vt-bootstrap --vt-type qemu
The output should be similar to:
12:02:10 INFO | qemu test config helper
12:02:10 INFO |
12:02:10 INFO | 1 - Updating all test providers
12:02:10 INFO |
12:02:10 INFO | 2 - Checking the mandatory programs and headers
12:02:10 INFO | /bin/7za OK
12:02:10 INFO | /sbin/tcpdump OK
...
12:02:11 INFO | /usr/include/asm/unistd.h OK
12:02:11 INFO |
12:02:11 INFO | 3 - Checking the recommended programs
12:02:11 INFO | /bin/qemu-kvm OK
12:02:11 INFO | /bin/qemu-img OK
12:02:11 INFO | /bin/qemu-io OK
...
12:02:33 INFO | 7 - Checking for modules kvm, kvm-intel
12:02:33 DEBUG| Module kvm loaded
12:02:33 DEBUG| Module kvm-intel loaded
12:02:33 INFO |
12:02:33 INFO | 8 - If you wish, you may take a look at the online docs for more info
12:02:33 INFO |
12:02:33 INFO | http://avocado-vt.readthedocs.org/
If there are missing requirements, please install them and re-run vt-bootstrap.
First steps with Avocado-VT¶
Let’s check if things went well by listing the Avocado plugins:
$ avocado plugins
That command should show the loaded plugins, and hopefully no errors. The relevant lines will be:
Plugins that add new commands (avocado.plugins.cli.cmd):
vt-bootstrap Avocado VT - implements the 'vt-bootstrap' subcommand
...
Plugins that add new options to commands (avocado.plugins.cli):
vt Avocado VT/virt-test support to 'run' command
vt-list Avocado-VT/virt-test support for 'list' command
Then let’s list the tests available with:
$ avocado list --vt-type qemu --verbose
This should list a large amount of tests (over 1900 virt related tests):
ACCESS_DENIED: 0
BROKEN_SYMLINK: 0
BUGGY: 0
INSTRUMENTED: 49
MISSING: 0
NOT_A_TEST: 27
SIMPLE: 3
VT: 1906
Now let’s run a virt test:
$ avocado run type_specific.io-github-autotest-qemu.migrate.default.tcp
JOB ID : <id>
JOB LOG : /home/<user>/avocado/job-results/job-2015-06-15T19.46-1c3da89/job.log
JOB HTML : /home/<user>/avocado/job-results/job-2015-06-15T19.46-1c3da89/html/results.html
TESTS : 1
(1/1) type_specific.io-github-autotest-qemu.migrate.default.tcp: PASS (95.76 s)
PASS : 1
ERROR : 0
FAIL : 0
SKIP : 0
WARN : 0
INTERRUPT : 0
TIME : 95.76 s
If you have trouble executing the steps provided in this guide, you have a few options:
- Send an e-mail to the avocado mailing list.
- Open an issue on the avocado-vt github area.
- We also hang out on IRC (irc.oftc.net, #avocado).
© Copyright 2014, Red Hat. Created using Sphinx 1.5.1.