Bug 202323
| Summary: | 10.2-RELEASE Announcement vagrant instructions don't work | ||
|---|---|---|---|
| Product: | Documentation | Reporter: | Chip Marshall <chip> |
| Component: | Website | Assignee: | freebsd-doc (Nobody) <doc> |
| Status: | Closed Works As Intended | ||
| Severity: | Affects Some People | ||
| Priority: | --- | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
| URL: | https://www.freebsd.org/releases/10.2R/announce.html | ||
|
Description
Chip Marshall
2015-08-14 13:10:18 UTC
'vagrant ssh' should work at this point. 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. (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. Ah, I never think to check the errata. A second `vagrant up` does work (although still tosses that error) but `vagrant ssh` does work after that. Just seems unpolished. Still nice to have though, hope it continues to improve :) > 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 up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Checking if box 'freebsd/FreeBSD-10.2-RELEASE' is up to date... ==> default: Setting the name of the VM: Personal_default_1439559903932_75205 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... default: 22 => 2222 (adapter 1) ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key default: Warning: Connection timeout. Retrying... default: Warning: Remote connection disconnect. Retrying... default: Warning: Remote connection disconnect. Retrying... default: Warning: Remote connection disconnect. Retrying... default: Warning: Remote connection disconnect. Retrying... default: Warning: Connection timeout. Retrying... default: Warning: Remote connection disconnect. Retrying... The configured shell (config.ssh.shell) is invalid and unable to properly execute commands. The most common cause for this is using a shell that is unavailable on the system. Please verify you're using the full path to the shell and that the shell is executable by the SSH user. > vagrant ssh FreeBSD 10.2-RELEASE (GENERIC) #0 r286666: Wed Aug 12 15:26:37 UTC 2015 Welcome to FreeBSD! Release Notes, Errata: https://www.FreeBSD.org/releases/ Security Advisories: https://www.FreeBSD.org/security/ FreeBSD Handbook: https://www.FreeBSD.org/handbook/ FreeBSD FAQ: https://www.FreeBSD.org/faq/ Questions List: https://lists.FreeBSD.org/mailman/listinfo/freebsd-questions/ FreeBSD Forums: https://forums.FreeBSD.org/ Documents installed with the system are in the /usr/local/share/doc/freebsd/ directory, or can be installed later with: pkg install en-freebsd-doc For other languages, replace "en" with a language code like de or fr. Show the version of FreeBSD installed: freebsd-version ; uname -a Please include that output and any error messages when posting questions. Introduction to manual pages: man man FreeBSD directory layout: man hier Edit /etc/motd to change this login announcement. Forget what directory you are in? Type "pwd". -- Dru <genesis@istar.ca> vagrant@:~ % |
