diff options
author | Joe MacDonald <joe@deserted.net> | 2013-09-24 14:41:00 -0400 |
---|---|---|
committer | Joe MacDonald <joe@deserted.net> | 2013-09-25 10:52:12 -0400 |
commit | 91fc10df2f2158cb6ae892636e8cff00c3479f42 (patch) | |
tree | cec5564fe9911cd58793e1088a8a860b9bb60996 | |
parent | 1f23fb218e55000b8f4bc8c47509631ffcc28445 (diff) | |
download | meta-selinux-91fc10df2f2158cb6ae892636e8cff00c3479f42.tar.gz |
documentation: update guidance for runqemu
Testing SELinux on QEMU occasionally results in OOM conditions during a
relabel from time to time. Update the documentation to warn about this
and suggest a way to avoid the situation.
Signed-off-by: Joe MacDonald <joe@deserted.net>
-rw-r--r-- | SELinux-FAQ | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/SELinux-FAQ b/SELinux-FAQ index 5894626..b6a0df9 100644 --- a/SELinux-FAQ +++ b/SELinux-FAQ | |||
@@ -111,6 +111,14 @@ For example, when you are using qemu targets, | |||
111 | 111 | ||
112 | $ runqemu qemumips core-image-selinux ext3 nographic bootparams="selinux=0" | 112 | $ runqemu qemumips core-image-selinux ext3 nographic bootparams="selinux=0" |
113 | 113 | ||
114 | The initial filesystem relabel step requires considerable memory and can result | ||
115 | in unexpected, sometimes impossible to reproduce, failures if an OOM condition | ||
116 | occurs while it is in progress. Therefore you should consider allocating at a | ||
117 | minimum 512MB of RAM to your qemu image. 1GB or more is recommended. This is | ||
118 | accomplished by adding qemuparams="-m 1024" to your runqemu options. | ||
119 | |||
120 | The defaults for various platforms vary, though it is usually around 256MB. | ||
121 | |||
114 | 3.2 - How do I turn enforcing mode on/off? | 122 | 3.2 - How do I turn enforcing mode on/off? |
115 | 123 | ||
116 | You can specify the SELinux mode in /etc/selinux/config. | 124 | You can specify the SELinux mode in /etc/selinux/config. |