aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndy Lutomirski <luto@kernel.org>2019-10-10 10:06:18 -0700
committerAndy Lutomirski <luto@kernel.org>2019-10-10 10:06:18 -0700
commit9d23dfbff3d3f52b00bc7cef0ea65f3a46f768b9 (patch)
treedc6285d731b804c5ad1362a1f945f99321f329d7
parent9a0ed9f43dbb2a510c802d8afe92f39f66e5d156 (diff)
downloadvirtme-9d23dfbff3d3f52b00bc7cef0ea65f3a46f768b9.tar.gz
Update README for modules
Signed-off-by: Andy Lutomirski <luto@kernel.org>
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index d53a456..38739a4 100644
--- a/README.md
+++ b/README.md
@@ -66,7 +66,7 @@ Once you have such a kernel, run one of:
* virtme-run --installed-kernel VERSION
* virtme-run --kimg PATH_TO_KERNEL_IMAGE
-Note that the --kdir and --kimg modes do not support modules yet.
+With --installed-kernel or --kdir, modules associated with the kernel will be available in the VM. With --kdir in particular, you will either need to follow the directions that virtme-run prints or specify --mods=auto to make this work. With --kimg, modules are not supported.
You can then do things like `cd /home/username` and you will have readonly
access to all your files.