Hi,
The shared folder is not created when I install the avocado and after running
the vt-bootstrap, I manually created the
shared/cfg/guest-os/Linux/LinuxCustom/foo.cfg
cat shared/cfg/guest-os/Linux/LinuxCustom/foo.cfg
- FooLinux:
image_name = images/foo-linux
It doesn't list the foo guest.
Thanks,
Chandrashekar
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Lukáš Doktor
Sent: Wednesday, February 7, 2018 9:51 PM
To: [email protected]; [email protected]
Subject: Re: [Avocado-devel] How to create a custom config image to import and
run the tests
Dne 31.1.2018 v 16:49 [email protected] napsal(a):
> How to add the user define guest and boot from the existing disk.img and run
> the minimal tests, like
>
> I don't include migration, nfs, glusterfs, etc.
>
> Could you please help me on the same.
>
> Thanks,
> Chandrashekar
>
Hello Chandrashekar,
I assume you're talking about Avocado-vt tests, right? There the disk image is
specified by the `--vt-guest-os` "profile" which are defined in
`$AVOCADO_VT/shared/cfg/guest-os/*` config files. You can see that there are
many values set which change many aspects throughout the test execution mainly
about the allowed devices (virtio_blk/virtio_scsi/...) or ways to interact with
os (yum, apt-get, whatever windows allows...), but many things are common even
across different profiles.
So, to answer your question, simply find the closest match either by looking
through the files or using `avocado list --vt-list-guests` (probably combined
with `--vt-arch aarch64 --vt-machine-type arm64-pci`) which lists the profiles
available for given arch/machine-type. Note that differences between
architectures are usually quite small so if need for example `debian` you can
copy the `x86_64` profile and change the values that are defined there and it
should "mainly" work. Keep in mind you have to run `avocado vt-bootstrap` to
propagate the changes in `$AVOCADO_VT/shared` to Avocado-vt.
Once you pick a suitable profile you can simply run `avocado --show all run
--vt-guest-os XXX -- boot` which will most probably fail saying "image
/foo/bar/baz/XXX.qcow2 not found" which gives you the location where you need
to put your image. Once the image is there Avocado will assume it's the correct
image of that OS, it'll create a backup and use it in tests usually reverting
back after testing. There are some exceptions where the image gets overridden
and that are mainly the `unattended_install` tests which try to install that
kind of OS using the chosen media (cdrom, url, ...).
Note that for start you should be able to use the default, which is `JeOS.27`
which is essentially a stripped out Fedora 27 shipped by us for all main
architectures (aarch64, ppc64, ppc64le, x86_64 and s390x) so `avocado run boot`
should usually work.
Happy testing,
Lukáš
