summaryrefslogtreecommitdiffstats
path: root/release
diff options
context:
space:
mode:
authorgjb <gjb@FreeBSD.org>2015-08-13 18:50:54 +0000
committergjb <gjb@FreeBSD.org>2015-08-13 18:50:54 +0000
commit1717104aa9777de5e792059581f096772a29c5e1 (patch)
treeda306aa3e1f41bc16f617caac64dd0806623a4da /release
parenta99cffa12bb357b20a46d9fbcb5f7f5f3e24250a (diff)
downloadFreeBSD-src-1717104aa9777de5e792059581f096772a29c5e1.zip
FreeBSD-src-1717104aa9777de5e792059581f096772a29c5e1.tar.gz
Document a known issue with the VirtualBox Vagrant provider failing
to boot on the first invocation of 'vagrant up'. Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
Diffstat (limited to 'release')
-rw-r--r--release/doc/en_US.ISO8859-1/errata/article.xml17
1 files changed, 17 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 3dbd676..c0c8fcd 100644
--- a/release/doc/en_US.ISO8859-1/errata/article.xml
+++ b/release/doc/en_US.ISO8859-1/errata/article.xml
@@ -251,6 +251,23 @@ boot</screen>
cause source-based upgrades to fail, a post-release Errata
Notice is planned.</para>
</listitem>
+
+ <listitem>
+ <para>An issue with &os; virtual machines with
+ <application>vagrant</application> was discovered that
+ affects the <application>VirtualBox</application> where the
+ virtual machine will not start on the initial boot invoked
+ with <literal>vagrant up</literal>.</para>
+
+ <para>The issue is due to the virtual machine
+ <acronym>MAC</acronym> being unset, as &os; does not provide
+ a default <filename>Vagrantfile</filename>.</para>
+
+ <para>It has been observed, however, that a subsequent
+ invocation of <literal>vagrant up</literal> will allow the
+ virtual machine to successfully boot, allowing access via
+ <literal>vagrant ssh</literal>.</para>
+ </listitem>
</itemizedlist>
</sect1>
OpenPOWER on IntegriCloud