scripts: Replace download_linux with prepare_linux

`prepare_linux` is capable of determining whether we need to invoke
`build_custom_linux` for building linux from source or `download_linux`
for dow

scripts: Replace download_linux with prepare_linux

`prepare_linux` is capable of determining whether we need to invoke
`build_custom_linux` for building linux from source or `download_linux`
for downloading pre-built.

Signed-off-by: Ruoqing He <heruoqing@iscas.ac.cn>

show more ...

build: Use binary kernel artifacts

The Linux kernel fork repository for Cloud Hypervisor now produces
prebuilt x86-64 and aarch64 binaries. Speed up the CI by using those
binaries.

Signed-off-by: R

build: Use binary kernel artifacts

The Linux kernel fork repository for Cloud Hypervisor now produces
prebuilt x86-64 and aarch64 binaries. Speed up the CI by using those
binaries.

Signed-off-by: Rob Bradford <rbradford@rivosinc.com>

show more ...

scripts: Update Azure storage location to access images

Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>

scripts: fix shell scripts according to shellcheck errors

Unify coding style of shell scripts in accordance with
shellcheck errors.

Signed-off-by: Ruslan Mstoi <ruslan.mstoi@intel.com>

scripts: fix shell scripts format according to shfmt

Unify coding style of shell scripts in accordance with shfmt checks.

Signed-off-by: Ruslan Mstoi <ruslan.mstoi@intel.com>

scripts: more compatible shebangs

Signed-off-by: Philipp Schuster <philipp.schuster@cyberus-technology.de>

scripts: propagate RUSTFLAGS and TARGET_CC to test scripts

There is no need to set them in the test scripts while the main script
already has them.

The consolidates how things are done.

Signed-off

scripts: propagate RUSTFLAGS and TARGET_CC to test scripts

There is no need to set them in the test scripts while the main script
already has them.

The consolidates how things are done.

Signed-off-by: Wei Liu <liuwe@microsoft.com>

show more ...

scripts: pass BUILD_TARGET directly to test scripts

There is no need to reconstruct it from within the scripts since the
main script already constructed it once.

Drop the previously useless setting

scripts: pass BUILD_TARGET directly to test scripts

There is no need to reconstruct it from within the scripts since the
main script already constructed it once.

Drop the previously useless setting of BUILD_TARGET from various
scripts. The value was always overwritten at a later point.

No functional change intended.

Signed-off-by: Wei Liu <liuwe@microsoft.com>

show more ...

scripts: Stop using "--no-default-features" for cargo build

Now feature "mshv" can be built together with "kvm". There is no need to
use "--no-default-features" any more.

Fixes: #5647

Signed-off-b

scripts: Stop using "--no-default-features" for cargo build

Now feature "mshv" can be built together with "kvm". There is no need to
use "--no-default-features" any more.

Fixes: #5647

Signed-off-by: Bo Chen <chen.bo@intel.com>

show more ...

Export RUST_BACKTRACE when it is not set explicitly

Currently we are overwriting the RUST_BACKTRACE if set
explicitly by user while running performance metrics tests
using dev_cli.sh

This change wi

Export RUST_BACKTRACE when it is not set explicitly

Currently we are overwriting the RUST_BACKTRACE if set
explicitly by user while running performance metrics tests
using dev_cli.sh

This change will allow user to set the RUST_BACKTRACE
while running performance metrics tests with dev_cli.sh
which invokes run_metrics.sh to run the performance binary.
We will set RUST_BACKTRACE to 1 if not set explicitly.

Signed-off-by: smit-gardhariya <gardhariya.smit@gmail.com>

show more ...

tests: integration: Use hugepage size to calculate the number of pages

The tests require a fixed amount of huge page memory to run, rather than
encode that as fixed number of huge pages it should be

tests: integration: Use hugepage size to calculate the number of pages

The tests require a fixed amount of huge page memory to run, rather than
encode that as fixed number of huge pages it should be calculated from
the size of memory required and the huge page size

Signed-off-by: Dom <peng6662001@163.com>

show more ...

scripts: Build dual kvm/mshv binary (like release.yaml) for integration testing

This means we are testing the same binary as we use in our releases.

Fixes: #4915

Signed-off-by: Rob Bradford <rober

scripts: Build dual kvm/mshv binary (like release.yaml) for integration testing

This means we are testing the same binary as we use in our releases.

Fixes: #4915

Signed-off-by: Rob Bradford <robert.bradford@intel.com>

show more ...

scripts: Make --hypervisor=mshv only affect features used by tests

This uncouples it from the features used for building the binary under
test allowing it to use the default build features.

This ch

scripts: Make --hypervisor=mshv only affect features used by tests

This uncouples it from the features used for building the binary under
test allowing it to use the default build features.

This change also removes the feature control from the test scripts where
it was never used (e.g. run_integration_tests_sgx.sh)

This allows the combined binary to be used for all testing but allows
the disabling of tests known not to work under mshv.

Fixes: #4915

Signed-off-by: Rob Bradford <robert.bradford@intel.com>

show more ...

scripts: Remove stripping from testing scripts

The binary stripping is now done by the toolchain for release builds.

Signed-off-by: Rob Bradford <robert.bradford@intel.com>

scripts: Remove common feature flag for mshv tests

