Links with downloadable images for virt tests¶
This is a central location that we aim to keep up to date with locations of iso files that might be needed for testing.
Update: Now we have a central location to define such downloads. In the source tree:
Contains a bunch of .ini files, each one with download definitions. It is expected that this will be more up to date than this page. You can see the available downloads and download the files using:
The windows utils file can be currently found at:
How to update winutils.iso¶
That’s basically a collection of files useful for windows testing. If you want to update that file, you’ll have to pick that iso file, extract it to a directory, make changes, remaster the iso and upload back to the main location.
Windows virtio drivers ISO¶
In Avocado we mainly use fedora/RHEL based windows virtio drivers ISO that can be obtained from:
You can find the JeOS images currently available here:
You can browse through https://avocado-project.org/data/assets/jeos/ and find other JeOS versions available.
How to update JeOS¶
The JeOS can be updated by installing it, just like a normal OS. You can do
that for example with
avocado-vt, selecting an unattended install test. In
this example, we’re going to use the unattended install using https kickstart
and network install:
$ avocado run io-github-autotest-qemu.unattended_install.url.http_ks.default_install.aio_native
The JeOS kickstart has a trick to fill the qcow2 image with zeros, so that we
can squeeze these zeros later with qemu img. Once the image is installed, you
can use our helper script, located at
scripts/package_jeos.py in the
avocado-vt source tree. That script uses qemu-img to trim the zeros of the
image, ensuring that the resulting qcow2 image is the smallest possible. The
command is similar to:
$ qemu-img convert -f qcow2 -O qcow2 jeos-file-backup.qcow2 jeos-file.qcow2
Then it’ll compress it using xz, to save space and speed up downloads for
avocado-vt users. The command is similar to:
$ xz jeos-file.qcow2.xz jeos-file.qcow2
As mentioned, the script is supposed to help you with the process.
If you want to use a custom image, please keep the following in mind:
- Per default configuration, the root account in the guests has a specific password. For example, Linux guests expect the password as defined in virttest/shared/cfg/guest-os/Linux.cfg.
- The guest user’s console configuration can have impact on the test code. We recommend to set TERM=dumb in case of bash. This suppresses control characters.