README: Document permissions needed for running.

Change-Id: Ia86cb49ffc89ad66fe67698e05968e6d6f19f743
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2231364
Auto-Submit: Andrew Walbran <qwandor@google.com>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
Commit-Queue: Stephen Barber <smbarber@chromium.org>
Tested-by: Stephen Barber <smbarber@chromium.org>
This commit is contained in:
Andrew Walbran 2020-06-05 11:31:58 +01:00 committed by Commit Bot
parent e187df2a5e
commit 55f21f7434

View file

@ -61,6 +61,11 @@ Known issues:
policies [into the crosvm binary](http://crbug.com/1052126).
* Devices can't be jailed if `/var/empty` doesn't exist. `sudo mkdir -p
/var/empty` to work around this for now.
* You need read/write permissions for `/dev/kvm` to run tests or other crosvm
instances. Usually it's owned by the `kvm` group, so `sudo usermod -a -G kvm
$USER` and then log out and back in again to fix this.
* Some other features (networking) require `CAP_NET_ADMIN` so those usually
need to be run as root.
And that's it! You should be able to `cargo build/run/test`.