From owner-freebsd-doc@freebsd.org  Fri Aug 14 13:42:42 2015
Return-Path: <owner-freebsd-doc@freebsd.org>
Delivered-To: freebsd-doc@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6480C9B8170
 for <freebsd-doc@mailman.ysv.freebsd.org>;
 Fri, 14 Aug 2015 13:42:42 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 517F215EC
 for <freebsd-doc@FreeBSD.org>; Fri, 14 Aug 2015 13:42:42 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t7EDggSQ026790
 for <freebsd-doc@FreeBSD.org>; Fri, 14 Aug 2015 13:42:42 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-doc@FreeBSD.org
Subject: [Bug 202323] 10.2-RELEASE Announcement vagrant instructions don't work
Date: Fri, 14 Aug 2015 13:42:42 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Documentation
X-Bugzilla-Component: Website
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: gjb@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-doc@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-202323-9-veAyeIGSUN@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-202323-9@https.bugs.freebsd.org/bugzilla/>
References: <bug-202323-9@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Documentation project <freebsd-doc.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/>
List-Post: <mailto:freebsd-doc@freebsd.org>
List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Aug 2015 13:42:42 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202323

--- Comment #3 from Glen Barber <gjb@FreeBSD.org> ---
(In reply to Chip Marshall from comment #2)
> Just tried again from scratch, this time got:
> 
> > vagrant init freebsd/FreeBSD-10.2-RELEASE
> A `Vagrantfile` has been placed in this directory. You are now
> ready to `vagrant up` your first virtual environment! Please read
> the comments in the Vagrantfile as well as documentation on
> `vagrantup.com` for more information on using Vagrant.
> > vagrant up
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'freebsd/FreeBSD-10.2-RELEASE'...
> No base MAC address was specified. This is required for the NAT networking
> to work properly (and hence port forwarding, SSH, etc.). Specifying this
> MAC address is typically up to the box and box maintainer. Please contact
> the relevant person to solve this issue.
> > vagrant ssh
> VM must be running to open SSH connection. Run `vagrant up`
> to start the virtual machine.

This particular issue is noted in the errata document for 10.2-RELEASE.  A
subsequent invocation of 'vagrant up' should start the VM.

Note, the output here differs from the initial report.

-- 
You are receiving this mail because:
You are the assignee for the bug.