Nayana BidariandgVisor bot
0890b4de46
This change extends the split filesystem checkpoint/restore feature to support saving and restoring only a subset of filesystems (specified by paths). This supports a "combined restore" mechanism where some memory files (tmpfs backings) are restored from the filesystem checkpoint, while others are restored from the main sentry checkpoint. - Added `SplitFSCheckpointPaths` to `SaveOpts` to allow specifying paths for partial FS checkpoints. - Updated `createPrivateMemoryFile` to return whether it successfully loaded state from the filesystem checkpoint. - Track which memory files were loaded from the FS checkpoint during restore (`fsCheckpointedMfs`) and pass this information to the kernel via context (`CtxFSCheckpointedMemoryFiles`). - In `loadPrivateMemoryFiles` (during sentry restore), only load memory files from the sentry checkpoint if they were not already loaded from the FS checkpoint. - Added validation to ensure each memory file is restored from exactly one source (no duplicates, and none are missed). PiperOrigin-RevId: 964518735
Tests
The tests defined under this path are verifying functionality beyond what unit tests can cover, e.g. integration and end to end tests. Due to their nature, they may need extra setup in the test machine and extra configuration to run.
- syscalls: system call tests use a local runner, and do not require additional configuration in the machine.
- integration: defines integration tests that uses
docker runto test functionality. - image: basic end to end test for popular images. These require the same setup as integration tests.
- root: tests that require to be run as root. These require the same setup as integration tests.
- util: utilities library to support the tests.
For the above noted cases, the relevant runtime must be installed via runsc install before running. Just note that they require specific configuration to
work. This is handled automatically by the test scripts in the scripts
directory and they can be used to run tests locally on your machine. They are
also used to run these tests in kokoro.
Example:
To run image and integration tests, run:
make docker-tests
To run root tests, run:
make sudo TARGETS=test/root:root_test
There are a few other interesting variations for image and integration tests:
- overlay: sets writable overlay inside the sentry
- hostnet: configures host network passthrough, instead of netstack
- kvm: runsc the test using the KVM platform, instead of systrap
The test will build runsc, configure it with your local docker, restart
dockerd, and run tests. The location for runsc logs is printed to the output.