mirrors/crosvm
1
0
Fork 0
mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2025-02-10 20:19:07 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

README.md: Add more known issues for running crosvm on Linux

Browse source 
BUG=none
TEST=none

Change-Id: Ic63772785256bc01648ec53e60ec725ee14fbd88
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2896073
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
Commit-Queue: Fergus Dall <sidereal@google.com>
This commit is contained in:
Fergus Dall 2021-05-14 19:44:39 +10:00 committed by Commit Bot
parent 96e3fb363f
commit 2f4a80f366
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
README.md
View file

@ -54,6 +54,15 @@ sudo apt install build-essential libcap-dev libgbm-dev libvirglrenderer-dev libw
```
Known issues:
* Even with the following points, jailed devices seem to crash for unclear
reasons. If you run into this, you can add `--disable-sandbox` to run
everything in a single process.
* If your Linux header files are too old, you may find minijail rejecting
seccomp filters for containing unknown syscalls. You can try removing the
offending lines from the filter file, or add `--seccomp-log-failures` to the
crosvm command line to turn these into warnings. Note that this option will
also stop minijail from killing processes that violate the seccomp rule,
making the sandboxing much less aggressive.
* Seccomp policy files have hardcoded absolute paths. You can either fix up
the paths locally, or set up an awesome hacky symlink: `sudo mkdir
/usr/share/policy && sudo ln -s /path/to/crosvm/seccomp/x86_64