Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Aug 2015 13:42:42 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-doc@FreeBSD.org
Subject:   [Bug 202323] 10.2-RELEASE Announcement vagrant instructions don't work
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/>

next in thread | previous in thread | raw e-mail | index | archive | help
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202323-9-veAyeIGSUN>