crosvm/e2e_tests
Wang Ningyuan 3fd003cefc e2e_tests: Use distinct tap name for each e2e test
In e2e tests, error 16 is thrown when a tap device is created when its
name is shared with another tap device. This makes the test flaky.
Distinct tap name is needed.

TEST=./tools/dev_container ./tools/presubmit crosvm_tests_x86_64
BUG=b:333090169

Change-Id: I205f69a81ef1f15c3a50c6aae5bcbcd80c30c99e
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5453013
Reviewed-by: Dennis Kempin <denniskempin@google.com>
Commit-Queue: Ningyuan Wang <ningyuan@google.com>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2024-04-16 02:17:42 +00:00
..
benches
fixture e2e_tests: wait for restore to complete before sending commands 2024-04-11 15:51:23 +00:00
guest_under_test e2e_test: Add a test for virtio-pvclock behavior 2024-03-13 09:05:25 +00:00
tests e2e_tests: Use distinct tap name for each e2e test 2024-04-16 02:17:42 +00:00
Cargo.toml e2e_tests: Add a helper to read guest clocks 2024-01-22 11:24:14 +00:00
README.md e2e_test: Update instructions to use locally built kernel/rootfs images 2024-01-05 04:50:21 +00:00

Crosvm End to End Tests

These tests run a crosvm VM on the host to verify end to end behavior. They use a prebuilt guest kernel and rootfs, which is downloaded from google cloud storage.

The e2e_tests can be executed by:

$ ./tools/run_tests --dut=vm -E 'rdeps(e2e_tests)'

Running with locally built kernel/rootfs

If you want to make changes to the kernel or rootfs, you have to specify the environment variables CROSVM_CARGO_TEST_KERNEL_IMAGE and CROSVM_CARGO_TEST_ROOTFS_IMAGE to point to the right files and then run cargo test.

With use_local_build.sh script, e2e_tests can be executed with custom kernel/rootfs as follows:

$ cd /path/to/crosvm
$ cd e2e_tests
$ source guest_under_test/use_local_build.sh
$ cargo test

Unsetting the variables will bring back you to the original behavior.

unset CROSVM_CARGO_TEST_KERNEL_IMAGE
unset CROSVM_CARGO_TEST_ROOTFS_IMAGE

Note: The custom images cannot be used with tools/run_tests.

Uploading prebuilts

Note: Only Googlers with access to the crosvm-testing cloud storage bin can upload prebuilts.

To upload the modified rootfs, you will have to uprev the PREBUILT_VERSION variable in:

  • ./guest_under_test/PREBUILT_VERSION

and request a permission to become a member of the crosvm-policy-uploader group.

Then run the upload script to build and upload the new prebuilts.

# Install QEMU-user-static to build aarch64 images
$ sudo apt install binfmt-support qemu-user-static
# Register binfmt_misc entries
$ docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
# Build and upload the new artifacts
$ ./guest_under_test/upload_prebuilts.sh

Never try to modify an existing prebuilt as the new images may break tests in older versions.