Commit b2d1dd65f39 ("build: Remove "fwdebug" and "common" feature
flags") removed support for common features flag. But some of the
scripts are sti

scripts: Remove common feature flag for mshv tests

Commit b2d1dd65f39 ("build: Remove "fwdebug" and "common" feature
flags") removed support for common features flag. But some of the
scripts are still using that parameter specifically test related to mshv
hypervisor. Thus fix those scripts by removing common feature flag.

Signed-off-by: Smit Gardhariya <sgardhariya@microsoft.com>

show more ...

scripts: Mark git repository as safe

Git will refuse to generate information for the report if the repository
is owned by a different user (root in the container vs the real owner
outside).

e.g:

E

scripts: Mark git repository as safe

Git will refuse to generate information for the report if the repository
is owned by a different user (root in the container vs the real owner
outside).

e.g:

Error generating human readable git reference: fatal: unsafe repository ('/cloud-hypervisor' is owned by someone else)
To add an exception for this directory, call:

git config --global --add safe.directory /cloud-hypervisor

Signed-off-by: Rob Bradford <robert.bradford@intel.com>

show more ...

scripts: Use the same linux kernel build function everywhere

This commit unifies the custom linux kernel build in x86, Arm, and
performance metrics to the same function. Therefore, when bumping
the

scripts: Use the same linux kernel build function everywhere

This commit unifies the custom linux kernel build in x86, Arm, and
performance metrics to the same function. Therefore, when bumping
the kernel version, we can make sure we only need to make the change
in one place.

Signed-off-by: Henry Wang <Henry.Wang@arm.com>

show more ...

scripts: run_metrics: Always build the custom linux kernel

This commit makes sure that the custom linux kernel is always
rebuilt when running the performance metrics tests, and therefore
changes to

scripts: run_metrics: Always build the custom linux kernel

This commit makes sure that the custom linux kernel is always
rebuilt when running the performance metrics tests, and therefore
changes to the kernel config file is always caught.

Signed-off-by: Henry Wang <Henry.Wang@arm.com>

show more ...

scripts: aarch64: Build fio from source for performance metrics

On Arm64, the fio binary that comes from ubuntu distribution cannot
support io_uring, which is a required engine for the block
perform

scripts: aarch64: Build fio from source for performance metrics

On Arm64, the fio binary that comes from ubuntu distribution cannot
support io_uring, which is a required engine for the block
performance tests in performance metrics. Therefore this commit
build the fio from a relatively new version, and replace the native
ubuntu fio with the newly build one.

Signed-off-by: Henry Wang <Henry.Wang@arm.com>

show more ...

performance-metrics: prepare image and toolchain for AArch64

Prepare disk image, kernel image and toolchain for AArch64 before run
performance-metrics tests.

Signed-off-by: Jianyong Wu <jianyong.wu

performance-metrics: prepare image and toolchain for AArch64

Prepare disk image, kernel image and toolchain for AArch64 before run
performance-metrics tests.

Signed-off-by: Jianyong Wu <jianyong.wu@arm.com>

show more ...

scripts: Propagate "--test-filter" metrics test

Populate iff the the parameter is passed.

Following combinations tested:

scripts/dev_cli.sh tests --metrics -- --test-filter boot_time
scripts/dev_c

scripts: Propagate "--test-filter" metrics test

Populate iff the the parameter is passed.

Following combinations tested:

scripts/dev_cli.sh tests --metrics -- --test-filter boot_time
scripts/dev_cli.sh tests --metrics -- --test-filter boot_time -- --report-file /root/workloads/metrics.json
scripts/dev_cli.sh tests --metrics
scripts/dev_cli.sh tests --metrics -- -- --report-file /root/workloads/metrics.json

Fixes: #3787

Signed-off-by: Rob Bradford <robert.bradford@intel.com>

show more ...

Revert "scripts: Pass-through '--test-filter' option to `performance-metrics`"

This reverts commit 0be2d09778ab08e49f8888a79688a8e288b27671.

See: #3813

Signed-off-by: Rob Bradford <robert.bradford

Revert "scripts: Pass-through '--test-filter' option to `performance-metrics`"

This reverts commit 0be2d09778ab08e49f8888a79688a8e288b27671.

See: #3813

Signed-off-by: Rob Bradford <robert.bradford@intel.com>

show more ...

scripts: Pass-through '--test-filter' option to `performance-metrics`

To be consistently with the integration scripts, we now pass through the
`--test-filter` option of the test scripts to the `perf

scripts: Pass-through '--test-filter' option to `performance-metrics`

To be consistently with the integration scripts, we now pass through the
`--test-filter` option of the test scripts to the `performance-metrics`
binary. Now the following two commands achieve the same results:

`$./scripts/dev_cli.sh tests --metrics -- --test-filter boot_time_ -- --test-filter latency`
`$./scripts/dev_cli.sh tests --metrics -- -- --test-filter boot_time_ --test-filter latency`

Note that, the test scripts support only single occurrence of the
`--test-filter` option while the `performance-metrics` binary allows
multiple occurrences for filtering based on different keywords.

Fixes: #3787

Signed-off-by: Bo Chen <chen.bo@intel.com>

show more ...

scripts: Support custom arguments to the test binary with dev_cli.sh

The dev container interface script (e.g. 'dev_cli.sh') now supports the
following arguments syntax for running tests:

`tests [--

scripts: Support custom arguments to the test binary with dev_cli.sh

The dev container interface script (e.g. 'dev_cli.sh') now supports the
following arguments syntax for running tests:

`tests [--unit|--cargo|--all] [--libc musl|gnu] [-- [<test scripts args>] [-- [<test binary args>]]] `

In this way, we can pass custom arguments to the test binary (either
"cargo test" or "performance-metrics") with our dev container script.
For example:

`$ ./dev_cli.sh tests --metrics -- -- --report-file /tmp/metrics.json --test-filter latency`
`$ ./dev_cli.sh tests --integration -- --test-filter "test_serial" -- --nocapture --test-threads=1`

Fixes: #3739

Signed-off-by: Bo Chen <chen.bo@intel.com>

show more ...

scripts: Generate performance metrics with the dev container

Signed-off-by: Bo Chen <chen.bo@intel.com>