Author: gjb
Date: Thu Aug 13 18:50:54 2015
New Revision: 286738
URL: https://svnweb.freebsd.org/changeset/base/286738
Log:
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
Modified:
stable/10/release/doc/en_US.ISO8859-1/errata/article.xml
Modified: stable/10/release/doc/en_US.ISO8859-1/errata/article.xml
==============================================================================
--- stable/10/release/doc/en_US.ISO8859-1/errata/article.xml Thu Aug 13
18:45:52 2015 (r286737)
+++ stable/10/release/doc/en_US.ISO8859-1/errata/article.xml Thu Aug 13
18:50:54 2015 (r286738)
@@ -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>
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-stable-10
To unsubscribe, send any mail to "[email protected]"
