6b1a35298c
This CL implements PCI hotplug feature for virtio-net device. The feature is controlled by pci-hotplug feature flag and pci-hotplug-slots runtime flag. No behavior change to crosvm unless pci-hotplug-slots flag is set to a nonzero value. BUG=b:243767476 TEST=tools/presubmit TEST=e2e_test::tap_hotplug for TAP device hotplug and removal TEST=manual test for TAP device hotplug and removal with swap Change-Id: I5a60314293ef8a27981d7b550a61822491c254bb Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4473610 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Shin Kawamura <kawasin@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Ningyuan Wang <ningyuan@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Jason Iman <jasongustaman@chromium.org> |
||
---|---|---|
.. | ||
benches | ||
fixture | ||
guest_under_test | ||
tests | ||
Cargo.toml | ||
README.md | ||
run |
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.
Running with locally built kernel/rootfs
If the test needs to run offline, or you want to make changes to the kernel or rootfs, you have to
specify the environment variables CROSVM_CARGO_TEST_KERNEL_BINARY
and
CROSVM_CARGO_TEST_ROOTFS_IMAGE
to point to the right files.
The use_local_build.sh script does this for you:
$ source guest_under_test/use_local_build.sh
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. Never try to modify an existing prebuilt as the new images may break
tests in older versions.