aboutsummaryrefslogtreecommitdiff
path: root/qemu-io.c
diff options
context:
space:
mode:
authorMax Reitz <mreitz@redhat.com>2020-11-02 17:18:59 +0100
committerDr. David Alan Gilbert <dgilbert@redhat.com>2020-11-02 19:23:48 +0000
commitaf1bb3fe7f146fafdaadb479975ca2b53b49df40 (patch)
treea7133f949d8e485930ebda9971321aacea89fa34 /qemu-io.c
parent0a7798037acb65cf4e9d64372690a47018e60d02 (diff)
downloadqemu-af1bb3fe7f146fafdaadb479975ca2b53b49df40.zip
qemu-af1bb3fe7f146fafdaadb479975ca2b53b49df40.tar.gz
qemu-af1bb3fe7f146fafdaadb479975ca2b53b49df40.tar.bz2
tests/acceptance: Add virtiofs_submounts.py
This test invokes several shell scripts to create a random directory tree full of submounts, and then check in the VM whether every submount has its own ID and the structure looks as expected. (Note that the test scripts must be non-executable, so Avocado will not try to execute them as if they were tests on their own, too.) Because at this commit's date it is unlikely that the Linux kernel on the image provided by boot_linux.py supports submounts in virtio-fs, the test will be cancelled if no custom Linux binary is provided through the vmlinuz parameter. (The on-image kernel can be used by providing an empty string via vmlinuz=.) So, invoking the test can be done as follows: $ avocado run \ tests/acceptance/virtiofs_submounts.py \ -p vmlinuz=/path/to/linux/build/arch/x86/boot/bzImage This test requires root privileges (through passwordless sudo -n), because at this point, virtiofsd requires them. (If you have a timestamp_timeout period for sudoers (e.g. the default of 5 min), you can provide this by executing something like "sudo true" before invoking Avocado.) Signed-off-by: Max Reitz <mreitz@redhat.com> Message-Id: <20201102161859.156603-8-mreitz@redhat.com> Tested-by: Eduardo Habkost <ehabkost@redhat.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Diffstat (limited to 'qemu-io.c')
0 files changed, 0 insertions, 0 deletions