summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorgjb <gjb@FreeBSD.org>2014-04-03 14:13:57 +0000
committergjb <gjb@FreeBSD.org>2014-04-03 14:13:57 +0000
commit5eff512a5157dcd6c4d84a77b9d1cc8df924e36e (patch)
tree46f7b529f4277c3dbf2250cc26eabd1165290233
parent003ac1d9a0df25662ff249364e9d61d968d7f61d (diff)
downloadFreeBSD-src-5eff512a5157dcd6c4d84a77b9d1cc8df924e36e.zip
FreeBSD-src-5eff512a5157dcd6c4d84a77b9d1cc8df924e36e.tar.gz
Document that the FreeBSD/i386 instability with
vfs.unmapped_buf_allowed=1 may be present on VMs running on hypervisors other than VirtualBox. Sponsored by: The FreeBSD Foundation
-rw-r--r--release/doc/en_US.ISO8859-1/errata/article.xml4
1 files changed, 4 insertions, 0 deletions
diff --git a/release/doc/en_US.ISO8859-1/errata/article.xml b/release/doc/en_US.ISO8859-1/errata/article.xml
index aee69c8..3484264 100644
--- a/release/doc/en_US.ISO8859-1/errata/article.xml
+++ b/release/doc/en_US.ISO8859-1/errata/article.xml
@@ -167,6 +167,10 @@ boot</screen>
It disables unmapped I/O at every boot:</para>
<programlisting>vfs.unmapped_buf_allowed=0</programlisting>
+
+ <para>[2014-04-03 update] It has been reported that
+ instability may be present on virtual machines running
+ on other hypervisors, such as Xen or KVM.</para>
</listitem>
<listitem>
OpenPOWER on IntegriCloud